Errors with IIS 6 on W2003 Web Ed.

After running IIS 6 without problems over the last few years, I've recently
began getting errors and I have no idea why.

From IIS Management Console, I choose 'Properties' of a website, then get an
error 'No such interface supported' just as soon as I click on the 'Home
Directory Tab'.

Also, I get a 'Metadata has not been initialized' error when trying to
'Create Application'

What I have done to try to fix the problem is to run 'cscript adsutil.vbs
enum' at the command prompt (c:\inetpub\adminscripts). The utility runs but
the same problems persist.

Please note that I never created a metabase backup. I found nothing
relevant in the event log, is there something else that I can try?

Re: Errors with IIS 6 on W2003 Web Ed.

If you have never done a metabase backup, then I recommend you do it
soon. If your hard drive fails and you lose the metabase without
backup, then you might as well rebuild the server from scratch.

Just think that hard drives fail in average of 3 years, and you do the
math of how important a backup and disaster recovery plan is to any
organization running a web server...

I actually think that you have COM+ issue because if the metabase is
corrupt you won't even be able to open the properties dialog page. COM
+ is involved with "Create Application" and the "Home Directory" tab.

I don't know what is telling you to run: 'cscript adsutil.vbs enum' as
a fix, but that does nothing of the sort.

If you haven't installed any software patches lately, then I simply
suspect that your hard drive is showing its age and starting to
randomly corrupt data. It just happens to nail COM+ configuration and
now you are hosed. I don't really know how to reinstall COM+.

What happens when you try to run the command:
dcomcnfg.exe

Can you actually navigate to the IIS Application Package within that
DCOM Explorer and view its settings? Because that's what gets invoked
when you click "Create Application" in IIS Management UI.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Aug 9, 5:34 pm, Jeff Dunlap
wrote:
> After running IIS 6 without problems over the last few years, I've recently
> began getting errors and I have no idea why.
>
> From IIS Management Console, I choose 'Properties' of a website, then get an
> error 'No such interface supported' just as soon as I click on the 'Home
> Directory Tab'.
>
> Also, I get a 'Metadata has not been initialized' error when trying to
> 'Create Application'
>
> What I have done to try to fix the problem is to run 'cscript adsutil.vbs
> enum' at the command prompt (c:\inetpub\adminscripts). The utility runs but
> the same problems persist.
>
> Please note that I never created a metabase backup. I found nothing
> relevant in the event log, is there something else that I can try?

Re: Errors with IIS 6 on W2003 Web Ed.

David,

Thank you kindly for your response.

>> What happens when you try to run the command:
dcomcnfg.exe

I ran dcomcnfg.exe from the command prompt successfully brings up MMC with
the title Component Services.

I hadn't thought that it may be a HD issue like you suggested, but maybe
that is what is happening. I rarely run checkdisk and it has been many
months since the last time I did due to the fact that it is a production web
server. Oh, another thing that I failed to mention in the original post is
that the server's memory and processor consumption is low at all times yet
the system reboots by itself at least twice a month--sometimes even every
other day for 2 or 3 days but never exceeding more than 4 or 5 reboots per
month. The message produced in the event log is:

Event Type: Error
Event Source: Winlogon
Event Category: None
Event ID: 1015
Date: 7/26/2007
Time: 6:41:28 PM
User: N/A
Computer: xxx-xxx
Description:
A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status
code . The machine must now be restarted.

Does it still appear to be corruption due to HD problems? I'm thinking that
if this is the case, I think that I may install a new drive and rebuild the
machine.

Thanks in Advance

Re: Errors with IIS 6 on W2003 Web Ed.

lsass.exe is not supposed to crash, and certainly not that often. I'm
suspecting:
- Either the file is subtly corrupted
- Or you have an application that is loading code into lsass.exe and
crashing
- Or lsass.exe has an exploitable security bug that is being exploited
- Or lsass.exe has a bug that is just regularly crashing
- Or the system is handling a lot of user authentications that simply
exhaust resources over time

This may/not have anything to do with what you observe with lsass.exe.
I'm guessing that you now see the issue with IIS Manager UI all the
time and not just occassionally?


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Aug 10, 12:18 pm, Jeff Dunlap
wrote:
> David,
>
> Thank you kindly for your response.
>
> >> What happens when you try to run the command:
>
> dcomcnfg.exe
>
> I ran dcomcnfg.exe from the command prompt successfully brings up MMC with
> the title Component Services.
>
> I hadn't thought that it may be a HD issue like you suggested, but maybe
> that is what is happening. I rarely run checkdisk and it has been many
> months since the last time I did due to the fact that it is a production web
> server. Oh, another thing that I failed to mention in the original post is
> that the server's memory and processor consumption is low at all times yet
> the system reboots by itself at least twice a month--sometimes even every
> other day for 2 or 3 days but never exceeding more than 4 or 5 reboots per
> month. The message produced in the event log is:
>
> Event Type: Error
> Event Source: Winlogon
> Event Category: None
> Event ID: 1015
> Date: 7/26/2007
> Time: 6:41:28 PM
> User: N/A
> Computer: xxx-xxx
> Description:
> A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status
> code . The machine must now be restarted.
>
> Does it still appear to be corruption due to HD problems? I'm thinking that
> if this is the case, I think that I may install a new drive and rebuild the
> machine.
>
> Thanks in Advance