vCenter Server fails with the error: Failed to initialize: vim.fault.ConcurrentAccess

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

When vApp is implemented on vCenter Server 4.1, you experience these symptoms:

• vCenter Server fails with the error:
  
  Failed to initialize: vim.fault.ConcurrentAccess
  
  
• In vCenter Server logs, you see entries similar to:
  
  [2011-01-15 09:44:12.703 02436 trivia 'VpxProfiler'] Ctr: TotalTime = 48859 ms
  [2011-01-15 09:44:12.703 02436 warning 'VpxProfiler'] ServerApp::Init took 48859 ms
  [2011-01-15 09:44:12.703 02436 error 'App'] [VpxdMain] Failed to initialize: vim.fault.ConcurrentAccess
  [2011-01-15 09:44:12.703 02436 error 'App'] Failed to intialize VMware VirtualCenter. Shutting down...
  [2011-01-15 09:44:24.640 02436 trivia 'App'] [Vdb::Connection::Release] Transaction took 60031 ms with 0 statements
  [2011-01-15 09:44:24.640 02436 verbose 'App'] Successfully unlocked VC repository
  [2011-01-15 09:44:24.640 02436 info 'App'] Forcing shutdown of VMware VirtualCenter now

Environment

VMware vCenter Server 4.1.x

Cause

This issue occurs if vApp has virtual machines that are invalid or in an inconsistent state.

Resolution

This issue is resolved in vCenter Server 4.1 Update 2 and vCenter Server 5.0.