cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
klacounte
Level 6

Bug in caCreateVRoots - Creating app pools

I've just converted an IS v12 project to IS 2008 and found a bug in the caCreateVRoots custom action. I've duplicated the problem with a new IS 2008 project and have tried it on three Windows 2003 servers (2 SP2, 1 SP1) and it fails on each. I've attached the project file to duplicate it and included a section of the log below. I'm guessing there is a handle that's not being closed in the previous OpenKey call. If an IS engineering can investigate, I'd appreciate it.

Log:
1: This appears to be a new apppool.
MSI (s) (C4!64) [23:18:38:448]: Closing MSIHANDLE (248) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:448]: Creating MSIHANDLE (249) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:464]: Closing MSIHANDLE (249) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:464]: Creating MSIHANDLE (250) of type 790531 for thread 2916
Action 23:18:38: Progress Custom Action. Creating application pool AppPool3
MSI (s) (C4!64) [23:18:38:464]: Closing MSIHANDLE (250) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:464]: Creating MSIHANDLE (251) of type 790531 for thread 2916
1: CreateAppPoolFunction
MSI (s) (C4!64) [23:18:38:464]: Closing MSIHANDLE (251) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:464]: Creating MSIHANDLE (252) of type 790531 for thread 2916
1: OpenKeyLog, pszMDPath =/LM
MSI (s) (C4!64) [23:18:38:464]: Closing MSIHANDLE (252) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:464]: Creating MSIHANDLE (253) of type 790531 for thread 2916
1: AddKey, pszMDPath = /W3SVC/AppPools/AppPool3
MSI (s) (C4!64) [23:18:38:480]: Closing MSIHANDLE (253) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:480]: Creating MSIHANDLE (254) of type 790531 for thread 2916
1: OpenKeyLog, pszMDPath =/LM/W3SVC/AppPools/AppPool3
MSI (s) (C4!64) [23:18:38:480]: Closing MSIHANDLE (254) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:495]: Creating MSIHANDLE (255) of type 790531 for thread 2916
1: Error: OpenKey failed for /LM/W3SVC/AppPools/AppPool3. HRESULT = HRESULT_FROM_WIN32(ERROR_PATH_BUSY)
MSI (s) (C4!64) [23:18:38:495]: Closing MSIHANDLE (255) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:495]: Creating MSIHANDLE (256) of type 790531 for thread 2916
1: Error adding apppool key.
MSI (s) (C4!64) [23:18:38:495]: Closing MSIHANDLE (256) of type 790531 for thread 2916
MSI (s) (C4!64) [23:18:38:542]: Creating MSIHANDLE (257) of type 790531 for thread 2916
1: Error with IISRT: -2147024748
MSI (s) (C4!64) [23:18:38:558]: Closing MSIHANDLE (257) of type 790531 for thread 2916
MSI (s) (C4:88) [23:18:38:558]: Closing MSIHANDLE (182) of type 790536 for thread 3768
Action ended 23:18:38: InstallFinalize. Return value 3.
Labels (1)
0 Kudos
(6) Replies
klacounte
Level 6

I'm guessing there isn't a workaround for this. I'm reverting back to IS12 until this gets addressed. I'll submit an official bug request and hope this gets fixed in SP1.
0 Kudos
davidh
Level 6

I ran this against the dll here and could not reproduce:
http://community.macrovision.com/showthread.php?p=397290#post397290
0 Kudos
syaeger
Level 2

Could someone please post an updated link for davidh's previous post...

I have an InstallShield 2008 Project that creates the AppPool in Windows Server 2003 , but fails in Windows Server 2008.

This is the error that is generated...

1: Attempt to change property value had problems, HRESULT: -2105
1: Error adding apppool key.
1: Error with IISRT: -2105

I was hopping the dll davidh refered to in his post, might also work for me. But his link appears to be broken...

Thanks
0 Kudos
MichaelU
Level 12 Flexeran
Level 12 Flexeran

The link is still mostly valid; only the host is incorrect. Here's an alternate version: http://community.installshield.com/showthread.php?p=397290#post397290
0 Kudos
syaeger
Level 2

Thanks! That fixed it.
0 Kudos
Christopher_Pai
Level 16

I've seen this intermittently on Windows 2003 Server VM's running an IS12 install. I don't know what IS uses for a timeout value when interacting with IIS but every once in awhile I seem to exceed it.
0 Kudos