Unable to start the VMware VirtualCenter Management Webservices after upgrading to vCenter Server 4.x or later
search cancel

Unable to start the VMware VirtualCenter Management Webservices after upgrading to vCenter Server 4.x or later

book

Article ID: 319654

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • You are unable to start the VMware VirtualCenter Management Webservices after upgrading to vCenter Server 4.x or vCenter Server 5.x.
  • The VMware VirtualCenter Management Webservices starts and stops repeatedly.
  • If you try to start the service, you see the error:

    VMware VirtualCenter Management Webservices stopped with a particular service error 0 (0x0)
     
  • The Tomcat service log (located at %Program Files%\VMware\Infrastructure\tomcat\logs) contains entries similar to:

    [11:47:06] [info] Procrun (2.0.3.0) started
    [11:47:06] [info] Running Service...
    [11:47:06] [info] Starting service...
    [11:47:07] [info] Error occurred during initialization of VM
    [11:47:07] [info] Could not reserve enough space for object heap
    [11:47:07] [info]
    [11:47:07] [395 javajni.c] [error] CreateJavaVM Failed
    [11:47:07] [992 prunsrv.c] [error] Failed initializing java C:\Program Files\VMware\Infrastructure\tomcat\bin\bootstrap.jar
    [11:47:07] [1260 prunsrv.c] [error] ServiceStart returned 2
    [11:47:07] [info] Run service finished.
    [11:47:07] [info] Procrun finished.

     
  • Accessing the Performance Overview tab fails for the vSphere Client.
  • When attempting to access the Performance Overview tab in the vSphere Client, you see the error:

    You don't have permission to access <servername:port>


Environment

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

Cause

This issue may occur if the Apache TomCat service memory pool parameter is too high.

Resolution

To resolve this issue, change the value of the memory pool parameter.

To change the value of the memory pool parameter:
  1. On the vCenter Server system, navigate to Start > Programs > VMware > VMware Tomcat > Configure Tomcat.
  2. Click the Java tab.
  3. Change the maximum memory pool parameter in the configuration utility from 1024 MB to 512 MB.
  4. Click OK.
  5. Restart the VMware vCenter Web Service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

    Note: For information on configuring Tomcat server settings in vCenter Server 5.1, see Configuring Tomcat server settings in vCenter Server 5.1 (2021302).


Additional Information

Configuring Tomcat server settings in VMware vCenter Server 5.1 and 5.5
vCenter Server 4.x 以降へのアップグレード後に VMware vCenter Web サービスを開始できない
无法在升级到 vCenter Server 4.x 或更高版本后启动 VMware VirtualCenter Management Webservices
VMware vCenter Server Service fails to start with the error: "Error 1075: The dependency service does not exist or has been marked for deletion"
The VirtualCenter Server service fails to start with alarm errors after upgrading to vCenter Server 5.0
Troubleshooting VMware Horizon HTML Access