in Search

Do you Twitter? Follow us @CodeBetter

Darrell Norton's Blog [MVP]

Fill in description here...

IIS 6 Tip

Make sure you have enough disk space for all the metabase history xml files. If IIS can't create a new history file due to insufficient disk space, it will automatically shut down without warning or explanation.

Published May 11 2004, 06:19 PM by darrell

Comments

Jeff Key said:

Wow, great to know. Thanks!

# May 11, 2004 2:58 PM

Darrell said:

Sure thing Jeff!

# May 12, 2004 1:57 AM

Bernard said:

I was told it won't shutdown and it does write to event log when disk full. Event ID 51257 and 51228.

Cheers.

# May 12, 2004 7:16 PM

Darrell said:

Bernard - I got this from the new Windows Server tips book. I hope the author did his research.

# May 13, 2004 2:10 AM

Bernard said:

Ya. I haven't tested it, but I got it from MS.

# May 13, 2004 3:41 PM

Darrell said:

You probably know better than me, being an IIS MVP and all! :)

# May 13, 2004 3:55 PM

Bernard said:

Cheers :) If I ever bump to this event id, I will give you a buzz.

# May 13, 2004 7:29 PM

Darrell said:

Deal!

# May 14, 2004 2:20 AM

Salonge said:

I got this error. I discovered when I could not sent email across the network. I have plenty of space on my disk (2 gb). I shut down my server and restarted and it seemed to clear up the problem. Can anyone tell me why this happened?

# June 28, 2004 9:06 AM

Darrell said:

Salonge - what error?

# June 29, 2004 1:26 AM

Eric said:

I have a similar situation as Salonge. Our Exchange 2003 (on Win 2003) server is logging the following text in the system log:

An error occurred while saving the metabase file. This can happen when the metabase XML file is in use by another program, or if the disk is full. Check for corresponding events in the event log for more details.
ErrorCode : 0x8007000E

The source is IIS Config, event ID 51228.
The sysmptoms are queues (in and out) are filling up and mail transfer is extremely slow. Any ideas?
eric@musictoday.com

# July 14, 2004 5:30 AM

Darrell said:

Do you have a quota enabled? If not, use WhosLocking to figure out which process is locking the file.

http://www.codeguru.com/Cpp/W-P/dll/article.php/c3641/

# July 14, 2004 6:18 AM

Eric said:

Thanks for responding. No, we are not using quotas. So far only inetinfo.exe and a couple of system processes (which we think are metabase backups) are hitting the metabase file. Have you heard of other people reporting problems like this?

Thanks,
Eric
eric@musictoday.com

# July 14, 2004 7:39 AM

Darrell said:

Eric, try this KB article:

http://support.microsoft.com/?kbid=269794

# July 14, 2004 8:10 AM

Eric said:

Thanks, Darrell. We looked at this, but are a bit leary using it in Exchange 2003. They only list Exhcange 5.5 in the notes. Also, we can get dozens of positive hits on the error code, ranging from Exchange and Outlook to even ASP/IIS. It seems to be a fairly generic 'out of memory' error. This is a real head scratcher...

# July 14, 2004 8:35 AM

Darrell said:

Sounds like it.

# July 14, 2004 8:54 AM

joesterba@nuvotec.com said:

We just started getting this IIS Config EventID: 51228 error on our new Exchange Server which shutdown our external mail. We have plenty of disk space. So we are trying to figure out where the conflict is.

# August 2, 2004 6:12 AM

Chris said:

Has any one figured this one out yet. I am having the same thing happen as Joe.

# August 16, 2004 4:32 AM

Jeff said:

I am having the same error, event id 51228 in my system log and have lots of disk space available. If I figure out why this is happening I will post.

# September 16, 2004 1:26 AM

Jeff said:

http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/en/wc030403/wct030403.asp

Take a look at that link. It talks about metabase corruption.

# September 16, 2004 1:36 AM

Darrell said:

Thanks Jeff!

# September 16, 2004 1:43 AM

Jeff said:

Also make sure your DNS is setup properly. I just solved mine and it was because the alternate DNS on the exchange 2003 server was an old DNS machine that no longer exists and the server tried to use the alternate DNS for some reason. This caused the smtpsvc to fail and start the whole metabase issue. I recycled IIS Admin along with the other dependants after I properly reconfigured the alternate DNS and now my issue is gone.

# September 16, 2004 2:08 AM