I've executed the steps in MS article 315296, "How to clean up a damaged
COM+ catalog." The last step seems to just hang. I enter this at a
command prompt:
Rundll32 c:\windows\system32\inetsrv\wamreg.dll, CreateIISPackage.
It does nothing for 30 minutes or more. How long should I wait? Is there a
log file generated somewhere?
rundll32 problem
Moderators: DllAdmin, DLLADMIN ONLY
Re: rundll32 problem
Duh. Earlier in the process I'd had to resort to safe mode, as the article
suggests. I just didn't think of it again when I hit this snag. Safe mode
solved it.
"Laurel" <FakeMail@Hotmail.com> wrote in message
news:%236AURBzUKHA.4484@TK2MSFTNGP02.phx.gbl...
> I've executed the steps in MS article 315296, "How to clean up a damaged
> COM+ catalog." The last step seems to just hang. I enter this at a
> command prompt:
>
>
>
> Rundll32 c:\windows\system32\inetsrv\wamreg.dll, CreateIISPackage.
>
>
>
> It does nothing for 30 minutes or more. How long should I wait? Is there
> a log file generated somewhere?
>
>
suggests. I just didn't think of it again when I hit this snag. Safe mode
solved it.
"Laurel" <FakeMail@Hotmail.com> wrote in message
news:%236AURBzUKHA.4484@TK2MSFTNGP02.phx.gbl...
> I've executed the steps in MS article 315296, "How to clean up a damaged
> COM+ catalog." The last step seems to just hang. I enter this at a
> command prompt:
>
>
>
> Rundll32 c:\windows\system32\inetsrv\wamreg.dll, CreateIISPackage.
>
>
>
> It does nothing for 30 minutes or more. How long should I wait? Is there
> a log file generated somewhere?
>
>