Skip to main content
10-Marble
July 23, 2024
Question

2 Kepserver connected to 1 OPCServer.WinCC.1

  • July 23, 2024
  • 1 reply
  • 2480 views

Hi, 

I want to migrate a server. I have 3 servers in the same domain

 

1 server for WinCC SCADA I'll call A

Server B is the standby Server now and is connected to WinCC Server A with OPC DA.

 

and now I want to migrate Kepserver from B to C.

 

I tried connecting Server C with Server A WinCC (OPCServer.WinCC.1) while Server B was still connected to Server A.

 

the entire setup is the same as server B.

and, from server C, I can scan all tags from server A WinCC

RM_10318757_0-1721765753643.png

but it takes 1-2 minutes for this pop-up appear.

 

when I try to open quick client, the quality is always bad, and sometimes "out of service"

and there is a message said "Failed to establish callback......"

Screenshot 2024-07-24 032529.png

 

Is there a possibility that the WinCC Server from server A can only connect to 1 Kepserver with OPC DA?

RM_10318757_1-1721765899828.png

 

1 reply

13-Aquamarine
July 25, 2024

@RM_10318757 

 

It sounds like you are up against Microsoft security called DCOM. You might have to reach out to WinCC support to see if there are any limitations that could prevent multiple connections, but it feels like DCOM is the issue. Here is a link to the Kepware knowledge base article on resolving Microsoft DCOM issues. 

 

https://www.ptc.com/en/support/article/CS293793

 

Thanks,

*Chris 

10-Marble
July 25, 2024

I have already tried to set up the DCOM  and create the same 1 user in the same group on each server (the same user, Anonymous logon, everyone, guest, interactive, network, and system). but still, the issue still happens.

 

 

13-Aquamarine
July 26, 2024

@RM_10318757 

 

It is possible the WinCC application only supports a single connection, and you may need to contact their support for verification.  As a test can you disconnect the connection to "KEPServerEX1 and attempt the connection to KEPServerEX2? If the single connection to KEPServerEX2 still fails, then it is most likely a DCOM issue. 

 

Thanks,

*Chris