New installl of vCenter 6.5.0 on Windows Server 2016 fails

[gchamby]

Chokes on the vcsservicemanager with a dialog box merely saying i"nternal error"? Tail of vminst.log is below:

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: LaunchPkgMgr: Hiding the cancel button

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: Entering function: PitCA_HideCancelButton

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: PitCA_HideCancelButton: Successful in hiding the Cancel button.

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: Leaving function: PitCA_HideCancelButton

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: LaunchPkgMgr: Telling child to install "D:\vCenter-Server\Packages\vcsservicemanager.msi" with "ALLUSERS=1 ARPSYSTEMCOMPONENT=1 INSTALLPATH="C:\Program Files\VMware\vCenter Server\" APPDATAPATH="C:\ProgramData\VMware\vCenterServer\" PARENTUILEVEL=5 DEBUG_SKIP_ROLLBACK=0 FIRSTBOOT=1 UPDATEBOOT=1 UPGRADEBOOT=1 VM_UPGRADE="" " details 1

2017-07-27 13:00:36.081-04:00| vcsInstUtil-4944578| I: wWinMain: Exe is told to run "D:\vCenter-Server\Packages\vcsservicemanager.msi" with "ALLUSERS=1 ARPSYSTEMCOMPONENT=1 INSTALLPATH="C:\Program Files\VMware\vCenter Server\" APPDATAPATH="C:\ProgramData\VMware\vCenterServer\" PARENTUILEVEL=5 DEBUG_SKIP_ROLLBACK=0 FIRSTBOOT=1 UPDATEBOOT=1 UPGRADEBOOT=1 VM_UPGRADE="" " details 1

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: Entering function: VM_RunFirstBoot

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Action Started

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Established explicit progress

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: DEBUG: silentMode 0

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Told to run "C:\Windows\system32\cmd.exe /S /C ""C:\Program Files\VMware\vCenter Server\bin\run-firstboot-scripts.bat" >> C:\Users\gchamby\AppData\Local\Temp\vminst-con.log 2>&1""

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: got current env variable: "C:\ProgramData\VMware\vCenterServer\logs"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Got log env var: "C:\ProgramData\VMware\vCenterServer\logs"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Status file directory is "C:\ProgramData\VMware\vCenterServer\logs\firstboot\"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Status file path is "C:\ProgramData\VMware\vCenterServer\logs\firstboot\fbInstall.json"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Monitoring common status file

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: Entering function: LaunchProcAndMonitorCommonStatusFile

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: Entering function: LaunchProcAndMonitorStatus

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: LaunchProcAndMonitorStatus: Launching "C:\Windows\system32\cmd.exe /S /C ""C:\Program Files\VMware\vCenter Server\bin\run-firstboot-scripts.bat" >> C:\Users\gchamby\AppData\Local\Temp\vminst-con.log 2>&1"" in "C:\Windows\system32\"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: LaunchProcAndMonitorStatus: Launched process with pid 2672 tid 4412

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: Entering function: MonitorStatusFile

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: MonitorStatusFile: Status file directory is "C:\ProgramData\VMware\vCenterServer\logs\firstboot\"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: MonitorStatusFile: Monitoring directory "C:\ProgramData\VMware\vCenterServer\logs\firstboot\" for file "fbInstall.json"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: MonitorStatusFile: Started execution of process

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: Entering function: ParseStatusFile

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: ParseStatusFile: STATUS: 0%: ""

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: ParseStatusFile: Calling callback with 0 -> 0 ""

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: Entering function: UpdatePkgMgrProgressFromStatusFile

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: ProcessMsiMsg: ACTIONDATA reporting ""

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: Leaving function: UpdatePkgMgrProgressFromStatusFile

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: Leaving function: ParseStatusFile

2017-07-27 13:00:56.218-04:00| vcsInstUtil-4944578| I: Entering function: ParseStatusFile

2017-07-27 13:00:56.233-04:00| vcsInstUtil-4944578| I: ParseStatusFile: curr error msg: "The installation of vCenter Server failed due to an internal error."

2017-07-27 13:00:56.233-04:00| vcsInstUtil-4944578| E: ParseStatusFile: Displaying error message for "VMware vCenter Server": "The installation of vCenter Server failed due to an internal error.

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."

[a_p_]

Discussion moved from tech support to VMware vCenter™ Server