vCenter 5.5 SSO to 6 PSC Upgrade 1603 Error: Unable to call to Component Manager; Failed to register service in Component Manager

By | March 31, 2016

Upgrading from 5.5 SSO to 6.0 PSC is usually pretty easy but I did have one error worth mentioning.

First I got the generic 1603 Error.

I then looked through the logs and saw this:

“Unable to call to Component Manager: Failed to register service in Component Manager; url:http://localhost:18090/cm/sdk/?hostid=5e7af582-c545-11e5-a7c6-005056b8654e, id:04d333a2-e2bb-41c8-8ae6-39598604ddc1”

After working through it with support, it turned out I was missing a PTR record. Once I created that my upgrade was successful.

NOTE: As with any of the 5.5 to 6 upgrades, a failure will trash your system. Restore from your snapshot and upgrade again.

 

 

5 thoughts on “vCenter 5.5 SSO to 6 PSC Upgrade 1603 Error: Unable to call to Component Manager; Failed to register service in Component Manager

  1. Fredrik

    I got a similar error for vCenter upgrade from 5.5 SSO to 6.0 embedded PSC.
    Could you elaborate on the PTR record you were missing?

    Reply
    1. Chris Post author

      The forward DNS entry for the server was there but the reverse was missing.

      Reply
      1. Fredrik

        I have an PTR for vCenter in reverse lookup, and tested a NSLOOKUP for both FQDN and IP which is both resolved. Guess I got some other cause.

        Reply
        1. Chris Post author

          The reverse DNS entry seemed to have fixed it in my case, but my colleague could have also trashed the reverse entry while troubleshooting. I just know that I recreated the entry and was successful during another upgrade sttempt.

          Reply
          1. Fredrik

            After going thru everything, one thing I found was that ESXi host clock was out of sync with NTP-server (this is a bug I thought was resolved in 5.5U2). Corrected and setup ran without issues. Did manage to drop HA due to also upgrading from Essentials to Standard license and doing vCenter before the Hosts.

Leave a Reply

Your email address will not be published. Required fields are marked *