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 ===



-- 
View this message in context: 
http://n2.nabble.com/%22This-installation-package-could-not-be-opened.%22-tp2566106p2571317.html
Sent from the wix-users mailing list archive at Nabble.com.


------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to