DataSocket and OPC: error 1184

[Christ0phe]

Hello,

We have some issues to connect to an OPC server (Kepware V5 for instance) with a remote computer using Labview 2012 and DataSockets. The case that does not work is when both computers are Windows 7 boxes. The error 1184 comes when we try to open an OPC tag. The DCOM is fully opened on both sides. The Kepware OPC server is configured to allow OPC 1.x, 2.x and 3.x standards. Other OPC clients (Matrikon, Kepware) work well. If we install the OPC Analyzer tool as a 'tunnel' between the Client and the Server, the error 1184 disappear and we are able to read all tags.

1. Do you know which Windows configuration needs to be configured correctly when using Labview 2012 DataSockets ?
2. Do you have a tools to dig into the details of this error 1184 ? We hoped to be able to do this using OPC Analyzer but 'unfortunately' using this tool the error disapprears !
3. Do you know how to fix the issue ?

1st Test:

PC with OPC server in Windows XP

PC with OPC client in Windows 7

Both computers have DCOM fully opened without firewall.

Test with Labview 2012 DataSocket : OK (Open and read tags with no issue)

Test with Kepware client :OK

2nd Test:

PC with OPC server in Windows7

PC with OPC client in Windows 7

Both computers have DCOM fully opened without firewall.

Test with Labview 2012 DataSockets: error 1184 when we try to open a tag. We can see the OPC server and all the tags with the browser but it is impossible to open any of the tags without this error 1184

Test with Kepware OPC client : OK

Test with Matrikon OPC client : OK

3rd Test:

PC with OPC server in Windows7

PC with OPC client in Windows 7

Same computer as the 2d test but using OPC Analyzer (from the OPC foundation, installed on the Client PC) between the OPC server and the client:

Test with Labview 2012 DataSocket: OK

Test with Kepware client : OK

[Tamdemonium]

Hi Christ0phe -

I just want to clarify some things about your setup:

1. Are you using the same bit OS? (So running from a 32-bit to a 32-bit Windows OS?)
2. Are you using any of NI's OPC products? (NI LabVIEW DSC Module or NI OPC Sever?)
3. Are you just using DataSockets to connect the tags between your OPC system?

Here are some responses I have for your questions:

1. There shouldn't be any special configuration for Windows configuration with DataSockets.  This is true for local DataSocket connections.  This may be different for remote connections (see below).
2. As to digging into the error, it seems like it is connected to a network error even with DCOM settings opened on both sides.  We could try to get a Wireshark view of the network traffic that is occurring. 
3. From a brief look around, and under the assumption that you are connecting remotely to your OPC using only DataSockets, I found the following posts:
   Datasocket open fails with 1184 error accessing an OPC server
   and
   Cannot connect to remote Mitsubishi OPC server using datasocket

It looks like it could be an issue with remote access being allowed between Windows 7 machines.  (There were some security changes between XP to 7 so that if you are trying to access the Windows XP machine from a Windows 7 machines, you would notice no issues but would notice issues on the reverse).  OPC Analyzer likely opens the remote access connection but that would be something to check on your machine.

[Christ0phe]

Hi Tamdemonium,

First of all sorry about my late answer but wanted to check everything very thoroughly.

- We use Windows XP and Windows 7 PCs

- We do not use NI OPC Server (only Kepwares') nor DSC modules

- We are just using DataSockets to connect to local and remote OPC tags

As per the advise of 'sletrab's message that you referred to in your email, we noticed that 'Remote Registry' (services.msc) had to be activated on the server's side to make the OPC/DataSocket communication work. Additionally there is also a need to set the two following policies (secpol.msc):

Local Policies/Security Options/Network Access: Let Everyone permissions apply to anonymous users: Enabled

Local Policies/Security Options/Network Access: Sharing and Security model for local accounts: Classic

Anyway thanks a lot and... Kudo to you and sletrab!

Christophe

[Tamdemonium]

Glad to hear that activating the service got you back on track!