Troubleshooting: Port 8005 conflict with SCCM "Express Updates"
Issue(s)
The “CoreOne Suite - Core” service does not start or - even worse - continuously restarts. Evidence of such behavior can only be found in:
Event-Viewer -->
Unable to bind to the underlying transport for [::]:8005. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.
Log file of the “CoreOne Suite - Core” in c:\programdata\itsense\log
2025-03-25 15:57:07,601 [GlobalEventManager_start] ERROR iTsense.Moving.Backend.ServiceRunner.Manager.WcfService [(null)] - Error starting Service GlobalEventManager System.ServiceModel.AddressAlreadyInUseException: The TransportManager failed to listen on the supplied URI using the NetTcpPortSharing service: the service failed to listen.
You can check which service is using which ports with the following powershell command:
netstat -ao
If port 8008 and port 8005 are taken by process-id 4 (=Operating System), then the “CoreOne Suite - Core” can’t start.
Cause(s)
Port 8005 is often used by SCCM (Microsoft System Center Configuration Manager) in combination with Windows-Update: https://learn.microsoft.com/en-us/intune/configmgr/core/clients/deploy/about-client-settings#port-that-clients-use-to-receive-requests-for-delta-content
Port that clients use to receive requests for delta content
This setting configures the local port for the HTTP listener to download delta content. It's set to 8005 by default. You don't need to open this port in the client firewall.There are a few conditions that are being checked before a resource assignment is actually provisioned.
Solution(s)
The Windows-Service "SMS Agent Host" takes Port 8005. You can define a dependency for this service, that it starts AFTER the "CoreOne Suite - Core" as follows:
The "SMS Agent Host" service will then use another Port.
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.