NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Error -17003 after upgrading to LV 7.1.1

Hello everybody,

i´m using Teststand 3.1 and Labview 7.1 which is now updated to 7.1.1.
When running a teststep which has an errormessage in the error-output-parameter then the Teststand-RunTimeError-Errorbox says:

Details: Parameter ´Error´
LABVIEW version ´7.1.1´ is not installed.

Errorcode:
-17003; An item could not be found in system registry.

But this is not the message which is in the parameter.
All VIS are mass-compiled to 7.1.1.

What is wrong here?

Thanks for any ideas.
0 Kudos
Message 1 of 4
(3,433 Views)
You can reproduce this error by doing this steps:

-Open Teststand 3.1 with a new testplan
-Rightclick an insert "Action"
-Select "create VI" and type a name
-in the new created VI go to to error-out and "create constant" to the error-out.
- Make the constant "True", Code "123" and string "abc"
-Save the new created VI and close it
-Back in Teststand, rightclick the new teststep and select "run selected steps"
-Now the "Rumtime-Error-Box pops up.
-But there is not the code/string inside which was just typed in the constant.
0 Kudos
Message 2 of 4
(3,410 Views)
Hi Panastra,
There is a work around for this problem. All you have to do is create a new registry key.
This is what you need to do:
1. Export the registry key HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW Run-Time\7.1 to a file (called it something like LabVIEWRT71.reg)
2. Rename the registry key above to HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW Run-Time\7.1.1.
3. Import the registry file you create in step 1 (Import LabVIEWRT71.reg).

This work around should fix the problem.

The problem only appears when the LabVIEW adapter is configured to use the LabVIEW Development System and the VI returns an error in its error out cluster. If the LabVIEW 7.1 Run-Time Engine is used, the problem will not appear.

The problem will be fixed in a future version of TestStand. It is unfortunate that a work around is needed.

Regards,
Jose
Message 3 of 4
(3,390 Views)
Hi Jose,
thanks for your fast help.
After editing the registry no more problems.
0 Kudos
Message 4 of 4
(3,369 Views)