Hello,

We have a user of our software that is having trouble installing the software on a Windows 7 PC. They get the message:
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package

This is day 3 of technical support on this issue, we have tried a lot of things.

I had them run the installation with verbose logging, here is the result:

=== Verbose logging started: 11/17/2015  13:46:20  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\SysWOW64\MSIEXEC.EXE ===
MSI (c) (A0:B0) [13:46:20:844]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (A0:B0) [13:46:20:844]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (A0:40) [13:46:20:854]: Resetting cached policy values
MSI (c) (A0:40) [13:46:20:854]: Machine policy value 'Debug' is 0
MSI (c) (A0:40) [13:46:20:854]: ******* RunEngine:
           ******* Product: C:\Windows\Downloaded Installations\HydroComp NavCad 2015.msi
           ******* Action: 
           ******* CommandLine: **********
MSI (c) (A0:40) [13:46:20:855]: Note: 1: 2203 2: C:\Windows\Downloaded Installations\HydroComp NavCad 2015.msi 3: -2147286960 
MSI (c) (A0:40) [13:46:20:856]: MainEngineThread is returning 1620
=== Verbose logging stopped: 11/17/2015  13:46:20 ===

Here is my interpretation:
There errors are present in your log files for the installations:
Note: 1: 2203 2: C:\Windows\Downloaded Installations\HydroComp NavCad 2015.msi 3: -2147286960
(1)The first number is the MSI error code, 2203, which means “Cannot open database”.
(2) The name database is the *.msi file
(3) –2147286960 is a system error code means “STG_E_FILEALREADYEXISTS – “Already exists.”
 
The next line in the log file is the termination of the installer:
MainEngineThread is returning 1620
1620 is the error message “This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.”


What I find the most interesting is the complete lack of a GUID for the extraction location of the MSI:
C:\Windows\Downloaded Installations\HydroComp NavCad 2015.msi 
This line is typically logged like this on other systems:
C:\Windows\Downloaded Installations\{E7646E61-43FB-460E-8D8F-15D8845FF10B}\HydroComp NavCad 2015.msi

This is being installed on a domain, so far everything with windows update and permissions for the system have checked out.

Any help is GREATLY appreciated.

-Adam
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0
Is this just one user/machine affected - or all deployments of the software?
What command line are you running?
What deployment tool are you using?
Is this a vendor MSI, or a capture?
Does a manual install work correctly?
Answered 11/18/2015 by: dunnpy
Red Belt

  • We have hundreds of successful installations, including at least 3 others on this network. So just one user/machine that is having trouble. We have seen this only once before 2 years ago, and do not have any information on how the user resolved it. But in this case the GUID was also missing and it was a domain style network.

    These are being executed manually, but the command line used for logging is:

    C:\NavCad2015.2.Setup.exe /v"/L*vx! C:\temp\SetupLog.log"

    The installation is created using InstallShield Express.

    Thanks
Please log in to comment
0
Answered 11/18/2015 by: aragorn.2003
Red Belt

  • Thanks for the help, no useful information there, I came across that previously. But thanks.

    Looking for details on the 1620 error with the –2147286960 system error code (STG_E_FILEALREADYEXISTS – “Already exists.”)

    I feel like this must be related to the lack of GUID...
Please log in to comment
0
try calling the 64 bit msi installer vs the 32 bit  (C:\Windows\SysWOW64\MSIEXEC.EXE) from your error logs.

Use the call
%
SYSTEMROOT%\sysnative\msiexec /i ...
or
c:\windows\system32\msiexec /i ...
Answered 11/18/2015 by: SMal.tmcc
Red Belt

  • The log file indicates it is already using the 64 bit version in System32...

    On my PC I have run it with both System32 and SysWOW64 and had no differences either way, but I will ask my customer to try this next anyway.
Please log in to comment
0
Day THREE!?! Since it's one out of so many, I'd have rebuilt it by now. Don't waste any more time on it.

If you *really* want to get to the bottom of it, you're going to have sit and watch the installation with ProcMon.
Answered 11/19/2015 by: VBScab
Red Belt

  • Day 4, although I haven't heard back from them since Day 2.

    Unfortunately it is someone else's workstation, located far away, it's not my call for the rebuild. I don't have any sort of remote access, all I can do is ask for logs and provide suggestions to the fix.

    But, since we have encountered this before, it is tough to ignore.

    We emailed the user who had the error, and they just told us they were never able to resolve it.

    Could this be caused by a non-deleted partial installation? I just don't understand this "already exists", –2147286960 system error code...
Please log in to comment
Answer this question or Comment on this question for clarity

Share