vCenter Server fails to start when Symantec Endpoint Protection is installed

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• You cannot access vCenter Server when Symantec Endpoint Protection is installed on the same server.
• VMware VirtualCenter Server services do not start.
• In the %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs\vpxd.log file, you see entries similar to:
  
  
  <time> [09464 error 'Default' opID=3ef53819] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (42000) - [Microsoft][SQL Server Native Client 10.0][SQL Server] " is returned when executing SQL statement "UPDATE VPX_SDRS_STATS_VM WITH (ROWLOCK) SET QUANTILES = ? , SPACE_STATS = ? WHERE VM_ID = ?"</time>

Environment

VMware vCenter Server 4.1.x
VMware vCenter Server 5.0.x
VMware vCenter Server 6.0.x
VMware vCenter Server 5.1.x
VMware vCenter Server 5.5.x
VMware vCenter Server 4.0.x

Cause

This issue is caused by port conflicts when both programs are installed with the default port configuration.

Specifically, port conflicts could affect these ports:

• 80
• 443
• 1433
• 8005
• 8045
• 8443
• 9090

For a complete list of port usage by Symantec Endpoint Protection, see the Symantec Knowledge Base article TECH163787.

Note: The preceding link was correct as of August 12, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.

For more information on VMware component port usage, see TCP and UDP Ports required to access vCenter Server, ESXi/ESX hosts, and other network components (1012382).

Resolution

To resolve this issue, either uninstall Symantec Endpoint protection or run the vCenter Server installer to change the default ports used.

Additional Information

TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components