Exchange Server 2003 SP2

[Guest]

I have a problem with a customer who's database has twice dismounted due to the database exceeding 18+GB. This of course can be increased to 72GB+ with the addition of a registry key. I have added this key but the logs still show the same error when I start the Exchange Information Store.

Event Type: Information

Event Source: MSExchangeIS Public Store

Event Category: General

Event ID: 1216

Date: 09/01/2010

Time: 11:22:56

User: N/A

Computer: *********

Description:

The Exchange store 'First Storage Group\Public Folder Store (*********)' is limited to 18 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 18 GB, the database will be dismounted on a regular basis.

For more information, click http://www.microsoft.com/contentredirect.asp.

If I delete the key and re-add it then restart the services it then shows the correct 72GB in the event logs. Overtime though it will resort back to 18GB. Ideas? :(

[sc302 Veteran]

run esutil to repair and defrag the database.

http://www.msexchange.org/tutorials/Exchan...EG-ESEUTIL.html

[Guest]

The key problem to off-line defrags is they are off-line. From experience they also take a few hours to days.

[sc302 Veteran]

few hours for that small of a database. I did one recently to a completely screwed exchange server 49GB took 8 hrs, repair first then defrag, defrag is optional but I would recommend it.

Either that or build another exchange server on hardware that you may or may not have. As I told them, its either you live without exchange until the process is done or we continue to have errors and issues until you get new hardware to put a new install on, they decided on the cheap way.

Edited January 11, 2010 by sc302

[REM2000]

Had the same problem once with a client, i did warn them a month before hand that the server was getting full but they ignored me until the server crashed.

I had to defrag the database to get it to run again, make sure you have lots of free space, due to the server i had to perform the defrag to an external USB2 HDD as i couldn't get another IDE / SCSI connection, the server was physically full.

Once defraged depending on your version of exchange you should then be able to create another database and move some users to that.

As others have mentioned a hell of a lot of patience is required.

[Guest]

The issue isn't due to size since the registry key increases the allowed limit. Sadly the reg key seems to work selectively.