LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

error loading DLL after upgrading LabVIEW

I recently upgraded from LabVIEW 7.0 to LabVIEW 8.5.  Most of the related issues with my code have now been resolved, but one DLL in particular is giving me problems.  It won't load properly.  Whenever I open a program containing a Call Library Function that references this particular DLL, I get an error message that there is an "Invalid access to memory location."
 
It is a third party DLL (ksv285_32.DLL from Kinetic Systems) that loaded and worked just fine under LabVIEW 7.0.  I've looked through the upgrade issues and haven't seen anything like this.  Any suggestions?
0 Kudos
Message 1 of 9
(3,680 Views)
Hi Quantum,

How are you?
I got a couple of questions for you:
1. What language is the DLL made of (.NET assembly? or C? etc?)
2. Does this error occur during run time or during edit mode?
3. What is the exact error code and error message?
4. Have you tried running this in other versions other than 8.5? (example 8.0 or 8.2)

Thanks

Van L
NI Applications Engineer
0 Kudos
Message 2 of 9
(3,656 Views)

Hi Van_L,

Thanks for responding.  Here are my answers:

1. The DLL uses the stdcall (WINAPI) calling convention.  Other than that piece of information, and the fact that it was last updated 8 years ago, I don't really know much about the actual DLL file.

2. The error occurs during edit mode.  It comes up as soon as I open the VI.  Because of the error, I can't even try to execute the code.

3. The error is

Error loading "D:\LabView Programs\QCEv12-3\ksv285_32.DLL".
Invalid access to memory location.
 
4. I have not tried any versions other than 7.0 and 8.5.  If I can get access to a copy of the intermediate versions (7.1, 8.0, 8.2) I may try those.
 
Thanks again for the response.
0 Kudos
Message 3 of 9
(3,637 Views)
Hi Quantum,

Can you try to build a simple vi that just calls this DLL using the call library function node?
Do you still get error there?
What's different with this particular DLL than others? are the others devleoped by the same company?

You might want to contact the company that produces it and find out what language it's written in and see if they experience problems with LV 8.5 and if so are they releasing newer versions to fix it.

Let me know how that goes
Van L
NI Applications Engineer
0 Kudos
Message 4 of 9
(3,632 Views)

Van_L

I tried a simpler VI and that didn't work either - same loading error.

This DLL is from a different company than the others.  I have contacted the company and am waiting for a response from them.

In the meantime, I think I will try to reinstall the drivers and see if that helps...

Thanks again for responding.

0 Kudos
Message 5 of 9
(3,603 Views)
Reinstalling the drivers didn't help.
 
However, I installed LabVIEW 8.5 on a different machine, one running Windows XP (instead of Windows Server 2003) and the DLL opens just fine on that machine.
 
This is helpful, but I would still like to get the code working on the original machine if I can.  Any recommendations?
0 Kudos
Message 6 of 9
(3,526 Views)
Is the machine a 64-bit machine using Windows Server 2003 x64?  If so, it may point to an incompatibility in the DLL.
0 Kudos
Message 7 of 9
(3,522 Views)
The operating system is 32-bit (Windows Server 2003 Standard Edition).
0 Kudos
Message 8 of 9
(3,508 Views)
Hello Quantum, 

LabVIEW is not officially compatible nor supported on Windows 2003 Server or Windows 2000 Server Edition. Even though you had success with LabVIEW 7 on Windows Server 2003, we cannot guarantee that you will have the same success on Windows Server 2003.  Supported operating systems can be found in the release notes for LabVIEW.

If you can, try to use one of the combinations of OS and LabVIEW versions that you know are working with the DLL.

Take care!
Kameralina

0 Kudos
Message 9 of 9
(3,488 Views)