Hello,
I'm at wits end trying to make an installer that does nothing more than create
an IIS7 app pool and set a registry key. No matter what I've tried, the
application pool never gets created, but the registry key is written. They are
both part of the same component like the following:
<Directory Id="TARGETDIR" Name="SourceDir">
<!-- Install stuff into program files folder. -->
<Directory Id="ProgramFilesFolder">
<Component Id="MyAppPoolComponent"
Guid="PUT_GUID_HERE"
KeyPath="yes">
<util:User Id="PoolAccount"
Domain="[DOMAIN_NAME]"
Name="[USER_NAME]"
CreateUser="no"/>
<iis:WebAppPool Id="MyAppPool"
Name="MYPool"
ManagedRuntimeVersion="v4.0"
ManagedPipelineMode="classic"
Identity="other"
User="PoolAccount">
<iis:RecycleTime Value="05:00" />
</iis:WebAppPool>
<CreateFolder/>
</Component>
<Component Id="MyAppPoolRegKeys"
Guid="PUT-GUID-HERE"
KeyPath="yes">
Both DOMAIN_NAME and USER_NAME are valid and I have tried setting the password
attribute as well.
The problem appears to be in the bowls of the ConfigureIIs custom action. I've
set LOGVERBOSE=1 and the only information I get in the /l*vx logs from
ConfigureIIs is just the following:
MSI (s) (D8:48) [16:01:03:946]: Doing action: ConfigureIIs
Action start 16:01:03: ConfigureIIs.
MSI (s) (D8:48) [16:01:03:946]: Creating MSIHANDLE (226) of type 790542 for
thread 2120
MSI (s) (D8:CC) [16:01:03:946]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSIDB77.tmp, Entrypoint: ConfigureIIs
MSI (s) (D8!08) [16:01:03:978]: Creating MSIHANDLE (227) of type 790541 for
thread 1544
MSI (s) (D8!08) [16:01:03:978]: Closing MSIHANDLE (227) of type 790541 for
thread 1544
MSI (s) (D8:CC) [16:01:03:978]: Closing MSIHANDLE (226) of type 790542 for
thread 2120
Action ended 16:01:03: ConfigureIIs. Return value 1.
In another installer, I can use WebAppPool to access existing app pools just
fine when used outside the component.
Any ideas or hints? Please don't make me resort to appcmd. :)
Also, I'm going to file a bug report for WiX 3.6 that they start adding the PDB
files for the CAs to the distributions. If I had those, I'd break in and be
able to debug the CA myself.
John
Wintellect
http://www.wintellect.com
+1-877-968-5528
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
