From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

urgent GPIB crash

Solved!
Go to solution

Hello

this morning we had a worse crash of one of our systems. During the startup the computer hangs and has to be restarted several times. When it is started finally, the CVI software do not work. We started the MAX and got an error message like this:

 

The niGPIBsys.dll plug-in caused an exception in the CmxSysExpertManager::FinalizeExpert function in the NIMax process.
See these files for details:
C:\Documents and Settings\All Users\Application Data\National Instruments\MAX\Logs\20140602_091902-NIMax-00000654.log
C:\Documents and Settings\All Users\Application Data\National Instruments\MAX\Logs\20140602_091902-NIMax-00000654.dmp

In the log file we found:

Context where exception was caught:
Func: CmxSysExpertManager::FinalizeExpert Args: plugin=niGPIBsys.dll

 

The problem is: We do not have a GBIP device in the system, there is only a Highspeed Digital I/O card 6534 inside.

 

Does anybody know what we can do to restart the system and bring it back to work

 

thanks

Oliver

 

0 Kudos
Message 1 of 4
(4,950 Views)

Hi Oliver,

 

have you tried to use the repair funktion for CVI ? What other products of NI do you have installed on your system?

 

Regards Anoj

Anoj Mubarak
National Instruments
0 Kudos
Message 2 of 4
(4,896 Views)
Solution
Accepted by topic author OZI

Hello

yes we tried to repair CVI and we deinstalled and reinstalled NI-Max but it didn't work. So we made a new installation of windows to solve the problem.

 

best regards

Oliver

 

0 Kudos
Message 3 of 4
(4,893 Views)

It seems like you have resolved the issue, and that you really didn't need to have the NI-488.2 driver on your system, but I wanted to respond for anyone else who may view this topic. This exception matches an issue that was fixed in the NI-488.2 3.1.2 driver release. Updating the version of NI-488.2 on the system should resolve the issue.

 

-Jason Smith

0 Kudos
Message 4 of 4
(4,824 Views)