LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

The shared variable does not exist????

This is really amazing!!!
 
I've called NI and explained the whole issue and they couln't give me a solution yet!
 
What we have discovered so far is:
1) All the current shared variables work just fine;
2) If I create any new shared variable and try to access it on my host VI it generates that error;
3) If I delete one of my current ones, create another one exactly like it (inside the same library), and try to use it I also get the error.
 
JLS, all my shared variables have the "description" setting disabled. I really don't think the problem is related to this...
 
So, if you guys have any other suggestion (besides reinstalling the whole software!), please let me know, ok?
 
Thanks a lot for the help!!
 
Daniel
0 Kudos
Message 11 of 16
(1,473 Views)
Hello,
 
Yep, this is strange, but it's not time to give up 🙂  I have a few questions as we move forward:
 
1. Can you confirm that tagsrv.exe is running on your machine (ctrl+alt+delete and see the process list in Task Manager)? 
2. Can you zip your project, or preferably a watered down version of it which reproduces the problem, so I can see if the problem follows your project to another machine? - it would be really nice if you can get this down to a single project - single VI - single library - single variable scenario.
3. You noted this problem occurs when you create new variables - is this confined to a specific library or a particular project, or is this ANY shared variable created in the LabVIEW environment?
 
Anyway, sorry you're seeing such a nasty problem - I look forward to hearing back from you!
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
0 Kudos
Message 12 of 16
(1,451 Views)
Hi

I´m also facing the same problem and it happens even if I started a new project with a new library ...

0 Kudos
Message 13 of 16
(1,322 Views)
Hi,
I got the same problem some time ago and it was related to the fact that app was reading or writing to fast. Try to slow down the read or write part of your code and see what is going on.
cosmin
0 Kudos
Message 14 of 16
(1,321 Views)

Hi,

I am developing a client-server application on my windows PC with Labview 8.21 using shared variables. (also deploying with the invoke node function)

I have experienced error -1950679035 (0x8BBB005) many times in different occasions ,mostly my fault,.....DCOM wrong settings, Variable Manager hangs, wrong "bind to source" item selected (network item DIO in sted of project item shared variable), sometimes <populating node> appaeared with no items to select, running my client application before running the host application.....and the bad thing about this error, it latches!! and can only be cleared by restarting the SVE in "services". Restarting Labview and my application does not clear this error.

After many days I found that there is a problem with the starting of the SVE at first power-up of my PC.(auto start at power-up)

The SVE runs at power-up but needs to restart again in services. After this I can start my client before starting my host with programmatically clearing the error. At last this problem is solved. Stepping to the next one.....

Maybe there is a sort of dependancy problem at first power-up?

Greatings,

Frank.

0 Kudos
Message 15 of 16
(1,176 Views)

Hi Frank,

I am having the same problem with Error -1950679035. But cant seems to find the solution. I am using LV8.6.

May i ask the following based on your previous experience;

1. what do you mean by DCOM wrong setting?

2. Do i need to include NI Variable Manager in the Build Specification/My Installer Properties/Additional Installers when building exe file?

    Is the NI Variable Engine not enough?

3. Where can I find SVE to re-start it and clear it from errors?

4. How did you programmatically clear the error? Is it possible to see a sample VI.

5. Do I really need to create invoke node function? Is making the Shared Variable Library.lvlib in Autodeploy Variables not enough?

 

Thanks a lot. I would appreciate for any help as i cant really find why i get the above error.

 

regards,

0 Kudos
Message 16 of 16
(874 Views)