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

WriteIIS7ConfigChanges: Error 0x800700b7: Failed to Commit #2755

Closed
wixbot opened this issue Jul 15, 2010 · 3 comments
Closed

WriteIIS7ConfigChanges: Error 0x800700b7: Failed to Commit #2755

wixbot opened this issue Jul 15, 2010 · 3 comments

Comments

@wixbot
Copy link

wixbot commented Jul 15, 2010

Using Wix 3.5.1909.0

I am able to successfully generate an msi and install a website in IIS7.5 using Wix. However, when I try installing a second website (generated from the same wix version), I experience the following error:

MSI (s) (20:E8) [12:55:03:962]: Executing op: ActionStart(Name=StartIIS7ConfigTransaction,Description=Starting IIS Config Transaction,)
MSI (s) (20:E8) [12:55:03:962]: Executing op: CustomActionSchedule(Action=StartIIS7ConfigTransaction,ActionType=11265,Source=BinaryData,Target=_,CustomActionData=__)
MSI (s) (20:F0) [12:55:03:976]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI7571.tmp, Entrypoint: StartIIS7ConfigTransaction
MSI (s) (20:E8) [12:55:03:990]: Executing op: ActionStart(Name=RollbackIIS7ConfigTransaction,Description=Rolling back IIS Config Transaction,)
MSI (s) (20:E8) [12:55:03:990]: Executing op: CustomActionSchedule(Action=RollbackIIS7ConfigTransaction,ActionType=11521,Source=BinaryData,Target=
__,CustomActionData=__)
MSI (s) (20:E8) [12:55:03:990]: Executing op: ActionStart(Name=CommitIIS7ConfigTransaction,Description=Committing IIS Config Transaction,)
MSI (s) (20:E8) [12:55:03:990]: Executing op: CustomActionSchedule(Action=CommitIIS7ConfigTransaction,ActionType=11777,Source=BinaryData,Target=
_
_,CustomActionData=__)
MSI (s) (20:E8) [12:55:03:991]: Executing op: ActionStart(Name=WriteIIS7ConfigChanges,Description=Installing Config Keys and Values,)
MSI (s) (20:E8) [12:55:03:992]: Executing op: CustomActionSchedule(Action=WriteIIS7ConfigChanges,ActionType=11265,Source=BinaryData,Target=
_
_,CustomActionData=_****)
MSI (s) (20:78) [12:55:04:001]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI7591.tmp, Entrypoint: WriteIIS7ConfigChanges
WriteIIS7ConfigChanges: Error 0x800700b7: Failed to Commit IIS Config Changes
WriteIIS7ConfigChanges: Error 0x800700b7: WriteIIS7ConfigChanges Failed.
CustomAction WriteIIS7ConfigChanges returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Many Thanks

Originally opened by mattmcgregor from http://sourceforge.net/p/wix/bugs/2179/

@wixbot
Copy link
Author

wixbot commented Sep 15, 2012

We used to have this problem when we were not properly generating new IDs for Websites. That should be fixed in the most recent builds. Can you retry this with the latest weekly build and see if it still repros?
If the problem still occurs in the latest build, can you share your wix source for both installers? If possible also share your applicationHost.config (in c:\windows\system32\inetsrv\config) at the time of the failure.
Thanks!
Eric

@wixbot
Copy link
Author

wixbot commented Sep 15, 2012

Thanks for the reply Eric.

You were correct in your suggestion that the problem was related to the SiteId setting of the Website node. Our IIS6 setting for this attribute was SiteId="*".

The documentation states:
Optional attribute to directly specify the site id of the WebSite. Use this to ensure all web sites in a web garden get the same site id. If a number is provided, the site id must be unique on all target machines. If "" is used, the Description attribute will be hashed to create a unique value for the site id. This value must be a positive number or a "" or a formatted value that resolves to "-1" (for the same behavior as "*") or a positive number or blank. If this attribute is absent then the web site will be located using the WebAddress element associated with the web site.

However, as my original description details, the setting of * produces the same site Id regardless of the description attribute value. This may be related to hashing functionality on a 64 bit machine. We have hardcoded each service's site Id for the moment.

Many Thanks
Matt

@wixbot
Copy link
Author

wixbot commented Sep 15, 2012

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

@wixbot wixbot added this to the v3.5 milestone Dec 20, 2015
@wixbot wixbot closed this as completed Dec 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant