Troubleshooting 1603 errors when installing\upgrading vCenter Server 6.x

Products

• VMware vCenter Server

Issue/Introduction

This article provides the list of symptoms and corresponding Knowledge Base articles that provide resolution of the failed vCenter Server 6.x Microsoft Windows installer that returns the error 1603.

Environment

VMware vCenter Server 6.5.x
VMware vCenter Server 6.7.x
VMware vCenter Server 6.x
VMware vCenter Server 6.0.x

Resolution

• Master KB for Installing\Upgrading vCenter Server 6.x troubleshooting articles for 1603 error 

 

Symptoms	Article
vcsInstUtil-2562624| I: ParseStatusFile: curr error msg: "VMware VirtualCenter failed firstboot." vcsInstUtil-2562624| I: ParseStatusFile: curr error msg: "Database in-place upgrade failed. Please see vcdb_inplace.err and vcdb_inplace.out for details." vcsInstUtil-2562624| E: ParseStatusFile: Displaying error message for "install.vpxd.action.failed": "VMware VirtualCenter failed firstboot. Database in-place upgrade failed. Please see vcdb_inplace.err and vcdb_inplace.out for details. Please refer to vSphere documentation to troubleshoot or Please contact VMware Support." vcsInstUtil-2562624| I: Leaving function: VM_RunLastBoot vcsInstUtil-2562624| E: wWinMain: MSI result of install of "install_drive:\vCenter-Server\Packages\vcsservicemanager.msi" may have failed: 1603 (0x00000643) vcsInstUtil-2562624| E: LaunchPkgMgr: Operation on vcsservicemanager.msi appears to have failed: 1603 (0x00000643) vcsInstUtil-2562624| I: PitCA_MessageBox: Displaying message: "Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details."	Database in-place upgrade fails with error code 1603 while starting VMware VirtualCenter Service (2119768)
<YYYY-MM-DD>T<time>| vcsInstUtil-2562624| I: ParseStatusFile: curr error msg: "Error in accessing windows registry entry during DSN analysis: Error in accessing registry entry for DSN 'VCDB'. Please make sure the DSN is set up properly." <YYYY-MM-DD>T<time>| vcsInstUtil-2562624| E: ParseStatusFile: Displaying error message for " ": "Error in accessing windows registry entry during DSN analysis: Error in accessing registry entry for DSN 'VCDB'. Please make sure the DSN is set up properly."</time></time>	Upgrading or installing VMware vCenter Server 6.0 fails with the vminst.log error: Error in accessing registry entry for DSN (2113068)
2015-07-06 15:05:40.416-04:00| vcsInstUtil-2656758| E: RunFirstLastUpdateboot: Failed to run boot script: "C:\Windows\system32\cmd.exe /S /C ""C:\Program Files\VMware\vCenter Server\bin\run-uninstall-scripts.bat" --operation ROLLBACK"" 2015-07-06 15:05:40.416-04:00| vcsInstUtil-2656758| I: Leaving Function: VMRunLastBoot 2015-07-06 15:05:40.479-04:00| vcsInstUtil-2656758| E: wWinMain: MSI result of install of "D:\vCenter-Server\Packages\vcsservicemanager.msi" may have failed : 1603 (0x00000643) 2015-07-06 15:05:40.479-04:00| vcsInstUtil-2656758| E: LaunchPkgMgr: Operation on vcsservicemanager.msi appears to have failed : 1603 (0x00000643) 2015-07-06 15:05:40.479-04:00| vcsInstUtil-2656758| I: PitCA_MessageBox: Displaying message: "Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details." 2015-07-06 15:06:00.775-04:00| vcsInstUtil-2656758| I: LaunchPkgMgr: Telling child to revert transaction 2015-07-06 15:06:00.775-04:00| vcsInstUtil-2656758| I: InstallStatus_SetStage: install stage: install-packages / revert-transaction 2015-07-06 15:06:35.554-04:00| vcsInstUtil-2656758| I: EndTransaction: Chain transaction 1 rollback result 0	Please contact Technical Support to address the error.
The range of ephemeral TCP ports on this system is 1025 to 65534. This range of ports is too large and the system must be reconfigured to use a smaller ephemeral port range before the install can continue. We recommend using the default range of 49152 to 65535 (For example, by running the command "netsh.exe int ipv4 set dynamicportrange tcp 49152 16384"	Installing or upgrading VMware vCenter Server 6.0 fails with the error: The range of ephemeral TCP ports on this system is 1025 to 65534 (2117961)
<YYYY-MM-DD>T<time>:t@8246016:INFO: Add Entry (CN=machine-########-####-####-####-########6847,CN=ServicePrincipals,DC=vsphere,DC=local) <YYYY-MM-DD>T<time>:t@8246016:INFO: Modify Entry (CN=SolutionUsers,DC=vsphere,DC=local) <YYYY-MM-DD>T<time>:t@8246016:INFO: Modify Entry (CN=ComponentManager.Administrators,DC=vsphere,DC=local) <YYYY-MM-DD>T<time>:t@8246016:INFO: Modify Entry (CN=SystemConfiguration.Administrators,DC=vsphere,DC=local) <YYYY-MM-DD>T<time>:t@8246016:ERROR: InternalModifyEntry: VdirExecutePostModifyCommitPlugins - code(9703) <YYYY-MM-DD>T<time>:t@8246016:ERROR: VmDirSendLdapResult: Request (102), Error (32), Message (BEEntryModify (9703)((MDB_NOTFOUND: No matching key/data pair found)(cn=administrators,cn=builtin,dc=vsphere,dc=local))), (0) socket ([2060] vcenter_ip:389<-vcenter_ip:50769)</time></time></time></time></time></time>	"LDAP error: No such Object" seen when upgraded vCenter Server 5.5 to 6.0 (2119606)

 

Note: If you are receiving a 1603 error that is not listed in the preceding steps, file a support request with Broadcom Support.