New DAQmx Drivers and I get an Error Trying to Run My Application

[DieselPower]

I just received the latest version of Measurement Studio 8.6 and I upgraded my development computer with it.  Then I opened my application and upgraded that and all was well.  I then propagated the latest build of my application to five different computers.  All of them have similar hardward configurations.  I did have a FileLoad error before upgrading the drivers at each test cell, but upgrading the drivers solved that for all but one test cell.

This one testcell spits out the error shown below when I try to run the application.  It is in the Initialize component subroutine so I can't debug it.  It has something to do with the waveform plot.  Any ideas?

 Thanks!

[DieselPower]

I should mention the things I've tried...

• Reinstalled the DAQ drivers at the cell.
• Updated the dependencies in the project and recompiled.
• Reinstalled the program at the test cell.
• Uninstalled and reinstalled the same build at a different test cell and verified that that test cell still works while the one in question does not with the same drivers and the same application.

[CorbinH]

This exception usually occurs when the underlying library DLLs are not present. Does the program work just fine on the development machine? I am also assuming this error occurs during run-time and not during installation.

What I would like for you to do is generate a log file of the installation for me. To do this, run your setup.exe file for the installation from command prompt, but add the following lines to the command line:

<directory>setup.exe \log install.log

This will place a log file of the install in the directory of the setup.exe file. Once you have uninstalled your program and reinstalled it with the log file, could you please post that log file?

[DieselPower]

Here is the good install and the bad install.

Thanks for your help.

[CorbinH]

Michael,

Are these log files from the same installer? I noticed quite a few differences in the two log files. For one, the "bad" install installed nianlys.dll and the "good" install did not. I also noticed the "bad" install was on a service pack 3 computer and the "good" install was on a service pack 2 computer. Were all the "good" installs done on service pack 2 computers?

[DieselPower]

The "bad" install was on the newest computer.  The rest are all older so I would assume they are all SP2.

[DieselPower]

Fixed it.

Somehow .NET Framework 3.5 was disincluded as a prerequisite in my project.  That is probably the reason that the new computer wouldn't work.  I just installed the .NET Framework and it works. 

Your question about service packs led me to check out the Add/Remove programs list and I noticed that 3.5 wasn't there.  

Thanks a lot!

[CorbinH]

Ah! Glad to hear. One of the reasons I was asking about service packs was due to the .NET Frameworks. I am glad you were able to fix the issue.