Connecting 3.14 to third party remote OPC server

[hotze.brons@strukton.com]

Hello,

I'm trying to connect WinCC OA 3.14 OPC client to a third party OPC server which is running on a remote PC. In the [OPC] section of the config file I use the following entry...
server="Klantnaam" "SC_Klantnaam/Softing.OPC.S7.DA"

WinCC OA log shows the following massages

WCCOAopc (1), 2016.05.19 16:54:43.089, SYS, WARNING, 54, Unexpected state, OPCGroup, groupGA, Could not start Refresh on Appendage:Niet nader omschreven fout (0x80004005)
WCCILpmon (1), 2016.05.19 16:54:45.730, SYS, INFO, 9/pmon, The project is up and running. Entering monitor mode
WCCOAopc (1), 2016.05.19 16:54:47.386, IMPL, SEVERE, 54, Unexpected state, OPCServer, initialize, CoCreateInstanceEx: could not connect to Softing.OPC.S7.DA at SC_Klantnaam
WCCOAopc (1), 2016.05.19 16:54:59.105, IMPL, SEVERE, 54, Unexpected state, OPCServer, initialize, CoCreateInstanceEx: could not connect to Softing.OPC.S7.DA at SC_Klantnaam


DCOM recieves errorcode 2147746132 from SC_Klantnaam


I also tried to connect an third party OPC client to the same third remote party OPC server. And that works!

What do I do wrong in WinCC OA??

Thanks in advance. Kind regards,
Hotze Brons

[hotze.brons@strukton.com]

By the way...

Connecting to the same OPC server on the local machine works using the following entry in the OPC section of the config-file

server="Klantnaam" "Softing.OPC.S7.DA"

Have a nice weekend!

[leoknipp]

Hello,

when using a Remote-OPC-connection you have to ensure that the DCOM settings are correct.
Please have a look at the WinCC OA documentation.

If possible the usage of DCOM shall be avoided.
If the OPC server must run on the other computer you have the possibility to use a WinCC OA remote driver project where the OPC client is running on the same machine like the OPC server.

Best Regards
Leopold Knipp
Senior Support Specialist

[hotze.brons@strukton.com]

Thank you. To be continued...