Error -17501: Unable to Test Environment adapter "C/CVI Std Prototype Adapter"

[JoergLee]

I use LabVIEW as Windows NT 4.0 shell. When I start TestStand (TS) during the LabVIEW shell I get the Error Message that TS can`t load the C/CVI Adapter (see Attachment). I configured also somthing on the DCOM tool, but that helps nothing. Knows somebody how it is possible to remove the C/CVI adapter from TS or what is neccessary to fix this problem.

[Carlos L]

Hello Joe,

If I understand correctly, you are using the LabVIEW Operator Interface, right?
How did you install TestStand in that machine? Using the TestStand CD and performing a full installation of TestStand? Or did you create a run-time engine installation?
Were you able to use the Operator Interface without problems before? (If so, what did you do before it stopped working?)

This might be related to the CVI run-time engine that is installed in your computer. If you are using TestStand 2.0, the CVI run-time engine version 5.5.1 or later MUST be installed in the machine. If you don't have it installed or if you have an earlier version, you get some errors.

FYI, the LabWindows/CVI Run-Time Engine is located on the TestStand CD
in the CVRTE folder, or you can download it from the Drivers and Updates library: http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BBB002C0E4F?opendocument&node=132060_US

Regards,

Carlos Leon

[JoergLee]

I use the LabVIEW Operator Interface 2.0f1 and the Error Message is the same, when I install the CVI Runtime Engine 6.02.

Teststand starts correctly, when I use the explorer shell from Windows, but when I use LabVIEW as Windows NT Shell the error message comes. Why I cannot connect to the TSAutoMgr.exe? When I look in the system resources I see, that the hardware 'cvintdrive' is started.

[Carlos L]

Joe,

I am a having some problems understanding what you mean by using the "explorer shell" vs "LabVIEW as Windows NT shell"??
a) By "I use the explorer shell", do you mean that you open the Windows explorer and double click on the LabVIEW Operator interface executable (testexec.exe)?
b) By "I use LabVIEW as Windows NT Shell", could you explain exactly what you mean?

Regards,

Carlos Leon

[JoergLee]

to a) "I use the explorer shell", means that I use the normal Windows and in the Registry Key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell" is standing "explorer.exe".

to b) "I use LabVIEW as Windows NT Shell", means that I use my own Windows Desktop and in the Registry Key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell" is standing "C:\Programms...\labview.exe "Application.vi"". So I can determine which programms could be open from the teststand operator and I save a lot of system resources, because only less applications are running in the background.