This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
cclouston
Level 3
‎Oct 17, 2011 06:13 PM

Error with IISRT: -1225

Hi. I'm pretty to new InstallShield so forgive me if this is in the wrong forum or is obvious. I've searched the forums and kb articles and haven't found an answer.

Our installer fails with the following error:

MSI (s) (D0:A8) [14:42:03:189]: Doing action: ISIISCosting
Action 14:42:03: ISIISCosting.
Action start 14:42:03: ISIISCosting.
MSI (s) (D0:14) [14:42:03:204]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI4329.tmp, Entrypoint: ISIISCosting
Action 14:42:03: Progress Custom Action. Extracting information for IIS virtual directories...
InstallShield 14:42:03: Error with IISRT: -1225
Action ended 14:42:03: ISIISCosting. Return value 3.
Action ended 14:42:03: INSTALL. Return value 3.

Can someone please telll me what error -1225 means? Thanks!
Labels (1)
Labels
0 Kudos
(3) Replies
cclouston
Level 3
‎Oct 18, 2011 09:48 AM

I found here:
C:\Program Files (x86)\InstallShield\2010\Script\Isrt\Include\IISRTErr.h

...that -1225 is:

ERROR_IISRT_INVALID_WEBSERVICEEXTENSIONFILE

So I have a bit more direction than I did. If anyone can help with what exactly that means, it'd be much appreciated.
0 Kudos
artevseev
Level 3
‎Oct 24, 2011 05:44 AM

Maybe this reference could help? http://community.installshield.com/archive/index.php?t-157080.html
0 Kudos
cclouston
Level 3
‎Oct 25, 2011 11:31 AM

Thanks for the suggestion, artevseev, but I don't think that was the same issue.

I believe I've solved the issue, but first some more detail on what was going on:

1) The installer only failed in some environments, not all.
2) The following was in the installation log prior to the -1225 error:

Info 1402.Could not open key: HKEY_LOCAL_MACHINE32\SOFTWARE\Wow6432Node\Microsoft\ASP.NET\2.0.50727.0. System error 161. Verify that you have sufficient access to that key, or contact your support personnel.

What stood out immediately was HKLM32 with Wow6432Node. For background info, look up how registry redirection works for 32bit keys on 64bit systems. Short story though, when a 32bit application requests certain keys, it is automatically redirected to the Wow6432Node, meaning you shouldn't explicitly need to have the Wow node in the path.

The fix I tried was to remove Wow6432Node from the path in the RegLocator table, and leave it set to scan the 32bit registry. Doing this fixed the installation issue and removed the IISRT error.

After further investigation, the client who was having the installation issue was using Server 2008. I believe on 2008 this registry redirection fails, and on the more forgiving 2008 R2 it succeeds. This would explain why only some environments had the issue. I haven't properly tested this hypothesis though.
0 Kudos