Fix was just checked-in. If all goes well, build that comes out tomorrow will be much happier.
-----Original Message----- From: Uwe Stump [mailto:uwe.st...@gewi.com] Sent: Friday, January 30, 2009 01:14 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] SetupBld and IIs Problem Rob, I think, you are right. The problem does not occur in WiX 3.0.4827.0. So I will try to open a bug. Be warned ;-) Kind regards and many thanks for your help, Uwe -----Ursprüngliche Nachricht----- Von: Rob Mensching [mailto:rob.mensch...@microsoft.com] Gesendet: Donnerstag, 29. Januar 2009 17:23 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] SetupBld and IIs Problem I think this is a bug introduced with the large changes to IIS CA recently to handle UAC/IIS7 better. Can you try an older build and see if the problem reproduces there? If it does repro with older builds then please open a bug with as much information as possible (especially the info below). Thanks. -----Original Message----- From: Uwe Stump [mailto:uwe.st...@gewi.com] Sent: Thursday, January 29, 2009 04:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] SetupBld and IIs Problem Dear all, after some research I found a workaround: I do wrap my msi to an exe file with setupbld now by using the command line option -msuc (c added). c means "enable msi caching". So the whole msi gets cached in Windows\Installer. On uninstall the msi file will be found by MSI and the message box: "The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'IIsInstallerProblem.msi' in the box below." doesn't appear. I don't know if this is ok. What's your opinion? I don't know why I need the switch in this case (reference to IIsExtensions) but in the other cases (without IIsExtensions) not. ("Resolving source" between -Action ended 09:17:40: CommitMetabaseTransaction and -Action start 09:18:35: ConfigureIIsExec.) Many thanks to Bob, he gave me a good starting point ("Check a verbose log to see what resource MSI is looking for from the original database"). Kind regards, Uwe ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users