VMware: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installed package
After trying to install vCenter Server I received a warning from Windows Installer:
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installed package
With some troubleshooting at the VMware vCenter Server MSI package to start this package with a logfile, command:
msiexec /l*vx c:\install.log /i "E\vCenter-Server\VMware vCenter Server.msi"
I received this installer Install.log output:
=== Verbose logging started: 2/21/2012 4:23:12 Build type: SHIP UNICODE 5.00.7600.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (DC:D8) [04:23:12:689]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell DlgMSI (c) (DC:D8) [04:23:12:689]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (DC:60) [04:23:12:704]: Resetting cached policy values
MSI (c) (DC:60) [04:23:12:704]: Machine policy value ‘Debug’ is 0
MSI (c) (DC:60) [04:23:12:704]: ******* RunEngine:
******* Product: D:\vpx\VMware vCenter Server.msi
******* Action:
******* CommandLine: **********
MSI (c) (DC:60) [04:23:12:704]: Note: 1: 2203 2: E\vCenter-Server\VMware vCenter Server.msi 3: -2147287039
MSI (c) (DC:60) [04:23:12:704]: MainEngineThread is returning 1620
=== Verbose logging stopped: 2/21/2012 4:23:12 ===
Okay.. the error message “MainEngineThread is returning 1620” means..
ERROR_BAD_CONFIGURATION 1610 The configuration data for this product is corrupt. Contact your support personnel.
Source: Microsoft
Solution:
After reading ^ a knowledgebase article from VMware about MD5 checksums I decided to check my .ISO MD5 checksum with ExactFile…
And there it is… MD5SUM mismatch..
Downloaded the ISO file again and started without problems the installation
Nice piece of troubleshooting my friend, thanks in advance Sander