Shared Variables stopped working in windows domain

[Florian.Ludwig]

Hi Community,

my company recently switched to a windows domain network, and ever since, I cannot connect to shared variables in a library I deploy.

The deployment of the lvlib gives no error, but open variable connection does give error −1950679035 (Unable to locate the shared variable in the Shared Variable Engine (SVE). Deployment of this shared variable may have failed, the SVE has not started, or the SVE is too busy to respond to this request.). A retry later in the code fails with the same error.

The code had been working for years and is unchanged. I am still attaching it (slightly stripped down, but still producing the error) for your review.

This happens only in the LabVIEW development environment on three machines I tested in on. If I build an executable containing the code it will work on any machine.

I tried to no avail:

making sure the exceptions for LabVIEW are set in the local firewall,

deactivating the local firewall,

making sure the variable service is running,

internet search.

I am convinced this is caused by the change in the network - but I am no IT expert, and thus hope that someone here knows what's going on.

It is probably one little setting I am not aware of.

Best Regards

Florian

[Vazgen_H]

Hello Florian.Ludwig.

I attach some useful links, which can help you to solve this problem. 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PAinSAG&l=en-US

Solved: Error - 1950679035 - NI Community

[Florian.Ludwig]

Thank you for answering.

I received the first link from NI support too, which I also contacted about this.

Here is my step by step progression through the first link:

Cause 1: Does not apply, this is not on Real-Time
Cause 2: Aliasing is disabled
Cause 3: Disabling the Firewall (private and public) did not help.
Cause 4: Running as admin did not help
Cause 5: Does not apply
Cause 6: Not sure if it applies.
I am using code as shown in the snippet to deploy.
Firewall is still off for testing.
OPC service is set to manual and currently not running, so this should be fine.
I only have one NIC.

Cause 7: Manually deploying before running my VI does not help.
Cause 8: Does not apply
Cause 9: Does not apply
Cause 10: Does not apply
Cause 11: I only have one project opened.

The example under additional information does work!

This points to my code or some configuration issue with my projekt maybe?

[Vazgen_H]

I dont know yet what is the problem. But Can you try to open a new project and try to use Network Shared Variables? 

[Vazgen_H]

Sometimes I get errors with shared variables too. The solution for me is to restart the cRIO and PC. Maybe some wrong with cRIO Ip address? Can you check it too?

[Vazgen_H]

Hi, any updates? Does it work?

[Florian.Ludwig]

Hi,

the PCs (it happens on all 3 machines I tried it on) have been restartet multiple times, and there is no cRIO infolved.

I have created a new project, and successfully used Network Share Variables there.

I have also created a new VI in my existing project, and successfully used NSV, even with the old library.

I have tried making a new VI and copying over the old code, just to be sure.

I'm at a loss why the code in my old VI as stopped working.

[Vazgen_H]

As I understand, that's work on all PC's except those 3, right?

[Vazgen_H]

Do you try to do this? 
Error -1950679035: Unable to Locate Variable in Shared Variable Engine - NI

[Florian.Ludwig · Accepted solution]

I've got it!

The switch to domain must have changed something in the underlying language setting of the OS or the network environment.

The constants in the VI I posted are the issue.

If I brose to the variables again the path changes from

ni.var.psp://mein computer...

to

ni.var.psp://my computer...

and then the connection is successful. Now I just need to see if it also works in the executable..