error 7, looks like GPIB got lost.

[Jay_Dubya]

FWIW Battle story:   LabView 2011 on a Windows 7 machine being compiled and ported over to a Windows XP sp3 laptop.

One might think from the following error message that the GPIB was somehow messed up and getting lost after the first initialization of the GPIB devices that I have connected:

After doing a LOT of messing around with the test and diligently removing one GPIB call at a time and recompiling and sending it over to the laptop the test was still failing with the same error and NO reference to any GPIB device in the code…..   the only thing to do was to look elsewhere.

So…………..   after some more fooling around with the Windows 7 source code that works properly, I found I could create the following error message by moving the .CSV file that the program uses to translate D/A temperature sensor output to real world degrees centigrade.

  Finally, a real clue!   BUT what is up with the GPIB?

Still complaining about the GPIB …BUT the actual problem was that the .CSV file was in the wrong location on the lap top even though the .vi that uses it was pointed correctly.   I fixed the location of the CSV on the laptop and the natives rejoiced and danced. 

Thanks NI for the concise and exacting error information that made a simple fix so much fun to find.

[Dennis_Knutson]

This has been discussed numerous times. If you notice - it says possible reason(s). So, error code 7 can be either a GPIB or file error. You can determine which function is actually throwing the error and isolate the problem.

[crossrulz]

I have never ran into that error due to GPIB.  The only reason I can think of that you would get that error for GPIB is if the card suddenly decided to disappear.  When I get that error, I always look for missing file(s) first.

[Dennis_Knutson]

And of course, no one should be using GPIB functions anyway since VISA has been preferred for a very long time.