Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging should indicate payload being sought when acquiring container #4758

Closed
wixbot opened this issue May 11, 2015 · 2 comments · Fixed by wixtoolset/burn#48
Closed

Logging should indicate payload being sought when acquiring container #4758

wixbot opened this issue May 11, 2015 · 2 comments · Fixed by wixtoolset/burn#48
Assignees
Milestone

Comments

@wixbot
Copy link

wixbot commented May 11, 2015

I have spent quite a chunk of time debugging an issue for the following situation

[1624:2E48][2015-05-08T18:48:32]i300: Apply begin
[2584:18BC][2015-05-08T18:48:32]i360: Creating a system restore point.
[2584:18BC][2015-05-08T18:48:40]i361: Created a system restore point.
[2584:2DC4][2015-05-08T18:48:40]i304: Verified existing payload: RequirementCheck at path: C:\ProgramData\Package Cache\xxxxxxxxxxxxxxxx\RequirementCheck.exe.
[2584:18BC][2015-05-08T18:48:40]i301: Applying execute package: RequirementCheck, action: Install, path: C:\ProgramData\Package Cache\xxxxxxxxxxxxxxxx\RequirementCheck.exe, arguments: '...'
[1624:2E48][2015-05-08T18:48:49]i319: Applied execute package: RequirementCheck, result: 0x0, restart: None
[1624:2E48][2015-05-08T18:48:50]i399: Apply complete, result: 0x0, restart: None, ba requested restart:  No

As you can see from the log there is a package called RequirementCheck which is called during the Installation. Since this package is not really installed and only run during the installation chain, I set its Cache property to Cache="no"

<ExePackage Id="RequirementCheck" Compressed="yes" PerMachine="yes" Permanent="yes" Cache="no" ... />

During the the past few days I wanted to add "Modify / Change" Support to the Installation and always ran into this error

[2C64:2A68][2015-05-08T18:35:37]i300: Apply begin
[2C64:2274][2015-05-08T18:35:44]w341: Prompt for source of container: WixAttachedContainer, path: C:\...\Bootstrapper.exe
[2C64:2274][2015-05-08T18:35:44]e054: Failed to resolve source for file: C:\...\Bootstrapper.exe, error: 0x80070002.
[2C64:2274][2015-05-08T18:35:44]e000: Error 0x80070002: Failed while prompting for source (original path 'C:\...\Bootstrapper.exe').
[2C64:2274][2015-05-08T18:35:44]e311: Failed to acquire container: WixAttachedContainer to working path: C:\...\{GUID}\RANDOMNUMBER, error: 0x80070002.
[2C64:2A68][2015-05-08T18:35:44]e000: Error 0x80070002: Failed while caching, aborting execution.
[2C64:2A68][2015-05-08T18:35:44]i399: Apply complete, result: 0x80070002, restart: None, ba requested restart:  No

As you can see in the log, there is absolutely no feedback as to why the installer wants the original bootstrapper file (because of the the uncached (missing) RequirementCheck).

It took me a lot of time to understand the issue at hand and the fix is extremely simple and understandable.

Could you please expand the logging Information about missing packages during the Installation / repair / change / modify chain to make it more clear when something is missing

Originally opened by martin

@wixbot
Copy link
Author

wixbot commented May 11, 2015

This post helped me to identify the issue and it may be related

Originally posted by martin

@wixbot
Copy link
Author

wixbot commented May 19, 2015

Logging should be improved.

Release changed from v3.9 to v4.x
Type changed from Bug to Feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants