So, I recently P2V migrated our VCenter following these instructions:

  1. Verify good full backup of vCenter Server
  2. Ensure there are no current migrations
  3. Verify good full backup of SQL
  4. Maintenance mode target ESX host and wait for all VM’s to DRS to another host
  5. Disconnect ESX host from vCenter
  6. Stop all vCenter and SQL Services on physical vCenter server
  7. Run P2V converter
  8. Check if stable with NIC disabled

(From here: https://communities.vmware.com/thread/454133)

However after starting up the new VM and making the necessary changes, VCenter wouldn’t start. Upon consulting the logs I found the following error:

[SSO][SsoFactory_CreateFacade]’] Unable to create SSO facade: vmodl.fault.SystemError.

My searches on the subject turned up a few people with the same problem but no resolution:

http://scupful2.rssing.com/browser.php?indx=1435389&item=26036
https://communities.vmware.com/thread/444242
https://communities.vmware.com/thread/443382

Until I came across an unrelated VMWare KB, which solved the problem by re-creating the SSO RSA keys:

To resolve this issue:

Click Start, right-click Command Prompt, and click Run as administrator to open a command prompt as an administrator.

Set the Java home path by running this command:

set JAVA_HOME=C:\Program Files\VMware\Infrastructure\jre

Note: The default location is C:\Program Files\VMware\Infrastructure\jre. Ensure that the command does not contain quotes around the path.

In the system where SSO is installed, locate and navigate to the SSO server installation directory.The default location of this directory is C:\Program Files\VMware\Infrastructure\SSOServer\Utils.

Run this command:

rsautil manage-secrets -a recover -m <masterPassword>

Notes:

Fill in the master password for the environment in place of <masterPassword> in the preceding command.

This command recovers and updates the masterPassword (admin@system-domain)

Restart the SSO service.

Restart the VMware VirtualCenter Server service.

(http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2036170)

After that – VCenter started right up!


Categories: Uncategorized


7 Responses so far.


  1. Steve says:

    I had the same problem after a vcetner p2v. This worked for me! Brilliant! Thanks!

  2. Victor says:

    Awesome! Thanks for sharing!

    But rsautil showed me error “Unlimited encription not available”, so it took me few minutes to figure out how to install “JCE Unlimited Jurisdiction 6”
    package.

    Then it worked!

  3. Josh D says:

    You are a LIFESAVER! I just P2V my 5.1 vCenter server to get it off the antiquated hardware, and had this problem, but within a few moments of finding your post, my issue is solved and vCenter is running. Thanks so much for posting this!

  4. Michael says:

    Excelent!
    It’s working.
    Tnak you!

  5. Veimar Souza says:

    OK!!!
    It’s working.
    Tank you from Brazil! 🙂

  6. Danny says:

    I upgraded my OS and had this issue. Saved me from going back to the previous snapshot and giving up.

Leave a Reply