VISA errors 1073807343 and 1073807202

[rattier]

Greetings everyone,

I am having multiple issues with VISA 5.0.3 and LabVIEW 2010 SP1, and I am not sure if or how they are related, so I will post as much information as I have here. Please excuse the super long post, just trying to be thorough.

Error BFFF009E (same as 1073807202 I believe) is shown on opening MAX as seen in ss1 attached. When trying to open VISA Interactive Control (IC), I get the message "Unable to initialize the VISA library. The VISA Interactive Control utility will exit." When I open any VI with a VISA resource and try to click the dropdown arrow on the right to see available resources, the arrow stays derpessed for a second, no dropdown field appears, and then it goes back to its original blank state. These problems all occur together now, but previously I was able to select VISA resources in LV and use VISA IC, while I have always seen the MAX error.

I have tried repairing VISA, as well as uninstalling-reinstalling VISA 5.0.3, which I believe is the newest version. No change. I have also verified that visa32.dll exists as suggested in the article below. See systeminfo.txt attached for installed software.

http://digital.ni.com/public.nsf/allkb/1D1736BFD24A09878625742500241386

This error seems to be related to a Tektronix DPO 2014 oscilloscope that I have connected over USB (or maybe something to do with TekVISA?). By that I mean that if the scope was connected when my computer booted up, this error occurs. When the scope is not connected at startup, I do not see the same problems as above. Instead I get...

Error 1073807343 (BFFF0011) when running a VI with a VISA resource to a serial device (see ss2), or when connecting to the device in VISA IC (see ss3). I also still see the BFFF009E error in MAX, but not the other problems from before. I can connect to these serial devices in hyperterminal and communicate just fine there. Seems similar to the post below, and I also cannot find visaconf.ini, but the solution does not apply as I have LV 2010. Also, ironically, I can use VISA just fine to talk to the scope (either in MAX or LV) over USB if I connect it after startup.

http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/Using-HP34401A-in-LabView-yields-error-code-1...

I am using Serial to USB adapters made by Ultra (http://mail.ultraproducts.com/product_resources.php?cPath=35&pPath=782&productID=782 ) to go from the serial instruments to my USB ports, and unfortunately the computer I am on has no serial ports to test with, nor do I have another brand of adapter. I know these converters can be an issue with VISA sometimes, but I was definitely using this same one without issue before.

These all seem to be intermittent issues, as I have seen them both before as I was developing, and got them to go away through strange things like swapping (apparently identical) USB extension cables or rebooting about a dozen times. This issue has been driving me crazy for weeks, I am looking for help to try to finally resolve it.

Thanks,

rattier

[rattier]

Last screenshot.

[rattier · Accepted solution]

I think I got it mostly figured out. Looks like it was TekVISA that was getting in the way, and though Visa32.dll was in the right place, it appeared (in Properties>>Details) to be the Tektronix version, not the LabVIEW version. After uninstalling everything Tektronix as well as NI-VISA, it was gone, but no amount of installing or repairing NI-VISA would replace it with a LabVIEW version Visa32.dll. 

However, with the help of the article linked below, I discovered that repairing the install of the NI-VISA Runtime is what replaces Visa32.dll, as opposed to just NI-VISA as the error messages and other links seemed to suggest.

http://digital.ni.com/public.nsf/allkb/B283196340462DFD86257633006DC799

Now all my VISA stuff is working again, except of course for the Tektronix scope. I'll save that battle for tomorrow. Guess I just needed to talk to myself for a while.

-rattier

[LuI]

Somehow similar and not, anyway...

Got an app built with LV711. The HD was moved to aother one via an image (due to bad sectors etc.). Afterwards the app no longer worked and reported 'VISA error -1073807202' (0xBFFF009E). Filexplorer revealed that some ni*.dll where missing... A reinstallation of the runtime engine fixed that.