Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

VMware VirtualCenter Server service fails after upgrading to vCenter Server 4.1 (1026688)

Symptoms

  • The VirtualCenter Server service fails after upgrading to vCenter Server 4.1.
  • You see this error in the vpxd logs:

    Panic: Win32 exception: Access Violation (0xc0000005)
       Read (0) at address 0000000000000098
       rip: 000000014071edcc rsp: 000000000419c700 rbp: 000000000419e160
       rax: 000000000419c7a8 rbx: 0000000000000018 rcx: 0000000000000020
       rdx: 000000000419c798 rdi: 0000000000000000 rsi: 000000000e8667b0
       r8:  000000000419c7a8 r9:  000000000cab1eea r10: 0000000002d27fd0
       r11: 000000000419c750 r12: 0000000007279700 r13: 0000000007279740
       r14: 00000000032edeb0 r15: 0000000000000004

    Note: For more information about the vpxd logs, see Common vCenter Server and vSphere Client Windows paths (1028185).
  • In vCenter Server 4.0, operations such as Inventory > Search fails. The vws.log file truncates with a Chunked stream ended unexpected error
  • In vCenter Server 4.1, vCenter Server 4.1 fails immediately after it is started and the vpxd-*.log shows an ASSERT fails at one of the following:
    • ASSERT d:/build/ob/bora-258902/bora/vpx/vpxd/util/vpxdDbLoad.cpp:1059
    • ASSERT d:/build/ob/bora-258902/bora/vpx/vpxd/util/vpxdDbLoad.cpp:1066


Resolution

This issue is resolved in vCenter Server 4.1 Update 1 and vCenter Server 4.0 Update 3.
 
For vCenter Server 4.1, this issue is caused by corrupt entries for the virtual machine in the vCenter database.

Caution: This article deals with SQL database operations. Before proceeding, ensure that you are familiar with database concepts and that you have adequate backups.
 
If you have upgraded to vCenter Server 4.1 and the server keeps failing:
  • Roll back to vCenter Server 4.0. Connect vCenter Server 4.0 to the backup database.
  • Follow the resolution steps mentioned below
To avoid encountering this issue:
  1. Download the appropriate script for your environment. The scripts are attached to this article (located in the Attachments section at the bottom of this article).
  2. Unzip the scripts.
  3. Run the scripts on vCenter Server 4.0 database.

    Note: The SQL query must be run with fully qualified database table names. If you have multiple database instances, there may be a need to qualify the tables with the db-instance name and the db-owner name.

  4. If no results are returned, you can continue with the upgrade

    If any virtual machines are reported with inconsistent data, perform step a or b depending on your requirements.
    1. Remove and re-register the affected virtual machines. Perform this workaround only if it is acceptable to power off the reported virtual machines.
      1. Power off the virtual machine.
      2. Right-click the virtual machine and choose Remove from inventory.
      3. Click Yes to remove the virtual machine.
      4. After removing all virtual machines, make sure these are no virtual machines returned by the SQL query.
      5. Continue with upgrade to vCenter Server 4.1. Make sure vCenter Server 4.1 is running after the upgrade.
      6. Browse to the datastore where the virtual machine is stored.
      7. Right-click the .vmx file for the virtual machine, choose Add to inventory, and follow the on-screen wizard.

    2. Move all reported virtual machines to one host and remove the host from the inventory. Perform this workaround if it is not acceptable to have the virtual machines powered off.
      1. vMotion all reported virtual machines to a single host in vCenter Server 4.0.
      2. Right-click the host containing the reported virtual machines and choose Disconnect.
      3. Once the ESX is disconnected Right-click the host and choose Remove.
      4. Click Yes to remove the host from vCenter Server 4.0.
      5. Continue with the upgrade to vCenter Server 4.1. Make sure vCenter Server 4.1 is running after the upgrade. Click on the data center where the host is to be re-added.
      6. Right-click and choose Add Host.
      7. Enter the host information and proceed to completion.

Note: If you experience the issue even though the script returned no virtual machines, this may be a new issue that has not been reported to VMware. Please contact VMware Support, with vCenter support information and a backup of the database for further review by VMware.

Additional Information

The error Win32 exception: Access Violation can occur for many issues. For other issues that generate this error, see:

See Also

Update History

10/19/2010 - Added updated zip files to the attachments section. 11/1/2010 - Included powered on VM steps; added new attachments

Attachments

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 27 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 27 Ratings
Actions
KB: