Handling error -1950679023

[Jason Stallard]

I searched the boards re: error -1950679023 and have not been able to find any conclusive reasons why a connection
would be closed..specifically when using localhost.

I also wasn't able to find any stratagies to deal with this error other than using development system tools such as the
variable manager.  However in my case, this is a stand-alone application so the users do not have access to the
development system tools.

Can anyone recommend what actions should be taken when error -1950679023 is encountered?  How does one re-establish
a connection with the PSP server programatically?  Re-deploy the library? Some invoke method call?

Thanks for any input

-Jason

[Nick R]

Hi Jason,

What version of LabVIEW are you using, and are you using the DSC module? Also, you said you're using localhost, so are these network-publised shared variables, or single process?

There is this knowledge base article that specifically discusses this error and the shared variable engine going down.

What Happens When my Shared Variable Engine Goes Down Unexpectedly?

Another thing you can check is in your Windows task manager, on the processes tab, check to see if the tagsrv.exe process is running. If you do not see this process then your shared variable engine is not running.

I hope this helps!

[Jason Stallard]

I'm running LV8.0.
No, I'm not using the DSC module.
Yes, these are Networked variables(PSP).
I'm primarilly using networked variables to bind front panel controls.

What I'm trying to figure out is when this application is in a compiled application
running an a user's machine, how does one recover from this error?  I've
not been able to find anything useful other than using certain tools the user
wouldn't have available.  I need to be able to handle this programmatically within
the .exe

[Nick R]

I've seen a lot of cases where this error is caused by a lost network connection. I would make sure you're not losing your connect, check your firewall, etc. Also, does this error happen on a consistant basis or just randomly? Have you tried running this .exe on another computer? Do you get this error when you are running VI's on your development machine?

There is also this knowledgebase on the website that discusses deploying shared variables in executables. You might try redeploying using the application invoke node as discussed in the knowledgebase. Good luck!

How Do I Deploy Network Shared Variables From a Compiled Executable?

[Mirash]

Hi all,

I also getting the same kind of error. The Shared Variable Engine Goes Down Unexpectedly. Can anybody tell me a way to sort out this problem. I am using Labview 8.2.1 and DSC 8.2.


Mirash

[Ray.R]

Did you read the Knowledge Based articles that Nick posted?

R

[Mirash]

Hi,

I understood what will happen when the Shared Variable Engine Goes Down Unexpectedly?. But i didnt find a solution to prevent the Shared Variable Engine from going down or crashing.


Blackperl

[jpaul]

Blackperl,

I wanted to follow up regarding your variable engine going down unexpectedly. Could you elaborate on the scenario in which your shared variable engine goes down? Does it go down always at a specific interval (after a few hours of running)? Does it go down when you start running a specific executable or part of your application? Can you confirm that you network connection is not being disconnected (as is commonly the case when this error occurs)? Any information to reproduce the issue would be helpful. Thanks.

Cheers,

Jonah
Applications Engineer
National Instruments

[Mirash]

Hi Jonah,

Actually i re-installed the LabVIEW since i was not having enough time to focus on the problem. I was able to run the same code in different PC without any problem. But i can tell you the scenarion where i got this problem. I have one set of library in My PC which i was updating continuously by opening PSP data socket connection. When i open the data socket connection, initially it was not giving any error and i was able to update the data. But when i aborted the program and run again, the Data Socket Open connection was giving timeout error 56 or error -1950679023. Then if i am waiting for some time or restart LabVIEW i was able to open without error. Sometime even restarting LabVIEW also was not effective. I dont remember the time intervel. If i am observing the same behaviour again, defenetly i will track it systematically and post it here.Sorry for disappointing you.

Blackperl

[mikeporter]

If you can't figure out what the problem is, it might be time to be looking at a different approach to the same basic tasks. You can also use VI Server (a very mature technology) to pass data between different LV-based applications running on different machines. Simply create a functional global and write to it from one machine and read it from the other...

Mike...