That's kind of where I was going with "file is already open" thing
and yes, I think we've all done it at one time. :)
---------------
Phil Wilson


On Mon, Oct 13, 2014 at 8:57 AM, Nicolás Alvarez
<nicolas.alva...@gmail.com> wrote:
> Or that you have the MSI open in Orca while trying to install it :)
>
> --
> Nicolás
>
> 2014-10-13 12:16 GMT-03:00 Phil Wilson <phildgwil...@gmail.com>:
>> Error 1619 is "This installation package could not be opened. Verify
>> that the package exists and is accessible, or contact the application
>> vendor to verify that this is a valid Windows Installer package."
>> Something about the context of the install or the security (or
>> sometimes when the file is already open) means that Windows can't get
>> access to the MSI file.
>> ---------------
>> Phil Wilson
>>
>>
>> On Sun, Oct 12, 2014 at 11:15 PM, Yankulin, Leonid
>> <leonid.yanku...@mckesson.com> wrote:
>>> Hello,
>>> I am trying to run silent installation of my MSI (WiX 3.8; VS2013) with /qn 
>>> parameter. When the MSI is stored locally on computer I am getting a pretty 
>>> long log with no errors, which ends with "nothing". No files installed, no 
>>> IIS virtual directories created, no SQL scripts ran. I am suspecting it is 
>>> somehow relates to execution sequence, but I do not know where to start. We 
>>> have customized UI that makes use of custom actions. However, all 
>>> installations are implemented using components and WiX iis and sql elements.
>>> When I am trying to install the file from remote location I am getting the 
>>> following log only:
>>> -----
>>> === Verbose logging started: 13/10/2014  08:41:26  Build type: SHIP UNICODE 
>>> 5.00.7601.00  Calling process: C:\Windows\system32\msiexec.exe ===
>>> MSI (c) (C4:B4) [08:41:26:585]: Resetting cached policy values
>>> MSI (c) (C4:B4) [08:41:26:585]: Machine policy value 'Debug' is 0
>>> MSI (c) (C4:B4) [08:41:26:585]: ******* RunEngine:
>>>            ******* Product: 
>>> \\migspicard\builds\Picard_Test\Picard_Test_101314.01
>>>            ******* Action:
>>>            ******* CommandLine: **********
>>> MSI (c) (C4:B4) [08:41:26:586]: Client-side and UI is none or basic: 
>>> Running entire install on the server.
>>> MSI (c) (C4:B4) [08:41:26:586]: Grabbed execution mutex.
>>> MSI (c) (C4:B4) [08:41:26:667]: Cloaking enabled.
>>> MSI (c) (C4:B4) [08:41:26:667]: Attempting to enable all disabled 
>>> privileges before calling Install on Server
>>> MSI (c) (C4:B4) [08:41:26:670]: Incrementing counter to disable shutdown. 
>>> Counter after increment: 0
>>> MSI (s) (B4:D8) [08:41:26:678]: Running installation inside multi-package 
>>> transaction \\migspicard\builds\Picard_Test\Picard_Test_101314.01
>>> MSI (s) (B4:D8) [08:41:26:678]: Grabbed execution mutex.
>>> MSI (s) (B4:68) [08:41:26:679]: Resetting cached policy values
>>> MSI (s) (B4:68) [08:41:26:679]: Machine policy value 'Debug' is 0
>>> MSI (s) (B4:68) [08:41:26:679]: ******* RunEngine:
>>>            ******* Product: 
>>> \\migspicard\builds\Picard_Test\Picard_Test_101314.01
>>>            ******* Action:
>>>            ******* CommandLine: **********
>>> MSI (s) (B4:68) [08:41:26:989]: Note: 1: 2203 2: 
>>> \\migspicard\builds\Picard_Test\Picard_Test_101314.01 3: -2147287035
>>> MSI (s) (B4:68) [08:41:26:990]: MainEngineThread is returning 1619
>>> MSI (s) (B4:D8) [08:41:26:991]: User policy value 'DisableRollback' is 0
>>> MSI (s) (B4:D8) [08:41:26:991]: Machine policy value 'DisableRollback' is 0
>>> MSI (s) (B4:D8) [08:41:26:991]: Incrementing counter to disable shutdown. 
>>> Counter after increment: 0
>>> MSI (s) (B4:D8) [08:41:26:991]: Note: 1: 1402 2: 
>>> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
>>>  3: 2
>>> MSI (s) (B4:D8) [08:41:26:992]: Note: 1: 1402 2: 
>>> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
>>>  3: 2
>>> MSI (s) (B4:D8) [08:41:26:992]: Note: 1: 1402 2: 
>>> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
>>>  3: 2
>>> MSI (s) (B4:D8) [08:41:26:992]: Note: 1: 1402 2: 
>>> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
>>>  3: 2
>>> MSI (s) (B4:D8) [08:41:26:992]: Decrementing counter to disable shutdown. 
>>> If counter >= 0, shutdown will be denied.  Counter after decrement: -1
>>> MSI (s) (B4:D8) [08:41:26:992]: Restoring environment variables
>>> MSI (c) (C4:B4) [08:41:26:994]: Decrementing counter to disable shutdown. 
>>> If counter >= 0, shutdown will be denied.  Counter after decrement: -1
>>> MSI (c) (C4:B4) [08:41:26:995]: MainEngineThread is returning 1619
>>> === Verbose logging stopped: 13/10/2014  08:41:26 ===
>>> -----
>>>
>>> Please, advise about what additional information is required to figure why 
>>> the local silent setup isn't working AND why a slient setup from remote 
>>> location behaves weird.
>>>
>>> Thank you,
>>> Leonid Yankulin
>>> Email: leonid.yanku...@mckesson.com<mailto:leonid.yanku...@mckesson.com>
>>>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to