LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

error 1950679035

hello matt,

 

yes i have removed the old library ... infact deleted from the system itself.

 

Regards,

Ramji

0 Kudos
Message 11 of 14
(3,449 Views)

LabView 8 doesn't find the shared variables by name. This can cause the error code 1950679035, when you have several shared variable libraries with the same name , in different file folders.

If you click a sv with richt mous click and select visible items -> label , then only a project explorer like path is shown, instead of an absolute path. Thats why references of sv may be errouneous.

 

The solution is to write the absolute path to the sv programmatically or by any ini file. As far as I know this is not yet possible in LV8.

 

DG3005

0 Kudos
Message 12 of 14
(3,449 Views)
Note  If you deploy a network variable to a Windows machine with the Windows firewall enabled, you must add \National Instruments\Shared\Tagger\tagsrv.exe and \windows\system32\lkads.exe to the Windows firewall exception list in order to read or write to the variable hosted on the machine.
 
This shoiuld be included in the PDA module step through guide on configutring firewalls with shared variables
0 Kudos
Message 13 of 14
(3,356 Views)
Monkins,

Thanks for that feedback.  I'll see what I can do to get that document updated.

For the meantime if anyone else encounters issues with Shared Variables when using a Windows XP SP2 or Windows Vista please follow the instructions found here:

KB 3HUD6PUW: Setup LabVIEW, LabVIEW DSC, and Lookout to Work with the Windows Firewall

Regards,

Simon H
Applications Engineer
National Instruments
http://www.ni.com/support/
0 Kudos
Message 14 of 14
(3,339 Views)