Ordinal 65 could not be found in NIVISV32.dll

[dbarbacci]

I'm getting the error above when trying to create a debug executable. I've found and checked the dll and ordinal 65 is visaFreeObject and its entry point is 0000 0000. I guess from the entry point that it isn't there. Is this a correct assumption? What to do next?

[Jason F.]

Usually, you get this error when you have a corrupt installation of NI-VISA. Did you encounter any errors while installing NI-VISA, either as a stand alone installation or as part of an installation of another product like NI-488.2 or NI-DAQ?

Try properly reinstalling NI-VISA on your system to see if that fixes the problem. Make sure to try uninstalling via Add/Remove Programs first, rebooting, and then installing again.

Jason F.
Applications Engineer
National Instruments
www.ni.com/ask

[dbarbacci]

Jason, I tried numerous software installations including upgrades. The only solution was a downgrade of NIVXI to version 2.11. The NiVisV32.dll is version 2.0.0 (build 16). Surprisingly, this version doesn't have an ordinal 65. What do make of this?

[Jason F.]

I'm a little confused as to where you are currently at on this. You say that the problem is solved by downgrading NI-VXI to v2.11? As far as nivsv32.dll v2.0.0 not having an ordinal 65, do you mean that the ordinal numbers in your version do not go as high as 65, or do you mean that when using a program like MS Depends the ordinal 65 comes up as not available? I have version 2.5.21 on my system and it comes up as n/a. The error you were receiving most likely didn't mean anything was specifically looking to use code at ordinal 65 in the dll, just that when trying to load the dll it did not like the integrity of it. We have never researched exactly what this means in terms of what the error code was generated from, but we know that it is generall
y caused by a corrupt installation of NI-VISA or other software that depends on it, such as NI-VXI.

Jason F.
Applications Engineer
National Instruments
www.ni.com/ask

[dbarbacci]

Sorry about that, I'll be more specific. I used Quick View from the right mouse click pull-down menu to view info about the dll. In version 2.0.0 of nivisv32.dll there is no ordinal 65 in the import or export table. In the version loaded with NIVXI 3.0, there is an ordinal 65 and it corresponds to visaFreeObject with an entry point of 0000 0000.

The error I observe occurs before the first line of code, so I would guess that there is something wrong with the file.

When I updated the VXI drivers, there were a couple of older files (a few *.lib and visa32.dll) in the project directory that were part of the project. Could that also be a source of the error?

[Jason F.]

Yes, if the only version of a dll by a particular filename is available to another dll that depends on it, and it is the wrong version there may be some descrepancies in the image of the dll that could cause it to be accessed incorrectly by the dependent dll in a call to FindResource or GetProcAddress. Also when a dll is loaded by a call to LoadLibrary, Windows does include the directory of whatever module called the function as a possible location for that dependent dll, so it very may be that one of the files you mentioned is trying to load the dll improperly. As I said before though, the only thing I can find in reference to this problem is when somebody has aa corrupt dll possibly due to a failed installation of a driver. Th
e only suggestion we can possibly give to make it work as we intended is to get a proper installation working on the machine, which I am assuming that you have now.

Jason F.
Applications Engineer
National Instruments
www.ni.com/ask