vcentre 5.5 to 6.0 migration error

[Martin_77]

Hi all.

I just inherited this vcenter 5.5 system and am tasked to get it 6.0 (going from Windows server to VCSA appliance).  I've started with the convenient U2M package and have the Migration Assistant running on the existing server, and when I run the actual migration tool, I get stuck on step 6 where I select the appliance size.  It comes up with an error 'Error in populating profiles' and won't let me select the appliance size.  I can't seem to find where the log files are that will help me on this, or a good answer from searching on how to get past that error.  Any ideas ?

[birend1988]

Can you please share the screen capture?

[Martin_77]

Screen shot attached.

[birend1988]

Please refer this KB and see if this helps,

VMware Knowledge Base

[Deso1ator]

You might want to check out this discussion. Someone had the same error has you during the migration wizard.

"Error in populating profiles" @ vcs 5.5 U2 (Windows) to VCSA 6.0 U2M migration

[a_p_]

...  I've started with the convenient U2M package ...

Just a quick side note (links for database cleanup have already been provided). U2m was the first vCSA build which had the migration wizard included. However, unless you have a reason to use this specific version, you may use the latest build for the migration.

André

[Martin_77]

We are looking that database cleanup, that sounds promising.

As for the version, we are still on Horizon View 6.2.3 and we can only go up to vcentre 6.0u3 with it.  This is an old environment and we are only going up to 6.0 to add some new servers until our new environment is ready.

[a_p_]

Please don't get me wrong. I'm not talking about vCenter 6.5, or later, I'm talking about the latest vCenter Serer 6.0 U3 build that you can migrate to, rather tha to the rather old U2m build.

André

[Martin_77]

Ah, I see.  The only reason for 6.0u2 is because vmware has that on one package.  Once migrated, I plan to update to 6.0u3.

[birend1988]

Pls take full DB backup and VC backup as well before perform any steps.

[Raj1988]

truncate VPX_TEXT_ARRAY  and then run the migration .