Windows 2000 locks up when running an exe file or Measurement & Automation

[Stagnok]

Hi all, I was hoping I could get some help here.

I have a system running windows 2000, LabView 5.1.2, Ni-Daq 6.7, it also has the application builder installed, LabView runtime engine 5.1 and 5.1.1 adn some other stuff like the NI-Pal, Ni-Imaq etc...

When run my exe file the screen comes up that searches for the files and gets to the lvdaq.dll file then promptly locks up everything.  I have to shut off the main power and reboot to get it working agian. 

Also if I instead go to measurement and automation and click on data neigbhorhood or work with daq files (File - new configuration, open configuration, save configuartion as, etc) the computer will lock up as well. 

I am in the process of uninstaling LabView and Ni-Daq so I can reinstall them to try to fix the problem; However, I was wondering if anyone has ever encounted a problem such as this one and what you might have done to fix it?

Thanks in advance for you help.

Bill

[Ryan_V[DE]]

Bill,

Did anything change on your computer that triggered this error? It sounds like lvdaq.dll driver was somehow corrputed. Uninstalling and reinstalling the DAQ driver is probably your best bet here. I would recommend using the latest version that is compatible with LabVIEW 5.1.2, NI-DAQ 6.9.3. You will also need to download the appropriate installation component, in your case LV51Eng.EXE.

Hope this helps,
Ryan

[Stagnok]

Thanks for the reply Ryan.  As far as I could determine nothing was changed in the software or windows.  The console was working and the technician changed a test unit and it locked up and has been locking up ever since.  This is the technicians account (I only acquired the problem after it was happening). 

Just to inform, the console is using a GUI and RT controllers.  I am almost positive the problem is somewhere in the communication between the two. 

I have uninstalled and reinstalled all NI software and Ni-Daq software on the GUI and RT compupter with out fixing the problem.  I have since reinstalled the network adapter drivers and had to leave for the day.  I will test that tomorrow. 

This problem has occured once before from what another Engineer told me.  That Engineer conversed with NI technical staff and tried everything to fix the problem.  Unfortuanly he ended up having to just reformat and reinstall from the ground up on the GUI computer and RT computer. 

I am hoping to find the solution without doing all that but I am almost to the point where that is all I have left 🙂  Anyways, I will post results as I get them. 

Has anyone else ever encounted this type of problem? 

Bill

[Ryan_V[DE]]

If you believe it is just the communications what happens if you run a VI on your target that does no communications?  Also in your first post you mentioned that you were running an EXE.  Did you mean that you were doing a startup exe?  Next, what RT controller are you using?  Finally, make sure you have the same versions of LVRT, DAQ and other drivers on your host and target.  You may want to consider upgrading your versions of LVRT and DAQ - the newer ones are much more reliable. Please let us know the answers to these quesitons and have a great day!

Ryan

[Stagnok]

Well, we are still working on this problem.  It seems like it might just be bad PXi-1010 Chasis, all three of them!  Which seems highly unlikely but we have tested the Controllers in a 4th Chassis without problems.  We would put the 6031 card in different slots of the 1010 chassis and get semi different problems like locking up or complete blue screen crash. 

Still working on it though.

Bill