Overview

The EventsManager 2013 services are not starting, and the splash screen does not go away when launching the console.

From the esmcfgsrv.csv logs, you will see entries similar to the following:

2013-01-30, 19:55:33, 379, 0, 2334, 19cc, error, esmcfgsrv.exe, Main,
Unexpected exception: A TCP error (10013: An attempt was made to access a socket in a way forbidden by its access permissions) occurred while listening on IP Endpoint=0.0.0.0:9090. 2013-01-30, 19:55:33, 379, 0, 2334, 19cc, error, esmcfgsrv.exe, Main,

The stack trace from the cfgconnector.csv logs show entries similar to the following:

2013-01-30, 19:53:48, 314, 0, fc8, 4638, error, CfgConnector.dll, CreateCfgSvcInstance, Inner exceptions are: 2013-01-30, 19:53:48, 315, 0, fc8, 4638, error, CfgConnector.dll, CreateCfgSvcInstance, Stack trace is: 2013-01-30, 19:54:10, 323, 0, fc8, 4638, error, CfgConnector.dll, CreateCfgSvcInstance, Unexpected exception: The server at net.tcp://localhost:9090/CfgSvc rejected the session-establishment request.

Environment

All Builds of EventsManager 2013 

Root Cause

Multiple services are using the same port.

In one identified case, the Symantec Endpoint Protection is using port 9090 for some of its communication, which is the same port being used by cfgsrv.ini, thus causing the conflict.

Resolution

1. Stop all EventsManager related services and processes.
2. Open the cfgsrv.ini file in notepad and change the port 9090 to an unused port, e.g., 9393.
3. If needed, run a netstat (network statistics) on the EventsManager server to determine an available port.
4. Save the changes made in the cfgsrv.ini file.
5. Restart the services. 

Verification

Launch EventsManager console. You should get past the splash screen and start the services.