-18002 error after Labview 7.1.1 upgrade

[SAS]

Hi All,

It seems like LV 7.1.1 upgrade is very dangerous when you use with Teststand. The existing system runs fine with LV 7.0 and TS 3.1. Now we have upgraded to LV 7.1.1. The LabVIEW adapter was set as LV 7.0 runtime engine previously. Now I could see only LV 7.0 and LV 7.1 even after I upgraded to LV 7.1.1. I have mass compiled my source code folder and also LV 7.1 folder. But I couldn’t see LV 7.1.1 listed in the runtime engine adapter list.

I could see some support link which explains about the registry changes (copying LV 7.1 (runtime) key to LV 7.1.1 (runtime)).  After doing so, I could see LV 7.1.1 in the adapter list. But then it is of No use. As even if I select the LV 7.1.1 runtime engine as my adapter, it changes back to LV 7.1 run time engine (when I check the adapter option again). It gives error when we run with LV 7.1 runtime engine.

I have attached the sample error message!

Thank you,

Sasi

[SAS]

Hi - its me again!

As the message size was limited - i am sending the addiitonal information below! I forgot to attach the error image in my previous message - it is attached along with this message.

My problem is, we have created few custom step types using LV. Those step type calls are giving errors while executing the code. We have compiled all those step types code also.I could see few other programmers also suffering with the same issue – does anyone know any solution to the problem!!! A real quick fix will be very helpful to us; else we may have to switch back to LV7.1 version!

[Schwede]

Hello,

i have the same problem updating LV under Teststand. Try to update the runtime engine on the 7.1.1 Version and masscompile (it is an function in LV and it opens and save all vi`s) all vi´s.

That help´s me.

Hope i could help you.

Greetings

Schwede

[DWeiland]

Hi Sasi,

Can you check and make sure the path to the runtime engine in your registry key is set?

Under your registry key (run regedit from the Start menu to access) go to:

 HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW Run-Time\7.1

In the "path" folder in the right window pane, make sure that C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\7.1 is the current value. Despite the fact that the path is pointing to 7.1 - that is where the 7.1.1 runtime engine is stored.

Let us know if this doesn't work Sasi, thanks!

Dan Weiland
Applications Engineer
National Instruments

[SAS]

Hi DWeiland and Schwede,

Thanks for your replies. Yes I did the runtime engine registry change and also mass compiled the LV7.1 folder and my sourcecode. I still see the problem as I have set the LV adapter as Lv 7.1.1 runtime engine. Now I have changed it to LV7.1 development system. With this setting, it is not giving any error. Thus I don’t see any problem now. The older version of the code had the adapter as the runtime engine for some reason, now I have changed the setting to the development system. I hope that it shouldn’t be a problem.

Thanks again!

Thank you,

Sasi