Take the 2-minute tour ×

A while back my Windows Server 2003 machine hung up and I needed to force-reboot by power-cycling it. When it was restarting it ran chkdsk, and chkdsk reported some problems.

Since then IISAdmin has not been able to start (which means that IIS doesn't work at all):

C:\WINDOWS\system32>sc query iisadmin

    SERVICE_NAME: iisadmin
    TYPE               : 20  WIN32_SHARE_PROCESS
    STATE              : 1  STOPPED
                            (NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN))
    WIN32_EXIT_CODE    : 1066  (0x42a)
    SERVICE_EXIT_CODE  : -2146893818  (0x80090006)
    CHECKPOINT         : 0x0
    WAIT_HINT          : 0x0

I suspected a corrupt Metabase so I tried restoring from a Metabase History file dated earlier than the crash -- but no luck.

Not really sure how to troubleshoot this further. There's one apparently-related error in the SYSTEM log that comes up regularly, event ID 10010 from DCOM:

The server {A9E69610-B80D-11D0-B9B9-00A0C922E750} did not register with DCOM
within the required timeout.

But I'm not sure if this actually sheds additional light or if it's just another warning that IISAdmin can't start.

Otherwise the Event logs are pretty empty of help. What's the next step to isolate this problem and fix it? I should point out that I don't have the luxury of rebooting this server very often -- it's an app server, and the users who depend on the app work until late at night, and I would need to be on-site to reboot it because it doesn't always restart reliably -- but I normally work off-site.

So if there's any way to keep investigating this without needing to reboot, I'm eager to hear it.

share|improve this question
add comment

2 Answers

According to winerror.h, 0x80090006 means "NTE_BAD_SIGNATURE", which is a return from the Win32 API call "CryptVerifyMessageSignature", and means that "The message's signature was not verified." Looks like a failure of a cryptographic signature check on some file related to the iisadmin startup, to me.

I'd consider doing an "SFC /SCANNOW" to see if you can replace the screwed-up file, assuming that the System File Checker can get to some Windows installation files, and assuming that it is a screwed-up file. (Yes-- "screwed-up" is a technical term. Sounds better than "corrupt" to me. Corrupt? Was the file taking bribes?)

If you're not getting it to work after an "SFC /SCANNOW", I'd probably fire up "Process Monitor" and watch what files are getting loaded. There will be a LOT of log entries generated, but you might find the needle in that haystack.

Given that the machine took a hard power-down and had some filesystem corruption, I'd put my money on "SFC /SCANNOW" finding one or more damaged files.

Aside: So, it won't restart reliably, eh? Gives me a "The web site is down!" kind of feeling... (DO NOT REBOOT THE WEB SERVER!!!!!! Heh heh...)

share|improve this answer
lol, thanks, I'll give SFC a try and report back –  Ben Dunlap Jun 18 '09 at 0:28
I looked into SFC and chickened out -- couldn't find any way to run it so that it would just report on possible problems, rather than automatically correcting them. So I've been using Process Monitor instead and unfortunately it hasn't shed too much light. I did finally find MSDN blog entry that seems related, though, and it keeps coming back to "reinstall IIS": blogs.msdn.com/vivekkum/archive/2009/02/14/… –  Ben Dunlap Jun 18 '09 at 18:28
"SFC /SCANNOW", from a command prompt, will do what you want. I'd do that before I'd reinstall IIS. –  Evan Anderson Jun 18 '09 at 18:56
It just occurred to me -- do you happen to know if the SFC utility uses VSS? Because that doesn't work on this server (yes, I know, the server is a wreck. Unfortunately it's also our primary machine and the most expensive piece of equipment in the building). It was actually a VSS operation that caused the lock-up that led to the hard-restart... ugh. –  Ben Dunlap Jun 18 '09 at 22:48
OK it's not as expensive as our digital printing press. Most expensive piece of strictly-IT equipment in the building. –  Ben Dunlap Jun 18 '09 at 22:48
show 2 more comments

Just re-install IIS from Add/Remove Programs > Windows Components. I have installed it before on Windows 2003 servers before and have not had to reboot.

share|improve this answer
Oh. Didn't realize I could do that. I thought I had to remove and then re-add the "application server" role -- which would also turn off some other stuff that our non-web-based apps rely on, thus being the practical equivalent of a reboot. I will try the Windows Components approach if I can't dig anything up with SFC or Procmon, thanks. –  Ben Dunlap Jun 18 '09 at 15:22
add comment

Your Answer


