Search the VMware Knowledge Base (KB)
View by Article ID

Upgrading from vCenter Server 5.5 U2 to 6.0 U2 fails during Inventory Service Database import (2149187)

  • 2 Ratings
Language Editions


  • Upgrading vCenter Server from 5.5 U2 to 6.0 U2 fails.
  • In the Import_com.vmware.is_<date> log, you see message similar to:

    Caught exception while adding permission java.util.concurrent.ExecutionException: (vmodl.fault.InvalidArgument) {
       faultCause = null,
       faultMessage = null,
       invalidProperty = Invalid role Ids [838861204]
    Restore Assignment failed java.util.concurrent.ExecutionException: (vmodl.fault.InvalidArgument) {
       faultCause = null,
       faultMessage = null,
       invalidProperty = Invalid role Ids [838861204]
    Restore Authz failed
    java.util.concurrent.ExecutionException: (vmodl.fault.InvalidArgument) {
       faultCause = null,
       faultMessage = null,
       invalidProperty = Invalid role Ids [838861204]
      at com.vmware.vim.vmomi.core.impl.BlockingFuture.get(
      at com.vmware.vim.dataservices.RestoreAuthz.processItem(
      at com.vmware.vim.dataservices.RestoreAuthz.restoreAssignment(
      at com.vmware.vim.dataservices.RestoreAuthz.main(
    Caused by: (vmodl.fault.InvalidArgument) {
       faultCause = null,
       faultMessage = null,
       invalidProperty = Invalid role Ids [838861204]
    Removing Client@1511370100 reference from CompiledHttpConfiguration@1477403302, 0 active clients left.
    Shutting down CompiledHttpConfiguration@1477403302 as there are no more clients.
    Shutting down the sync ClientConnectionManager
    Shutting down connection monitor thread
    Shutting down the connection monitor.
    Total Memory: 491
    Max Memory: 491
    Free Memory: 442
    Used Memory: 48
    Exiting with code 1 after Restore Authz.
    2017-02-07T10:36:38.336Z INFO is Restore Authz data StdErr:
    2017-02-07T10:36:38.336Z INFO is
    2017-02-07T10:36:38.338Z ERROR __main__ Upgrade Phase 'is:Import' failed. Exception: 'instancemethod' object has no attribute '__getitem__'
    Traceback (most recent call last):
      File "Z:\PFiles\VMware\CIS\cis_upgrade_runner\payload\", line 379, in main
        executionResult = systemExtension(exeContext)
      File "Z:\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\", line 94, in __call__
        result = self.extension(*args)
      File "Z:\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\", line 110, in _func
        return func(*args)
      File "Z:\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\is\", line 686, in importData
        execIsCmd(reporter, restoreAuthz, "Restore Authz data", 50, destComponentAssistant)
      File "Z:\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\is\", line 242, in execIsCmd
      File "Z:\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\is\", line 218, in raiseUpgradeFailed
        if os.environ.has_key['VLSI_CLIENT_PROTOCOLS']:
    TypeError: 'instancemethod' object has no attribute '__getitem__'

    - VPX_ACCESS does not have the reference id's


This article provides steps to resolve the issue when  vCloud is integrated with vCenter Server and inventory database cannot be reset.


To resolve this issue, truncate 'VPX_PROPERTY_BULLETIN' table during the upgrade.

1. Take a snapshot of the existing setup.

2. On the vCenter Server, stop these services in this order:
  • VMware VirtualCenter Server service
  • VMware Inventory service.

3. Connect to the vCenter Server database.

Note: Ensure to take a backup of the database before proceeding. Snapshot at Step1 will take VCDB backup also.

4. Run this query to truncate the VPX_PROPERTY_BULLETIN table:


5. Run this query to ensure that the VPX_PROPERTY_BULLETIN table is empty:


6. Start the VMware VirtualCenter Server service.

Note: Allow 2-3 minutes before proceeding. This will repopulate 'VPX_PROPERTY_BULLETIN'

7. Start the VMware Inventory Service. Wait for 10-15 minutes depending on inventory size.

Note: If there are other products that use the VMware Inventory Service, they may require a restart to function properly.

8. Upgrade should be successful now.

See Also

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.


  • 2 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)

Please enter the Captcha code before clicking Submit.
  • 2 Ratings