Lost of manager number

[eMichx]

Hello,

Could you help me on the following problem on WinCC OA V3_17P4 (Windows Server 2019 STD) :
Sometimes, a manager is restarting with a wrong number (different from the one defined in prog file), and due to the fact the number is already used by another manger, there's a conflict and it's not possible for the manager to restart.

extract from PVSS_II.log:
WCCOAopcsrv (2), 2020.12.05 03:07:56.786, PARAM,WARNING, 54, Unexpected state, OpcDASrvDPHotlinkWFA, doHotlink, CNSViews has been changed when server was started in DP Groups mode. OPC Server restart is required to use the CNS configuration!

WCCOAopcsrv (2), 2020.12.08 02:11:34.689, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 2), Connection reset by peer (10054)
WCCOAopcsrv (2), 2020.12.08 02:11:34.689, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Event -num 0 CONN: 2), Connection reset by peer (10054)
...
WCCOAopcsrv (1), 2020.12.08 02:13:49.021, SYS, INFO, 1, Manager Start, PROJ, RECOM, V 3.17 - 3.17 platform Windows AMD64 linked at May 14 2020 11:33:29 (aabbb06530e)
WCCOAopcsrv (1), 2020.12.08 02:13:49.162, SYS, INFO, 3, Trying to connect to (SYS: 0 Data -num 0 CONN: 1) @ RESRVT1:4897$RESRVT2:4897
WCCOAopcsrv (1), 2020.12.08 02:13:49.193, SYS, INFO, 4, Connected to (SYS: 0 Data -num 0 CONN: 1) @ RESRVT1 (128.5.0.3)
WCCOAopcsrv (1), 2020.12.08 02:13:49.207, SYS, SEVERE, 229, The Manager MAN: (SYS: 1 Data -num 0 CONN: 1) is already running at host localhost.

Extract from Prog:
...
WCCOAopcua | always | 30 | 2 | 2 |-num 1
WCCOAopcsrv | always | 30 | 2 | 2 |-num 2
WCCOAsnmp | always | 30 | 2 | 2 |-num 2
...

If I use useLocalIdentification (set to 1), do you think this problem will not occur anymore?

Best Regards
Emmanuel

[leoknipp]

The option useLocalIdentification = 1 will not solve the problem.
From the log file we cannot see if the OPC server was restarted by the Process Monitor or not.
Possibly the WinCC OA OPC server was restarted by the OPC client and therefore the manager number does not match the progs file.

Best Regards
Leopold Knipp
Senior Support Specialist

[eMichx]

Thanks Leopold for your analysis,

Is there any possibility even if the OPC client restart the OPC server, to force the manager number?

Best regards
Emmanuel

[leoknipp]

I do not know a possibility to define a manager number if the OPC server is restarted by the client.
Normally it takes some time ( a few seconds) before the OPC client detects that the connection is lost and to restart the OPC server.
Please check the log files to see why the OPC server was not restarted by the Process Monitor.

Best Regards
Leopold Knipp
Senior Support Specialist

[gschijndel]

At the OPC HDA server configuration there are instructions for defining a specific manager number. With some slight modifications these instructions should work for the OPC DA server.

See in the documentation under: Drivers -> OPC Historical Data Access -> Configuration of the OPC HDA Server -> Starting the OPC HDA Server -> NOTE

[eMichx]

Thank you, I will change registry and change also the DCOM configuration for activation and execution attributes

regards
Emmanuel

[leoknipp]

The WinCC OA OPC DA client offers the possibility to define if the client shall be able to restart the OPC server.
Maybe the OPC client you are using has a similar configuration option.

Best Regards
Leopold Knipp
Senior Support Specialist