Community

I have this issue where sometimes, the WCCILproxy (Multiplexing Proxy manager) fails to start whenever my WinCC OA project is restarted. Most often this is when the project is running as a Windows Service and the service restarts or when the project gets restarted due to a needed restart when using the Split-mode or other dist/redu mechanisms that warrant a project restart.

The relevant logs I'm getting are the following:
```
PROJ_SERVICE (1), 2025.11.17 13:11:16.602, SYS, INFO, 1, Manager Start, "C:\Siemens\Automation\WinCC_OA\3.20\bin\WCCILproxy.exe" -PROJ "MyProj" -pmonIndex 4
WCCILproxy (1), 2025.11.17 13:11:25.667, SYS, INFO, 220, Multiplexing proxy Start, PROJ, MyProj, V 3.20 - 3.20 final platform Windows AMD64 linked at Jul 9 2024 21:27:30 (5a83340193)
WCCILproxy (1), 2025.11.17 13:11:25.673, SYS, FATAL, 197, Endpoint could be not created., fd = -1, code = 6, errno = [10048] Only one usage of each socket address (protocol/network address/port) is normally permitted.
PROJ_SERVICE (1), 2025.11.17 13:11:25.851, SYS, INFO, 11/pmon, Detected stopped manager WCCILproxy(1) - restarting it #1
PROJ_SERVICE (1), 2025.11.17 13:11:25.853, SYS, INFO, 1, Manager Start, "C:\Siemens\Automation\WinCC_OA\3.20\bin\WCCILproxy.exe" -PROJ "MyProj" -pmonIndex 4
WCCILproxy (1), 2025.11.17 13:11:34.923, SYS, INFO, 220, Multiplexing proxy Start, PROJ, MyProj, V 3.20 - 3.20 final platform Windows AMD64 linked at Jul 9 2024 21:27:30 (5a83340193)
WCCILproxy (1), 2025.11.17 13:11:34.929, SYS, FATAL, 197, Endpoint could be not created., fd = -1, code = 6, errno = [10048] Only one usage of each socket address (protocol/network address/port) is normally permitted.
PROJ_SERVICE (1), 2025.11.17 13:11:35.095, SYS, INFO, 11/pmon, Detected stopped manager WCCILproxy(1) - restarting it #2
PROJ_SERVICE (1), 2025.11.17 13:11:35.097, SYS, INFO, 1, Manager Start, "C:\Siemens\Automation\WinCC_OA\3.20\bin\WCCILproxy.exe" -PROJ "MyProj" -pmonIndex 4
PROJ_SERVICE (1), 2025.11.17 13:11:37.910, SYS, INFO, 12/pmon, Manager WCCILproxy(1) restarting too rapidly - giving up restarting
```

When looking in Task Manager, I see there are two instances of "WCCILproxy.exe" running. I guess these are the instance from the project "session" that has just been stopped and the instance of the new project "session". The old one is still occupying the proxy port, which results in the new one not being able to restart.

I have also observed that when stopping the project, the WCCILproxy manager is (almost) always the last manager to terminate/stop. It stops after the data and event managers are stopped, which is logic in a way. I don't know what the trigger is when the project is allowed to restart when restarting the Windows Service, but it seems like the project is restarted before the proxy manager had had time to shut down.

Does anyone has encountered this problem?
Is there some config entry that can tweak this behaviour?