Hi,
It's a per machine install. I'll ask our customer if they have an IT dept.
that sets policies and see if they can get any information on what they do with
EFS. I also asked them to browse to the Package Cache folder and see if it's
encrypted.
I know there is a bug in windows were it an MSI will fail to install if it's
encrypted by EPS. It's a permission issue, once MSIexec goes into the server
side it is running as System and the MSI is encrypted with a user key by EFS.
You see in the MSI log below the message " The system cannot open the device or
file specified.".
I have the logs and the main burn log shows my two optional MSI packages being
skipped by failing on the third MSI package which is required.
Snippet of Burn log:
[1308:08D0][2014-06-24T08:30:57]i299: Plan complete, result: 0x0
[1308:08D0][2014-06-24T08:30:57]i300: Apply begin
[10BC:1688][2014-06-24T08:30:57]i360: Creating a system restore point.
[10BC:1688][2014-06-24T08:31:10]i361: Created a system restore point.
[10BC:1688][2014-06-24T08:31:10]i000: Caching bundle from:
'C:\Users\BOBBYR~1\AppData\Local\Temp\{0c5773dd-0a10-45df-9f49-05cc6186a803}\.be\ConfigInstaller.exe'
to: 'C:\ProgramData\Package
Cache\{0c5773dd-0a10-45df-9f49-05cc6186a803}\ConfigInstaller.exe'
[10BC:1688][2014-06-24T08:31:10]i320: Registering bundle dependency provider:
{0c5773dd-0a10-45df-9f49-05cc6186a803}, version: 2.0.3.4
[1308:1100][2014-06-24T08:31:10]i338: Acquiring package:
DynagenCertInstall.msi, payload: DynagenCertInstall.msi, copy from:
C:\Users\bobbyranker\Documents\1.60.08\ConfigInstaller_v2_0_3_4\data\DynagenCertInstall.msi
[1308:1100][2014-06-24T08:31:12]i000: Setting string variable
'WixBundleLastUsedSource' to value
'C:\Users\bobbyranker\Documents\1.60.08\ConfigInstaller_v2_0_3_4\'
[10BC:14A8][2014-06-24T08:31:12]i305: Verified acquired payload:
DynagenCertInstall.msi at path: C:\ProgramData\Package
Cache\.unverified\DynagenCertInstall.msi, moving to: C:\ProgramData\Package
Cache\{0C955FEC-7D66-40A6-8099-374AAC3CA079}v1.2.2.0\data\DynagenCertInstall.msi.
[1308:1100][2014-06-24T08:31:12]i338: Acquiring package: DynagenHid_x86.msi,
payload: DynagenHid_x86.msi, copy from:
C:\Users\bobbyranker\Documents\1.60.08\ConfigInstaller_v2_0_3_4\data\DynagenHid_x86.msi
[10BC:14A8][2014-06-24T08:31:13]i305: Verified acquired payload:
DynagenHid_x86.msi at path: C:\ProgramData\Package
Cache\.unverified\DynagenHid_x86.msi, moving to: C:\ProgramData\Package
Cache\{3C7CA1E6-177D-4EC7-86F1-D80509A9DC93}v1.2.1.0\data\DynagenHid_x86.msi.
[1308:1100][2014-06-24T08:31:13]i338: Acquiring package: DynagenDfu_x86.msi,
payload: DynagenDfu_x86.msi, copy from:
C:\Users\bobbyranker\Documents\1.60.08\ConfigInstaller_v2_0_3_4\data\DynagenDfu_x86.msi
[10BC:14A8][2014-06-24T08:31:15]i305: Verified acquired payload:
DynagenDfu_x86.msi at path: C:\ProgramData\Package
Cache\.unverified\DynagenDfu_x86.msi, moving to: C:\ProgramData\Package
Cache\{F042A1F9-DE9D-4F0D-A8CA-C1E9C70BD314}v1.1.1.0\data\DynagenDfu_x86.msi.
[1308:1100][2014-06-24T08:31:15]i338: Acquiring package: ShellSetup.msi,
payload: ShellSetup.msi, copy from:
C:\Users\bobbyranker\Documents\1.60.08\ConfigInstaller_v2_0_3_4\data\ShellSetup.msi
[10BC:14A8][2014-06-24T08:31:18]i305: Verified acquired payload: ShellSetup.msi
at path: C:\ProgramData\Package Cache\.unverified\ShellSetup.msi, moving to:
C:\ProgramData\Package
Cache\{12680859-3246-4D2A-9F49-BC6384F2E9DE}v2.0.3.0\data\ShellSetup.msi.
[1308:1100][2014-06-24T08:31:18]i338: Acquiring package: TG350_Configs.msi,
payload: TG350_Configs.msi, copy from:
C:\Users\bobbyranker\Documents\1.60.08\ConfigInstaller_v2_0_3_4\data\TG350
Configs.msi
[10BC:14A8][2014-06-24T08:31:33]i305: Verified acquired payload:
TG350_Configs.msi at path: C:\ProgramData\Package
Cache\.unverified\TG350_Configs.msi, moving to: C:\ProgramData\Package
Cache\{F5F9A3B9-3461-4DA7-9153-87CB3E68CD69}v2.0.2.0\data\TG350 Configs.msi.
[1308:1100][2014-06-24T08:31:33]i338: Acquiring package: TG350AMF_Configs.msi,
payload: TG350AMF_Configs.msi, copy from:
C:\Users\bobbyranker\Documents\1.60.08\ConfigInstaller_v2_0_3_4\data\TG350AMF
Configs.msi
[10BC:14A8][2014-06-24T08:31:33]i305: Verified acquired payload:
TG350AMF_Configs.msi at path: C:\ProgramData\Package
Cache\.unverified\TG350AMF_Configs.msi, moving to: C:\ProgramData\Package
Cache\{E099BF1D-BF7C-44A4-A351-4FB7979E6D65}v2.0.2.0\data\TG350AMF Configs.msi.
[1308:1100][2014-06-24T08:31:33]i338: Acquiring package: TG410_Configs.msi,
payload: TG410_Configs.msi, copy from:
C:\Users\bobbyranker\Documents\1.60.08\ConfigInstaller_v2_0_3_4\data\TG410
Configs.msi
[10BC:14A8][2014-06-24T08:31:33]i305: Verified acquired payload:
TG410_Configs.msi at path: C:\ProgramData\Package
Cache\.unverified\TG410_Configs.msi, moving to: C:\ProgramData\Package
Cache\{E446A594-3900-40A7-AE84-4CB7B69C0520}v2.0.3.0\data\TG410 Configs.msi.
[10BC:1688][2014-06-24T08:31:33]i323: Registering package dependency provider:
{0C955FEC-7D66-40A6-8099-374AAC3CA079}, version: 1.2.2.0, package:
DynagenCertInstall.msi
[10BC:1688][2014-06-24T08:31:33]i301: Applying execute package:
DynagenCertInstall.msi, action: Install, path: C:\ProgramData\Package
Cache\{0C955FEC-7D66-40A6-8099-374AAC3CA079}v1.2.2.0\data\DynagenCertInstall.msi,
arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[10BC:1688][2014-06-24T08:32:13]e000: Error 0x8007006e: Failed to install MSI
package.
[10BC:1688][2014-06-24T08:32:13]e000: Error 0x8007006e: Failed to execute MSI
package.
[1308:08D0][2014-06-24T08:32:13]e000: Error 0x8007006e: Failed to configure
per-machine MSI package.
[1308:08D0][2014-06-24T08:32:13]w350: Applied non-vital package:
DynagenCertInstall.msi, encountered error: 0x8007006e. Continuing...
[10BC:1688][2014-06-24T08:32:13]i325: Registering dependency:
{0c5773dd-0a10-45df-9f49-05cc6186a803} on package provider:
{0C955FEC-7D66-40A6-8099-374AAC3CA079}, package: DynagenCertInstall.msi
[10BC:1688][2014-06-24T08:32:13]i323: Registering package dependency provider:
{3C7CA1E6-177D-4EC7-86F1-D80509A9DC93}, version: 1.2.1.0, package:
DynagenHid_x86.msi
[10BC:1688][2014-06-24T08:32:13]i301: Applying execute package:
DynagenHid_x86.msi, action: Install, path: C:\ProgramData\Package
Cache\{3C7CA1E6-177D-4EC7-86F1-D80509A9DC93}v1.2.1.0\data\DynagenHid_x86.msi,
arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[10BC:1688][2014-06-24T08:32:23]e000: Error 0x8007006e: Failed to install MSI
package.
[10BC:1688][2014-06-24T08:32:23]e000: Error 0x8007006e: Failed to execute MSI
package.
[1308:08D0][2014-06-24T08:32:23]e000: Error 0x8007006e: Failed to configure
per-machine MSI package.
[1308:08D0][2014-06-24T08:32:23]w350: Applied non-vital package:
DynagenHid_x86.msi, encountered error: 0x8007006e. Continuing...
[10BC:1688][2014-06-24T08:32:23]i325: Registering dependency:
{0c5773dd-0a10-45df-9f49-05cc6186a803} on package provider:
{3C7CA1E6-177D-4EC7-86F1-D80509A9DC93}, package: DynagenHid_x86.msi
[10BC:1688][2014-06-24T08:32:23]i323: Registering package dependency provider:
{F042A1F9-DE9D-4F0D-A8CA-C1E9C70BD314}, version: 1.1.1.0, package:
DynagenDfu_x86.msi
[10BC:1688][2014-06-24T08:32:23]i301: Applying execute package:
DynagenDfu_x86.msi, action: Install, path: C:\ProgramData\Package
Cache\{F042A1F9-DE9D-4F0D-A8CA-C1E9C70BD314}v1.1.1.0\data\DynagenDfu_x86.msi,
arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[10BC:1688][2014-06-24T08:32:27]e000: Error 0x8007006e: Failed to install MSI
package.
[10BC:1688][2014-06-24T08:32:27]e000: Error 0x8007006e: Failed to execute MSI
package.
[1308:08D0][2014-06-24T08:32:27]e000: Error 0x8007006e: Failed to configure
per-machine MSI package.
[1308:08D0][2014-06-24T08:32:27]i319: Applied execute package:
DynagenDfu_x86.msi, result: 0x8007006e, restart: None
[1308:08D0][2014-06-24T08:32:27]e000: Error 0x8007006e: Failed to execute MSI
package.
[10BC:1688][2014-06-24T08:32:27]i318: Skipped rollback of package:
DynagenDfu_x86.msi, action: Uninstall, already: Absent
[1308:08D0][2014-06-24T08:32:27]i319: Applied rollback package:
DynagenDfu_x86.msi, result: 0x0, restart: None
[10BC:1688][2014-06-24T08:32:27]i329: Removed package dependency provider:
{F042A1F9-DE9D-4F0D-A8CA-C1E9C70BD314}, package: DynagenDfu_x86.msi
----------------------
Example MSI Log: (the third MSI package, required. I have logs for the first
two packages and they appear similar)
=== Verbose logging started: 6/24/2014 8:32:23 Build type: SHIP UNICODE
5.00.7601.00 Calling process:
C:\Users\bobbyranker\Documents\1.60.08\ConfigInstaller_v2_0_3_4\ConfigInstaller.exe
===
MSI (c) (BC:2C) [08:32:23:426]: Resetting cached policy values
MSI (c) (BC:2C) [08:32:23:426]: Machine policy value 'Debug' is 0
MSI (c) (BC:2C) [08:32:23:426]: ******* RunEngine:
******* Product: C:\ProgramData\Package
Cache\{F042A1F9-DE9D-4F0D-A8CA-C1E9C70BD314}v1.1.1.0\data\DynagenDfu_x86.msi
******* Action:
******* CommandLine: **********
MSI (c) (BC:2C) [08:32:23:426]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (BC:2C) [08:32:23:426]: Grabbed execution mutex.
MSI (c) (BC:2C) [08:32:23:426]: Cloaking enabled.
MSI (c) (BC:2C) [08:32:23:426]: Attempting to enable all disabled privileges
before calling Install on Server
MSI (c) (BC:2C) [08:32:23:426]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (0C:28) [08:32:23:426]: Running installation inside multi-package
transaction C:\ProgramData\Package
Cache\{F042A1F9-DE9D-4F0D-A8CA-C1E9C70BD314}v1.1.1.0\data\DynagenDfu_x86.msi
MSI (s) (0C:28) [08:32:23:426]: Grabbed execution mutex.
MSI (s) (0C:F0) [08:32:23:426]: Resetting cached policy values
MSI (s) (0C:F0) [08:32:23:426]: Machine policy value 'Debug' is 0
MSI (s) (0C:F0) [08:32:23:426]: ******* RunEngine:
******* Product: C:\ProgramData\Package
Cache\{F042A1F9-DE9D-4F0D-A8CA-C1E9C70BD314}v1.1.1.0\data\DynagenDfu_x86.msi
******* Action:
******* CommandLine: **********
MSI (s) (0C:F0) [08:32:26:194]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (0C:F0) [08:32:26:194]: SRSetRestorePoint skipped for this transaction.
MSI (s) (0C:F0) [08:32:26:194]: Note: 1: 1309 2: 5 3: C:\ProgramData\Package
Cache\{F042A1F9-DE9D-4F0D-A8CA-C1E9C70BD314}v1.1.1.0\data\DynagenDfu_x86.msi
MSI (s) (0C:F0) [08:32:27:505]: MainEngineThread is returning 110
MSI (s) (0C:28) [08:32:27:505]: No System Restore sequence number for this
installation.
The system cannot open the device or file specified.
MSI (s) (0C:28) [08:32:27:505]: User policy value 'DisableRollback' is 0
MSI (s) (0C:28) [08:32:27:505]: Machine policy value 'DisableRollback' is 0
MSI (s) (0C:28) [08:32:27:505]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (0C:28) [08:32:27:505]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
3: 2
MSI (s) (0C:28) [08:32:27:505]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
3: 2
MSI (s) (0C:28) [08:32:27:505]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
3: 2
MSI (s) (0C:28) [08:32:27:505]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
3: 2
MSI (s) (0C:28) [08:32:27:505]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (0C:28) [08:32:27:505]: Restoring environment variables
MSI (c) (BC:2C) [08:32:27:505]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (BC:2C) [08:32:27:505]: MainEngineThread is returning 110
=== Verbose logging stopped: 6/24/2014 8:32:27 ===
-----Original Message-----
From: Hoover, Jacob [mailto:[email protected]]
Sent: June-26-14 10:31 PM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Windows 7 Professional - Package Cache and Encryption
Blind fixes are never a good thing. Is this a use case where the admin has
encryption turned on and it's a different user account that is escalating "as
admin" using the encrypted admin credentials? Is this a per user install or a
per machine install that you are seeing the issue? Do you have it logged with
what artifacts you do have from the sample of failed installs?
-----Original Message-----
From: Wesley Manning [mailto:[email protected]]
Sent: Thursday, June 26, 2014 6:05 PM
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Windows 7 Professional - Package Cache and Encryption
I just got the below issue again with a different customer (see end of e-mail):
Installer fails because MSI is encrypted. This is the third time now in about
a year. Anybody else seen this? I never seen anybody talk about it on any of
the mailing lists. Pretty weird if I'm the only one seeing it.
I remember reviewing the burn code and saw maybe there was a potential weakness
where encryption is not being removed from the cache folder. It was being
removed from the working folder. Rob asked me for a test case and I did set up
a VM of Win 7 Professional but was never able to reproduce it. I pasted that
conversion below.
I'm going to look into it again but posted here in the hopes someone else ran
into this. Is this something worth changing in the burn code even without a
repro? What are the risks?
Wes
---------------------------------------
Investigation:
From: Rob Mensching [mailto:[email protected]]
Hmm, that's a good point. It looks like Decrypt is only being done on the
working folder. It's possible we're not preventing the inheritance from the
LocalAppDataFolder!
Do you have a consistent repro of this issue?
On Mon, May 6, 2013 at 1:47 PM, Wesley Manning <[email protected]> wrote:
Can anyone tell me where the burn code checks/removes encryption from the
Package Cache? I see that encryption is removed from the working folder by the
method CacheEnsureWorkingFolder via method DecryptFileW but nothing for the
cache folder.
For the "Package Cache" folder the CreateCompletedPath method is used to create
the Package Cache directory and set ACL permissions.
Wes
---------------------------------------
Issue description:
-----Original Message-----
From: Wesley Manning [mailto:[email protected]]
I had a second customer where our burn installer failed on Windows 7
Professional x64. I had him go into the "Package Cache" folder and encryption
was not set on it and all subfolders but was set on the one remaining msi file.
I had him remove the encryption from the file and rerun the installer and it
then installed successfully. Must be a bug in rollback also because it left
one MSI there (I cache 3 in total). I guess good thing otherwise I wouldn't
have found the cause.
Has there been any problems with Visual Studio install for Windows 7
professional? If I've seen this twice Visual Studio team must have seen this
before. I tried reproducing this on my Windows 7 Ultimate x64 computer by
encrypting the package cache folder and then installing but it installed fine
(as you would expect).
Where is the encryption code located in the burn source code?
Maybe it should be changed to check MSI files before they are run from the
cache and decrypt them. What do you guys think?
Wes
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced analytics on
semi-structured data. The platform includes APIs for building apps and a
phenomenal toolset for data science. Developers can use our toolset for easy
data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse Turn
processes into business applications with Bonita BPM Community Edition Quickly
connect people, data, and systems into organized workflows Winner of BOSSIE,
CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse Turn
processes into business applications with Bonita BPM Community Edition Quickly
connect people, data, and systems into organized workflows Winner of BOSSIE,
CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
