Exchange 2003 IS unmounts database

15 pts.
Tags:
Exchange 2003
Exchange 2003 administration
Exchange 2003 SP2
Exchange 2003 Standard Edition
Hi Knowledge Exchange,

I have an Exchange 2003 sp2 server (version 6.5 build 7638.2) on Windows Server 2003 sp2 with about 100 users. Very recently it started to Unmount the Information Store at odd times with event id 1216, and the message:

"The Exchange store 'First Storage GroupPublic Information Store (mailsrvr)' is limited to 36 GB. The current physical size of this database (the .edb file and the .stm file) is <1 GB. If the physical size of this database minus its logical free space exceeds the limit of 36 GB, the database will be dismounted on a regular basis."

Using the information from the article : http://technet.microsoft.com/en-us/library/aa998066(EXCHG.65).aspx

I increased the database size limit to 50gb, however, the same thing occured with the same errors. This continued for several hours until I increased the database limit to 75gb and finially it stopped.

This cant be a good solution as we will certainly hit the 75gb mark in the future.

What is the correct solution to this problem?

Thanks in advance, Rhrivera



Software/Hardware used:
Exchange 2003 Information Store
ASKED: January 10, 2011  9:26 PM
UPDATED: June 15, 2012  3:30 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

The event you are seeing, #1216, seems to be merely an informational message. See<a href=”http://www.msexchange.org/tutorials/Explaining-Database-size-limit-changes-Exchange-2003-Service-Pack-2.html”> Explaining the Database size limit changes in Exchange 2003 Service Pack 2 </a> for an explanation. It should appear each time you mount the store.

If your store is actually dismounting, or the IS service stopping, you’ll need to look further for the source of the problem.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Rhrivera
    The Store is actually being dismounted. There are other error messages to the effect that the IS store service has stopped. This eventid 1216 message is the only indication of WHY it is being dismounted. I have already read the article that you refer to, infact, that was what lead me to the technet article that specifically addresses increasing the database limit. Thanks for trying.
    15 pointsBadges:
    report
  • MartinX
    My recommendation is to 1.) Upgrade to the enterprise version of Exchange Server 2003 (I believe this can be done in-place) and then 2.) Create new storage groups and mailbox stores and distribute the mailboxes from the existing database evenly. MS does not recommend having an Ex 2003 database larger than 100 GB (I didn't see an actual KB or anything, but a MS support tech told me), so 75 GB is getting up there. Imagine if there was some physical disk corruption and the entire database got hosed. If you split the current database into several, one corrupt database won't bring all your users down.
    20 pointsBadges:
    report
  • Stevesz
    What kind of free space do you have on the drive where the IS is located? If your backup is not doing its job, the space could be filling with logs, and this would cause the store to dismount. How is your server anti-virus scanning? If you have not excluded the Exchange directories, specifically MDBDATA where the store is located, this may cause your store to dismount, and other weird Exchange stuff, including corruption of the store. Have you set the service to restart if it is stopped? It will not stop the store from dismounting, but can keep it up for you while you look for a solution. You should be getting some error message indicating the cause of the problem. You might want to increase the logging of the store activities while you are looking for a solution. The dismount of the store should be throwing an error message out, and this is what we need to diagnose the problem.
    2,015 pointsBadges:
    report
  • Davidwalter
    If the physical size of the Exchange Server database file exceeds the configured size, It displays a message "A database reached the maximum allowed size" during the Mounting process. Please go throught this helpful article, describing how to resolve this database oversize problem: http://www.repair-file.com/article-Exchange-Server-Database-Oversized.htm thanks
    75 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following