Open datasocket connection error 42

[Pataclaque]

Hello,

When I run my application as a standalone appliation I get error 42 from the "Open Datasocket Connection" VI, I was able to see it using the "Enable debbuging" feature in the build specification.  When I run my application in source code I don't have any problems with the "Open Datasocket Connection".  The address provided is the exact same address for the standalone executable and the source code which points to another computer LabVIEW application.  The protocol I'm using is psp://ComputerName...

Any ideas?

Michel

[wiebe@CARYA]

Firewall?

[Pataclaque]

I've disable everything I could.

[wiebe@CARYA]

Are you able to read at all? E.g. does the error happens sometime, or everytime?

[wiebe@CARYA]

It could be a problem that the executable cannot access the registery. That seems to be needed for Datasocket. Does it work when you start the application as administrator?

Btw. Why do you use Datasocket to read a psp variable? You should be able to use Open Variable Connection I think? Datasocket is almost obsolete.

[eaguero]

Hi Patacle,

What are you doing with the DataSocket? An OPC server (Tags) for example?

Thanks

[Pataclaque]

I'm using the "Open Datasocket Connection" to connect to a shared variable hosted on the remote computer.  By the way, this has worked in the past but I had to re-install Windows OS and LabVIEW on the "remote" computer.  So it it is probably due to something related to firewall, but like I said I think I have disabled everything...

[wiebe@CARYA]

Sounds like a DCOM issue. I think shared variables use OPC as underlying layer.

If the OS of the server PC causes the client PC to fail (in an exe, but not in LV), it must be some OS rights issue.

I'd still try to use Open Shared Variable, and Read Shared Variable. It should be easy.

[Pataclaque]

Hello,

Windows 8 is installed on the remote computer, what would be the steps in order to determine what is blocking the "Open Datasocket Connection" (with the executable) to that remote computer?

Thanks,

Michel

[wiebe@CARYA]

Have you tried to run the exe as administrator?

OPC\DCOM access rights are terrible to get working. Usually, giving everybody rights to everything is the only solution.