therealLars
Contributor
Contributor

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

Hi,

we try to migrate our vCenter Server (Windows Server 2008 R2 x64 with embedded SQL 2008 SP2) to VCSA 6.0. To use the officially supported way, we've used the VCSA 6.0 U2M Version, but currently we are unable to complete the migration process.

At our vCenter Server the migration assistent started sucessfully and told us also "waiting for migration, don't close this windows etc" but as we tried to follow the migration, we got an error message at step 6.

After we entered our Domain credentials (AD) the setup failed with "Error in populating profiles" and so we are unable to select the size of the vcsa VM (tiny, small etc.) via the combobox (it's empty).

After some research we found similar errors and some solutions like uninstall vmware horizon but we don't have anything special installed at our clients (where we started the vcsa-setup.html) and tried already different clients, including other OS (Win Srv and 10) and different languages (ENG/GER).

Does anybody has any clou about this?

Thanks in advance

0 Kudos
7 Replies
vHaridas
Expert
Expert

have you entered correct password for SSO Administrator?

See migration logs for errors or upload it here.

If migration fails or if I want to see more details regarding a migration, where can I find the logs?

vCenter Server Appliance Migration Tool UI Logs: %appdata%\Local\VMware\CIP\vcsaInstaller\sessions\session_id\logs
vCenter Server Appliance Migration Tool CLI Logs: %TMPDIR/vcsaCliInstaller-<timestamp>/vcsa-cli-installer.log
vCenter Server Appliance Migration Assistant Logs on Source Windows vCenter Server: %temp%/vcsMigration & %temp%/migration-assistant.log

-

Haridas

Please consider awarding points for "Correct" or "Helpful" replies. Thanks....!!! https://vprhlabs.blogspot.in/
0 Kudos
therealLars
Contributor
Contributor

Yeah I think I entered it correctly.

I've checked the logs arelady but I couldn't found anything suspicious. I've sent the logs to you via file upload.

Thanks for your help

0 Kudos
opoly
Contributor
Contributor

Did you find a solution to this issue? Currently hit it also and have an SR open with VMware

0 Kudos
neesus
Contributor
Contributor

Also receiving this error while trying to upgrade my virtual appliance by running the client integration plugin from a Windows 2012 R2 server.
Step 5 Select appliance size has a yellow banner with "Error in populating profiles" and nothing in the drop down.

The Next button is available but wouldn't want to proceed without sizing it correctly.

Waiting for support to get back to me.

0 Kudos
sanjeebkumar
VMware Employee
VMware Employee

can you post the vcsupport or prechecks.json file ?

0 Kudos
neesus
Contributor
Contributor

Not sure where to pull the requested.

Below is the response I received back from support:

I understand, from briefly reviewing the case notes, that at present you're experiencing issues upgrading via the Migration Tool?

Just from the error you've reported, I've had other customers resolve the issue by following the below - essentially tidying up their existing database and then attempting the migration again.

VPX_TEXT_ARRAY table growing in size causes the vCenter Server database to run out of space (2005333) --> https://kb.vmware.com/kb/2005333

Selective deletion of tasks, events, and historical performance data in vSphere 5.x and 6.x (2110031) --> https://kb.vmware.com/kb/2110031

Also, make sure that the database has been prepared for the upgrade as per:

https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.upgrade.doc/GUID-55F7FFDB-01B8-4C18-...

Then attempt the upgrade again, if you hit an issue, then we will require the log bundle from the failed upgrade as per:

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

Do let me know if the migration is successful after implementing these steps.

This did not fix anything for me, but I did find a way around the issue.

When I do not check the box in step 4 for "Migrate Performance & other historical data" I do not receive the error for the sizing selection page and am able to proceed.
My company doesn't allow major system changes on a Friday so I can't hit finish until Monday but this will work for me.

I have instead exported the previous log data to a folder off my vCenter 5.5 environment in case I need to ever reference it.

Just wanted to share my findings incase it helps anyone else.

0 Kudos
navy4596
Contributor
Contributor

This fixed the issue - VPX_TEXT_ARRAY table growing in size causes the vCenter Server database to run out of space (2005333) --> https://kb.vmware.com/kb/2005333

0 Kudos