What is the CP_manager::Create_pod_connection() returned code mean?


Article ID: 169116


Updated On:


Web Security Service - WSS


When the Auth Connector failed to connect to ThreatPulse Auth Control Pod, the BCCA debug log generates an event returning error code. For example:

CP_manager::Create_pod_connection() returned 2746, thread_group a21f70

If the Auth Connector can login to the Control Pod successfully, then the debug BCCA log displays a return value of 0 (zero) for this function call:

CP_manager::Create_pod_connection() returned 0



Refer to Microsoft Windows Sockets Error Codes:

Windows Sockets Error Codes



The Auth Connector error code is in HEX. Convert it to DEC and look for error code description in the Microsoft Windows Sockets Error Code page given.

Common errors (but not limited to):

2745 (HEX) = 10053 (DEC)


Software caused connection abort.

An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.

2746 (HEX) = 10054 (DEC)


Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

271D (HEX) = 10013 (DEC)


Permission denied.

An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).

Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.