[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2066
  • Last Modified:

Recalculate Logical Space - Exchange 2003

At regular intervals I am getting this error message in the EventLog:

"Exchange store 'First Storage Group\Mailbox Store (XXXXXX-XXXX)': The current physical size of this database (the .edb file and the .stm file) is 100 GB. This database has exceeded the size limit of 75 GB. However, the logical free space in this database has not yet been evaluated. Therefore, it is possible that this database contains enough free space to bring its logical size below the maximum size limit.

If the logical database size exceeds the maximum size limit, it will be dismounted on a regular basis."

I think the size of the edb and stm files are actually larger than they need to be, but I am unable to find any good resources that explain how I could recalculate the logical space.

Any suggestions would be greatly appriciated!
0
AskCentric
Asked:
AskCentric
  • 2
  • 2
2 Solutions
 
RudramCommented:
* Hopefully the below link might be useful

http://support.microsoft.com/kb/192185

Good Luck (^_^)
0
 
RudramCommented:
* Heres a more detailed explanation:

http://technet.microsoft.com/en-us/library/aa996139(EXCHG.65).aspx

(^_^)
0
 
pradeepg1971Commented:
Solved this problem with the following solution.
http://support.microsoft.com/kb/912375
*****************
How to increase the Exchange Server 2003 Service Pack 2 18-gigabyte database size limit
View products that this article applies to.
Article ID
:      912375
Last Review      :      November 27, 2007
Revision      :      5.4
INTRODUCTION
New functionality has been included with Microsoft Exchange Server 2003 Service Pack 2 (SP2). You can now configure database size limits.

The database size limits for Microsoft Exchange Server 2003 Standard Edition have been increased from 16 GB to 18 GB. The limit can be increased to as much as 75 GB by using a registry key.

Microsoft Exchange Server 2003 Enterprise Edition does not have a maximum database size limit.

For more information about how to set the database size limit, see the Exchange Server 2003 Help topic. The Help topic was updated during the installation of Exchange Server 2003 SP2.
MORE INFORMATION
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows


To increase the Exchange Server 2003 SP2 database size, follow these steps.

Important Before you increase the maximum size of an Exchange database, verify that sufficient hard disk space is available for the larger database.
1.      On the computer that is running Exchange 2003 SP2, click Start, click Run, type regedit, and then click OK.
2.      Click one of the following registry subkeys, as appropriate for the store that you want to increase:
"      For a mailbox store, click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Private-Mailbox Store GUID
"      For a public folder store, click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Public-Public Store GUID

3.      On the Edit menu, point to New, and then click DWORD Value.
4.      In the New Value #1 box, type Database Size Limit in Gb, and then press ENTER.
5.      Right-click Database Size Limit in Gb, and then click Modify.
6.      Click Decimal, and then type an integer from 1 to 75 in the Value data box.

Note These integer values represent the maximum size of the database in gigabytes (GB). For example, a value of 75 represents a database that has a maximum size of 75 GB.
7.      Click OK, and then exit Registry Editor.
8.      Restart the Microsoft Exchange Information Store service. To do this, follow these steps:
a.       Click Start, click Run, type cmd, and then click OK.
b.       At the command prompt, type the following command, and then press ENTER:
net stop msexchangeis
c.       After the Microsoft Exchange Information Store service has stopped successfully, type the following command, and then press ENTER:
net start msexchangeis

9.      Examine the Application log to verify that the database size has been set successfully. To do this, follow these steps:
a.       Click Start, click Run, type eventvwr, and then click OK.
b.       In the Event Viewer tool, click Application.
c.       Double-click event ID 1216 to verify that the database size has been set successfully.

For more information about how to configure the new database size limit when you use Exchange Server 2003 SP2, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/aa998066.aspx
For more information about how to temporarily increase the database size in Exchange Server 2003 Service Pack 1 or an earlier version of Exchange Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
828070 Exchange Server Mailbox Store does not mount when the Mailbox Store database reaches the 16-GB limit
For more information about how to temporarily increase the database size in Exchange 2000 Server, click the following article number to view the article in the Microsoft Knowledge Base:
813051 How to temporarily increase the Exchange 2000 16-gigabyte database size limit


0
 
pradeepg1971Commented:
please update and close this.
thanks
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

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