Hi,
I am trying to migrate from vCenter Server 6.0 U 2 (build 3634793) to vCSA 6.5 (build 5178943) using the VMware migration assistant on the (German) Windows Server 2012 R2.
Directly after double-clicking VMware-Migration-Assistant.exe and elevating I get an APPCRASH referring to MSVCR120.dll and code c0000005.
Log looks clean to me:
2017-03-28 13:17:47.194Z| migration-assistant-5178943| I: MAInit: stdout successfully changed to UTF-8 mode
2017-03-28 13:17:47.216Z| migration-assistant-5178943| I: SetMALocale: UI language id of machine 1031 is supported.
2017-03-28 13:17:47.216Z| migration-assistant-5178943| I: GetInstallParameter: Retrieving the data for vmdir.domain-name
2017-03-28 13:17:47.218Z| migration-assistant-5178943| I: GetPdtConfigDirPath: ENV_VMWARE_CFG_DIR directory path is D:\ProgramData\VMware\vCenterServer\cfg
2017-03-28 13:17:47.218Z| migration-assistant-5178943| I: GetInstallDefaultsDirPath: install-defaults directory path is D:\ProgramData\VMware\vCenterServer\cfg\install-defaults\
2017-03-28 13:17:47.218Z| migration-assistant-5178943| I: GetFileContents: Contents from [D:\ProgramData\VMware\vCenterServer\cfg\install-defaults\vmdir.domain-name] file is [vsphere.local]
2017-03-28 13:17:47.218Z| migration-assistant-5178943| I: GetInstallParameter: PropertyName=[vmdir.domain-name] : Value=[vsphere.local]
2017-03-28 13:17:47.218Z| migration-assistant-5178943| I: ParseCommandLineOptions: MA launched without passing command line parameters.
2017-03-28 13:17:47.232Z| migration-assistant-5178943| I: LocaleHandler::SetLocale: Client locale en is supported
2017-03-28 13:17:47.232Z| migration-assistant-5178943| I: MAInit: Initializing Migration Assistant...
2017-03-28 13:17:47.233Z| migration-assistant-5178943| I: MAInit: Ctrl handler successfully set.
2017-03-28 13:17:47.234Z| migration-assistant-5178943| I: SanityCheckAdminPrivilege: Launching user retrieved successfully: '<domain\user name>'
2017-03-28 13:17:47.234Z| migration-assistant-5178943| I: SanityCheckAdminPrivilege: Process has admin privilege.
AV software is turned off, firewalls also, machine has been rebooted. Already tried copying the directory to the system disks, replaced the dll from the Windows directory and so on.
Since the main reason to go to vCSA is the crappy update mechanism in vCenter Server for Windows - I wasn't able to upgrade it for so many times already (error 1603), had to rebuild the server a couple of times and now I am fed up with it - upgrading to a higher build first is not an option. But this build is supported for vCSA 6.5 migration anyway.
Any idea how to solve this?
Thanks so much in advance!
Martin
