无法在升级到 vCenter Server 4.x 或更高版本后启动 VMware VirtualCenter Management Webservices

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:
免责声明：本文为 Unable to start the VMware VirtualCenter Management Webservices after upgrading to vCenter Server 4.x or later (1011648) 的翻译版本。尽管我们会不断努力为本文提供最佳翻译版本，但本地化的内容可能会过时。有关最新内容，请参见英文版本。

---

• 无法在升级到 Center Server 4.x 或 vCenter Server 5.x. 之后启动 VMware VirtualCenter Management Webservices。
• VMware VirtualCenter Management Webservices 会重复启动和停止。
• 如果尝试启动服务，您会看到以下错误：
  
  VMware VirtualCenter Management Webservices stopped with a particular service error 0 (0x0)
  
  
• Tomcat 服务日志（位于 %Program Files%\VMware\Infrastructure\tomcat\logs 中）包含类似于以下内容的条目：
  
  [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.
  
  
• 访问 vSphere Client 的“性能概览”选项卡失败。
• 尝试访问 vSphere Client 中的“性能概览”选项卡时，您会看到以下错误：
  
  You don't have permission to access <servername:port>

Environment

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

Resolution

要解决此问题，请更改内存池参数的值。

要更改内存池参数值，请执行以下操作：

1. 在 vCenter Server 系统中导航到启动 > 程序 > VMware > VMware Tomcat > 配置 Tomcat。
2. 单击 Java 选项卡。
3. 将配置实用工具中的最大内存池参数从 1024 MB 更改为 512 MB。
4. 单击 OK。
5. 重新启动 VMware vCenter Web Service。有关详细信息，请参见 Stopping, starting, or restarting vCenter services (1003895)。
   
   注：有关配置 vCenter Server 5.1 中的 Tomcat 服务器设置的信息，请参见 Configuring Tomcat server settings in vCenter Server 5.1 (2021302)。

Additional Information

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