Comments on: Exchange 2003 IS unmounts database

By: davidwalter

davidwalter — Fri, 15 Jun 2012 03:30:09 +0000

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

By: stevesz

stevesz — Thu, 13 Jan 2011 16:38:01 +0000

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.

By: martinx

martinx — Thu, 13 Jan 2011 02:17:07 +0000

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.

By: rhrivera

rhrivera — Tue, 11 Jan 2011 22:57:44 +0000

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.