Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 847
  • Last Modified:

Exchange 2003 is dismounting daily

Every morning @ 5:00 am Central, our exchange dismounts. Recently we installed BBPro software but were not satisfied with the software. Therefore we removed it and coincedentally these errors have occured daily, causing a reboot of the server in order to reestablish our email. Here are the errors in the event viewer on the server:

The MAPI call 'OpenMsgStore' failed with the following error:
The attempt to log on to the Microsoft Exchange Server computer has failed.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0512-00000000

Exchange store 'First Storage Group\Mailbox Store (SERVER NAME)': The logical size of this database (the logical size equals the physical size of the .edb file and the .stm file minus the logical free space in each) is 25 GB. This database size has exceeded the size limit of 25 GB.
This database will be dismounted immediately.

Unexpected Exchange mailbox Server error: Server: User: HTTP status code: [503]. Verify that the Exchange mailbox Server is working correctly.

LDAP Bind was unsuccessful on directory for distinguished name ''. Directory returned error:[0x34] Unavailable.    

Error 0x7da occurred while rendering message 0001-00000036f638 for download for user  

This is an SMTP protocol warning log for virtual server ID 1, connection #29. The remote host "", responded to the SMTP command "rcpt" with "450 4.7.1 <aerialvideo@excite.com>: Recipient address rejected: Greylisting in use, please try again in 60 seconds.  ". The full command sent was "RCPT TO:<aerialvideo@excite.com>  ".  This may cause the connection to fail.
4 Solutions
assuming you're running exchange 2003 standard, make sure you are running sp2.

Change the maximum size to 75GB:

Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
Everyday around that time, Exchange runs online maintainence and calculates your white space, event id 1221.

The error says that you have a limit of 25gb and you have exceeded that. Once exchange finds out that the database size is over the limit configured, it dismounts it. It is by design.

As your is Exchange 2003, you can increase your limit to 75gb with a registry edit.

 * HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Servername>\Private-GUID

Do the same for public folder db as well.


Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
We are running a Standard verion of Exchange and with SP1 it had a limit of 16Gb and with SP2 it was raised to 18Gb. So your server has SP2 but not the Registry key
HKLM\System\Current ControlSet\Services\MSExchangeIS\<Server name>\PRIVATE-GUID of the Store
We have to create a
DWORD name: "Database Size Limit in Gb" (this is case sensitive).
DWORD value: xx (This would be the physical limit that you want to set for the size of the store).
We now would have to restart the Information Store service.

Comming to the point of it getting dismounted every morning is that, every morning the Online Maintance is run it one of its 10 tasks is to check wiith the size of the store and if it finds its value as higher then the permisible limit it would dismount the stores.
You can also try to find the free space in the database and run the Offline Defrag and isinteg commands over the database on the weekend. This would get you the Exact size of the DB. To check the free space you can verify with 1221 event id for the specific store.
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:

If the issue is resolved can close the issue and distribute the points...... :-)

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now