Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#3183 Intermittent WriteIIS7ConfigChanges Errors

v3.8
migrated
nobody
None
2013-12-16
2013-01-10
Nick Hansen
No

Originally opened this as Bug 3089. Upgraded to 3.7.1224.0 and still having the issue. Repeated below with a new logging snippet.

On some major upgrade installs in an unpredictable and not-consistently-repeatable manner we are getting the follow error in a select number of deployment environments:

MSI (s) (68:84) [06:04:32:983]: Executing op: ActionStart(Name=StartIIS7ConfigTransaction,Description=Starting IIS Config Transaction,)
MSI (s) (68:84) [06:04:32:983]: Executing op: CustomActionSchedule(Action=StartIIS7ConfigTransaction,ActionType=11265,Source=BinaryData,Target=*,CustomActionData=*)
MSI (s) (68:9C) [06:04:33:046]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI860.tmp, Entrypoint: StartIIS7ConfigTransaction
MSI (s) (68:84) [06:04:33:108]: Executing op: ActionStart(Name=RollbackIIS7ConfigTransaction,Description=Rolling back IIS Config Transaction,)
MSI (s) (68:84) [06:04:33:124]: Executing op: CustomActionSchedule(Action=RollbackIIS7ConfigTransaction,ActionType=11521,Source=BinaryData,Target=*,CustomActionData=*)
MSI (s) (68:84) [06:04:33:124]: Executing op: ActionStart(Name=CommitIIS7ConfigTransaction,Description=Committing IIS Config Transaction,)
MSI (s) (68:84) [06:04:33:124]: Executing op: CustomActionSchedule(Action=CommitIIS7ConfigTransaction,ActionType=11777,Source=BinaryData,Target=*,CustomActionData=*)
MSI (s) (68:84) [06:04:33:124]: Executing op: ActionStart(Name=ConfigureIIs7Exec,Description=Configuring IIS,)
MSI (s) (68:84) [06:04:33:124]: Executing op: CustomActionSchedule(Action=ConfigureIIs7Exec,ActionType=11265,Source=BinaryData,Target=*,CustomActionData=*)
MSI (s) (68:FC) [06:04:33:171]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI8EE.tmp, Entrypoint: ConfigureIIs7Exec
MSI (s) (68:84) [06:04:33:327]: Executing op: ActionStart(Name=WriteIIS7ConfigChanges,Description=Installing Config Keys and Values,)
MSI (s) (68:84) [06:04:33:327]: Executing op: CustomActionSchedule(Action=WriteIIS7ConfigChanges,ActionType=11265,Source=BinaryData,Target=*,CustomActionData=*)
MSI (s) (68:D4) [06:04:33:374]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI9BA.tmp, Entrypoint: WriteIIS7ConfigChanges
WriteIIS7ConfigChanges: Error 0x80071a90: Failed to Commit IIS Config Changes
WriteIIS7ConfigChanges: Error 0x80071a90: WriteIIS7ConfigChanges Failed.
CustomAction WriteIIS7ConfigChanges returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (68:84) [06:04:33:874]: User policy value 'DisableRollback' is 0
MSI (s) (68:84) [06:04:33:874]: Machine policy value 'DisableRollback' is 0
Action ended 6:04:33: InstallFinalize. Return value 3.

We are using Wix Toolset v3.7.1224.0 and the target machines are Win2K8 64-bit servers.

I tried attaching the full log and sample wix, but the file size upload nixed that. Please let me know if you require additional resources to help troubleshoot.

Discussion

  • Rob Mensching
    Rob Mensching
    2013-03-04

    • Milestone: v3.7 --> v3.8
     
    • When we first reported this error in 3.6 (http://sourceforge.net/p/wix/bugs/3089/) the answer was to go to 3.7. Is this comment that this is being actively worked on in 3.8 or that there is some nebulous activity that we hope will fix this.

      We have installations over various products in a continous QA cycle that involves over 100 installations of our wix based products a day. We are getting a 1-2% failure rate with this a day, with no pattern of which product. It is proving to be be very impactful.

       
      • Rob Mensching
        Rob Mensching
        2013-03-25

        The actual suggestion was to use the final bits of WiX v3.6 since there were fixes done to IIS CA in that time frame. There were no fixes done to IIS CA in WiX v3.7 so this bug is being moved along until someone steps up to fix it.

        The unpredictable repro makes it difficult to track down in non-production situations.

         
  • It is impacting our daily deployment in some of our QA machines, we need a fix for this.

     
  • Rob Mensching
    Rob Mensching
    2013-03-25

    The unpredictable repro makes it difficult to hunt this bug down. If anyone has a small example .wxs file that reproduces the issue regularly, it would go a long way to helping us get a fix. That this point, it is not clear why the IIS CA transaction is sometimes getting aborted.

     
  • Peter Ivarsson
    Peter Ivarsson
    2013-08-19

    I got the same error:
    WriteIIS7ConfigChanges: Error 0x80071a90: Failed to Commit IIS Config Changes
    WriteIIS7ConfigChanges: Error 0x80071a90: WriteIIS7ConfigChanges Failed.
    CustomAction WriteIIS7ConfigChanges returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    This link helped me solve it: http://support.microsoft.com/kb/2876732
    Disabling the virus scanner, which locked some files, solved the problem.

     
  • Rob Mensching
    Rob Mensching
    2013-08-21

    • Status: open --> migrated