HomeSupportGPIB-32.DLL is Missing or Damaged After Installing Agilent IO Libraries

GPIB-32.DLL is Missing or Damaged After Installing Agilent IO Libraries

Updated Jan 3, 2018

Reported In

Reported In shows products that are verified to work for the solution described in this article. This solution might also apply to other similar products or applications.

Hardware

GPIB-USB

PCI-GPIB

PCI-GPIB+

Software

Measurement and Automation Explorer (MAX)

Driver

NI-488.2

GPIB Software

NI-VISA

Issue Details

I installed the Agilent's IO Libraries 14.1 and now my GPIB interface is not working properly. I see the message:

The NI-488.2 file 'GPIB-32.DLL' is either missing or damaged

Solution

Agilent IO Libraries 14.1 overwrites a portion of the National Instruments NI-488.2 driver when it is installed. The installer renames National Instruments' GPIB-32.dll file in the \System32 directory to GPIB-32.ORIG.dll, and copies Agilent's GPIB-32.dll in place of NI's GPIB-32.dll.

Note: Agilent IO Libraries 14.0 and prior versions do not exhibit this behavior and thus should not produce this problem.

If you want to use your NI card on a machine that still has the Agilent and NI GPIB drivers installed, use the following procedure:

Launch the Agilent Connection Expert

Select Tools» Options

Select the Agilent 488 Options tab

Uncheck the Use the Agilent 488 driver library where possible checkbox

The Agilent software should no longer overwrite your NI GPIB-32.dll with Agilent's version.

Additional Information

Because NI's GPIB tools and accessories expect to communicate directly with NI's GPIB-32.dll file, NI-488.2 and Agilent IO Libraries 14.1 cannot coexist on the same system. The Agilent IO Libraries monitor the GPIB-32.dll and will continuously replace it with the Agilent version of the DLL if it is changed. This makes it impossible to just restore the National Instruments version of the DLL without first removing Agilent IO Libraries 14.1.