NI TestStand
Can not load Automation Suppor DLL
Hi,
if I'm reading this correctly, someone generated a test system for you, and installed it all OK, but after a HDD crash, you've re-instated the files you backed up, but not done a re-install?
Does the error message tell you which DLL it cannot load, or any other information? Is it the operator interface you cannot launch, or having the operator interface working OK, is it a sequence that you cannot run?
The TestStand directory should contain a bin directory, and in there should be some dll's that TestStand needs to have registered with the OS to work. I think there's also some in the windows system directory (I'm on a PC without access to TestStand at the minute)
If you can find the appropriate files, you could do a start->run...
regsvr32
an
d that would register the .dll with the OS.
If however, you can find the version of the TestStand run-time engine, you could ask here if someone would generate you an run-time engine installation set of files for that version, and then you would know that the registry is correctly setup. (There's a little more than just the registering of files to be able to do things like use MAX (Measurement and Automation Explorer) to check for NI software installed on your system.) Find one of the dll's in the bin directory, and right click it (in windows explorer) and go to properties. It should give a version like 1.0, 1.0.1, 1.0.2, 1.0.3, 2.0, 2.0.1, 2.0.1f1, 3.0 etc, possibly with some build version information after it.
If the problem isn't with a TestStand dll not being registered, then it could be that your 3rd party generated some code which also needs to be registered on the system to run.
Thanks
Sacha Emery
National Instruments (UK)
if I'm reading this correctly, someone generated a test system for you, and installed it all OK, but after a HDD crash, you've re-instated the files you backed up, but not done a re-install?
Does the error message tell you which DLL it cannot load, or any other information? Is it the operator interface you cannot launch, or having the operator interface working OK, is it a sequence that you cannot run?
The TestStand directory should contain a bin directory, and in there should be some dll's that TestStand needs to have registered with the OS to work. I think there's also some in the windows system directory (I'm on a PC without access to TestStand at the minute)
If you can find the appropriate files, you could do a start->run...
regsvr32
an
d that would register the .dll with the OS.
If however, you can find the version of the TestStand run-time engine, you could ask here if someone would generate you an run-time engine installation set of files for that version, and then you would know that the registry is correctly setup. (There's a little more than just the registering of files to be able to do things like use MAX (Measurement and Automation Explorer) to check for NI software installed on your system.) Find one of the dll's in the bin directory, and right click it (in windows explorer) and go to properties. It should give a version like 1.0, 1.0.1, 1.0.2, 1.0.3, 2.0, 2.0.1, 2.0.1f1, 3.0 etc, possibly with some build version information after it.
If the problem isn't with a TestStand dll not being registered, then it could be that your 3rd party generated some code which also needs to be registered on the system to run.
Thanks
Sacha Emery
National Instruments (UK)
