System Level Exception. Error code -17502

[Martin.D]

"System Level Exception, Error code -17502" when starting TestStand, then TestStand closes. This has happened on two of our systems now. After reading some other postings that discuss this error we tried creating a new windows user account, now TestStand starts OK. Can someone help us with this? We would very much like to eliminate the cause of this error.

Win NT4 & 2000, TestStand 2.01

Before the error occurred TestStand was running modules created in the following environments:

LabVIEW 6.1, Labwindows CVI.

[Elaine_R.]

Hello Martins -

I am curious when you say that TestStand was running modules before. Is it safe to assume that TestStand was at one point working on your WindowsNT4 machines? Has something recently been added or taken away from your system that has caused this altered behavior? Errors such as 17502 at launch are commonly caused by an inability for the TestStand to see/ interact with the CVI Run-Time Engine or other support software needed for basic internal DLL interpretation/ additional features (17502 errors are also seen sometimes when calling steps using the CVI Adapter). Reasons why this failure to communicate occur to whether or not CVI and TestStand were installed by someone with Administrator access on the WindowsNT machine, and also what the access leve
l of the current user logged in is set to on the operating system. Launching ActiveX servers is usually a function reserved for Super Users and higher on Windows systems which is why some customers have good luck with simply altering user privileges. Usually the least time-consuming way of resolving issues like this is to double check that the software (CVI and TestStand) was installed by an Administrator, and if not, simply log in as Administrator and install over the existing installations to reset the system settings 'for all users'.

If you have any information to add it may help me offer additional suggestions.

-Regards
Elaine R.
National Instruments
http://www.ni.com/ask

[Martin.D]

Correct TestStand was running continuously for about 30 days. Then:

1. TestStand was closed.
2. TestStand was launched to run some other sequences.
3. TestStand was closed.
4. Tried to launch TestStand to run the sequence that had run for 30 days. The error occurred and TestStand failed to launch.

That was on one system (NT4), on the other system (2K) the error occurred after some debugging via CVI crashed and the system was re-booted.

Thanks for the information I'll investigate these areas, try to recreate the problem, and let you know what I find.