[WiX-users] "This installation package could not be opened."

[Michael.A.Kelley]

I have a .msi I've created using Wix that seems to work on a lot of computers. However, I occasionally have reports of of clients running the .msi on their computer and getting this error message:

"This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package."

Does anyone know how I can recreate this image, and what I could possibly be doing wrong in my .wxs file? This error happens with both 2.0 and 3.0 versions of Wix.

Product.wxs

[Karl Denning]

What are the circumstances when it fails?

Perhaps there is another process locking the file open?
I have seen this error occasionally when I try to open a package that is on a network share with orca.
I presume that there is an AV scanner running on the server locking the file open.



I have a .msi I've created using Wix that seems to work on a lot of computers. However, I occasionally have reports of of clients running the .msi on their computer and getting this error message:

"This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package."

Does anyone know how I can recreate this image, and what I could possibly be doing wrong in my .wxs file? This error happens with both 2.0 and 3.0 versions of Wix.

Product.wxs

[Michael.A.Kelley]

It's hard to say the exact circumstances. The .msi is downloaded from our website, and I don't have access to the client's computer.

The client that last reported this problem has his AV scanner disabled. I'll ask him if he's running it from a network share.


What are the circumstances when it fails?

Perhaps there is another process locking the file open?
I have seen this error occasionally when I try to open a package that is on a network share with orca.
I presume that there is an AV scanner running on the server locking the file open.



I have a .msi I've created using Wix that seems to work on a lot of computers. However, I occasionally have reports of of clients running the .msi on their computer and getting this error message:

"This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package."

Does anyone know how I can recreate this image, and what I could possibly be doing wrong in my .wxs file? This error happens with both 2.0 and 3.0 versions of Wix.

Product.wxs

[Michael.A.Kelley]

Here's the log file from the failed install. This looks like it could be file corruption error, unless someone else can tell me otherwise?

=== Verbose logging started: 4/1/2009 11:02:16 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (28:DC) [11:02:16:072]: Resetting cached policy values
MSI (c) (28:DC) [11:02:16:072]: Machine policy value 'Debug' is 0
MSI (c) (28:DC) [11:02:16:072]: ******* RunEngine:
******* Product: PixelActiveCityScape_v1_7_Demo.msi
******* Action:
******* CommandLine: **********
MSI (c) (28:DC) [11:02:16:072]: Note: 1: 2203 2: PixelActiveCityScape_v1_7_Demo.msi 3: -2147287010
MSI (c) (28:DC) [11:02:16:072]: MainEngineThread is returning 1620
=== Verbose logging stopped: 4/1/2009 11:02:16 ===


It's hard to say the exact circumstances. The .msi is downloaded from our website, and I don't have access to the client's computer.

The client that last reported this problem has his AV scanner disabled. I'll ask him if he's running it from a network share.


What are the circumstances when it fails?

Perhaps there is another process locking the file open?
I have seen this error occasionally when I try to open a package that is on a network share with orca.
I presume that there is an AV scanner running on the server locking the file open.



I have a .msi I've created using Wix that seems to work on a lot of computers. However, I occasionally have reports of of clients running the .msi on their computer and getting this error message:

"This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package."

Does anyone know how I can recreate this image, and what I could possibly be doing wrong in my .wxs file? This error happens with both 2.0 and 3.0 versions of Wix.

Product.wxs

[Karl Denning]

I just tried my msi when locked by orca, and when it is on a nw share (I don't manage the nw share, and I have no idea why I cannot open it when it's on that particular share). In both cases i get error 1619. So it's not what I think it might be.

I'd guess it's corrupt to.

However... http://www.appdeploy.com/msierrors/detail.asp?id=26 says other things.

K.




Here's the log file from the failed install. This looks like it could be file corruption error, unless someone else can tell me otherwise?

=== Verbose logging started: 4/1/2009 11:02:16 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (28:DC) [11:02:16:072]: Resetting cached policy values
MSI (c) (28:DC) [11:02:16:072]: Machine policy value 'Debug' is 0
MSI (c) (28:DC) [11:02:16:072]: ******* RunEngine:
******* Product: PixelActiveCityScape_v1_7_Demo.msi
******* Action:
******* CommandLine: **********
MSI (c) (28:DC) [11:02:16:072]: Note: 1: 2203 2: PixelActiveCityScape_v1_7_Demo.msi 3: -2147287010
MSI (c) (28:DC) [11:02:16:072]: MainEngineThread is returning 1620
=== Verbose logging stopped: 4/1/2009 11:02:16 ===

[Thomas Due]

I usually experience this error when I forget where I am and try to
execute an MSI package from a subst'ed drive. I get the same when
executing from a network drive. I have not looked deeply into the cause,
but it seems that the msi needs to be on at least a primary partition
for msiexec to run it.

/Thomas Due

-----Original Message-----
From: Michael.A.Kelley [mailto:***@gmail.com]
Sent: 1. april 2009 02:36
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] "This installation package could not be
opened."


It's hard to say the exact circumstances. The .msi is downloaded from
our website, and I don't have access to the client's computer.

The client that last reported this problem has his AV scanner disabled.
I'll ask him if he's running it from a network share.


What are the circumstances when it fails?

Perhaps there is another process locking the file open?
I have seen this error occasionally when I try to open a package that is
on a network share with orca.
I presume that there is an AV scanner running on the server locking the
file open.



I have a .msi I've created using Wix that seems to work on a lot of
computers. However, I occasionally have reports of of clients running
the .msi on their computer and getting this error message:

"This installation package could not be opened. Contact the application
vendor to verify that this is a valid Windows Installer package."

Does anyone know how I can recreate this image, and what I could
possibly be doing wrong in my .wxs file? This error happens with both
2.0 and 3.0 versions of Wix.

Product.wxs