VMware Cloud Community
ChuckS42
Enthusiast
Enthusiast
Jump to solution

vCenter migration from 5.5U3 to 6.5U1 VCSA fails

So, trying to get a 5.5U3 Windows-based vCenter migrated to a 6.5U1 VCSA. Migration Assistant pre-checks come up clean. The appliance deploys properly. However, the process fails on the "Set up target vCenter Server and start services" step of Phase 2. It throws an error about failing to register the Web Client with Component Manager. Tried multiple times. VMware Support has so far not been helpful; their suggestions made no difference (reinstall the web client on the source vCenter, disable/remove any plugins). Anyone see this happen before?

0 Kudos
1 Solution

Accepted Solutions
ChuckS42
Enthusiast
Enthusiast
Jump to solution

Got it sorted. SSO was borked, as a result a bad decision a few years ago to use a forbidden character in the SSO site name ("\"; oddly enough the installer never complained, and it worked fine for years). Had to uninstall and reinstall SSO, then re-register components. After that the VCSA migration went swimmingly.

View solution in original post

0 Kudos
4 Replies
daphnissov
Immortal
Immortal
Jump to solution

Sorry to ask the obvious, but need to cover the bases. Have you tried:

  • Ensuring there are forward and reverse DNS records created for the vCSA
  • Ensuring NTP is started and accessible (local NTP) with times in sync for the source vCenter, target vCSA, and the workstation from which you're launching the wizard?
0 Kudos
ChuckS42
Enthusiast
Enthusiast
Jump to solution

No worries getting the obvious out of the way. Yes, forward and reverse DNS records exist and work, and time is fully in sync all around.

0 Kudos
msripada
Virtuoso
Virtuoso
Jump to solution

can you upload the log bundle for the migration?

Thanks,

MS

0 Kudos
ChuckS42
Enthusiast
Enthusiast
Jump to solution

Got it sorted. SSO was borked, as a result a bad decision a few years ago to use a forbidden character in the SSO site name ("\"; oddly enough the installer never complained, and it worked fine for years). Had to uninstall and reinstall SSO, then re-register components. After that the VCSA migration went swimmingly.

0 Kudos