- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I got same issue trying to upgrade vCenter server from 5.5 U1 Build 1623099 to vCenter 6.0.0 build 4541947. (my infrastructure has SQL database hosted on different server than vCenter and vCenter server installed with AD service account)
First error:
On file vmafd-firstboot.py_5500_stderr.log I found :
2016-12-22T11:58:29.793Z password:
2016-12-22T11:58:29.793Z Vdcsrp failed. Error[9234] - User invalid credential
Make sure the UPN and password are correct
2016-12-22T11:58:29.793Z <type 'exceptions.SystemExit'>
2016-12-22T11:58:29.793Z <type 'exceptions.SystemExit'>
I applied KB 2144402 (set a default Identity Source) and KB 2143753 (change password for AD service account & SSO with a simple password that does not contain special characters) and I got following errors:
File: visl-support-firstboot.py_5924_stderr.log has only one line:
2016-12-22T14:57:30.585Z WARNING Value for install-parameter machine.cert.replacement is empty
...and then:
On file vminst.log:
2016-12-22 06:57:26.450-08:00| vcsInstUtil-4541944| I: ParseStatusFile: STATUS: 0%: ""
2016-12-22 06:57:26.450-08:00| vcsInstUtil-4541944| I: ParseStatusFile: Calling callback with 0 -> 0 ""
2016-12-22 06:57:26.450-08:00| vcsInstUtil-4541944| I: Entering function: UpdatePkgMgrProgressFromStatusFile
2016-12-22 06:57:26.450-08:00| vcsInstUtil-4541944| I: ProcessMsiMsg: ACTIONDATA reporting ""
2016-12-22 06:57:26.450-08:00| vcsInstUtil-4541944| I: Leaving function: UpdatePkgMgrProgressFromStatusFile
2016-12-22 06:57:26.466-08:00| vcsInstUtil-4541944| I: Leaving function: ParseStatusFile
2016-12-22 06:57:31.467-08:00| vcsInstUtil-4541944| I: Entering function: ParseStatusFile
2016-12-22 06:57:31.467-08:00| vcsInstUtil-4541944| I: ParseStatusFile: STATUS: 3%: "Starting VMware Authentication Framework..."
2016-12-22 06:57:31.467-08:00| vcsInstUtil-4541944| I: ParseStatusFile: Calling callback with 0 -> 3 "Starting VMware Authentication Framework..."
2016-12-22 06:57:31.467-08:00| vcsInstUtil-4541944| I: Entering function: UpdatePkgMgrProgressFromStatusFile
2016-12-22 06:57:31.467-08:00| vcsInstUtil-4541944| I: ProcessMsiMsg: ACTIONDATA reporting "Starting VMware Authentication Framework..."
2016-12-22 06:57:31.483-08:00| vcsInstUtil-4541944| I: Leaving function: UpdatePkgMgrProgressFromStatusFile
2016-12-22 06:57:31.483-08:00| vcsInstUtil-4541944| I: Leaving function: ParseStatusFile
2016-12-22 06:57:49.042-08:00| vcsInstUtil-4541944| I: Entering function: ParseStatusFile
2016-12-22 06:57:49.042-08:00| vcsInstUtil-4541944| I: ParseStatusFile: curr error msg: "Encountered an internal error
see C:\ProgramData\VMware\vCenterServer\logs\firstboot\vmafd-firstboot.py_5924_stderr.log"
2016-12-22 06:57:49.042-08:00| vcsInstUtil-4541944| E: ParseStatusFile: Displaying error message for " ": "Encountered an internal error.
see C:\ProgramData\VMware\vCenterServer\logs\firstboot\vmafd-firstboot.py_5924_stderr.log
This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request."
I checked ODBC connection, applying Windows 2012 R2 (where vCenter Server resides), I cheeked different other settings found on internet, I reinstalled back 5.5 using same SQL database and perform the upgrade again => the upgrade failed every time (I think I tried 4-5 times by reinstalling vCenter 5.5).
Because my environment was a test platform and no huge deployment (2 clusters, 8 hosts ESXi 5.5, 28 test VMs) I decided to reinstall the Windows 2012 R2 operating system.
So, I performed following steps:
1) I reinstalled the Windows 2012 R2 operating system (without updates);
2) I installed vCenter Server 5.5 U1 Build 1623099 using the existing SQL database (during the install a new certificate is created ... perhaps you can preserver the old one and replace the new one after vCenter is installed);
3) I rejoined hosts to the new vCenter because the hosts were in disconnected state;
4) I moved hosts out of their Cluster one by one to keep my VMs running (maintenance mode first), reboot the hosts, exit from maintenance mode and re-added to their cluster;
5) Installed Net Framework 3.5
6) Run vCenter upgrade process to 6.0.0 build 4541947
In this way I succeeded to complete the upgrade..
Maybe it's not the right solution for everybody (special if they use different VMware applications on top of vCenter 5.5 - e.g. VMware View) but hope my experience will help the others. ![]()