XADM: Troubleshooting a Rapidly Growing Information Store This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
This article was previously published under Q170361 SYMPTOMS
This article describes the steps you can use to troubleshoot a rapidly
growing Exchange Server information store (the Priv.edb or Pub.edb files).
In certain cases, the information store can grow to from a few megabytes to several gigabytes in a 24-hour period. CAUSE
Usually, a looping Inbox Assistant or Public Folder causes this problem.
Assistant rules that cause a message to be continuously sent and received.
RESOLUTION
To avoid the problem, set mailbox size limits for all users on a server.
This prevents the information store from continuously growing.
Set the mailbox size limits in the Exchange Server Administrator program on the Advanced tab of the mailbox properties. MORE INFORMATION
Use the Exchange Server Administrator program to determine which mailbox
or public folder is causing the problem. To do this, view the
mailbox resources in the properties of the private information store or the
public folder resources in the properties of the public information store.
Look for mailboxes or public folders that have an unusually large number of
items or are using an unusually large amount of disk space.
After you determine which mailbox or public folder is causing the problem, log on to the Microsoft Exchange Client and disable any rules that reply or forward messages. Also delete items from the mailbox or public folder. Deleting messages in the mailbox or public folder does not automatically reduce the size of the Priv.edb or Pub.edb files. To recover the disk space, you must compact the Priv.edb or Pub.edb files; use the Edbutil.exe utility with the /d switch. Note that the Edbutil utility requires disk space in an amount equal to twice the size of the database that you want to process. Before you proceed, confirm that you have enough disk space available. To compact the database files, perform the following steps:
217139 (http://support.microsoft.com/kb/217139/EN-US/) XADM: Meeting Requests Are Not Delivered if Recipient's Mailbox Has Exceeded the Storage Limit and Has a Delegate Defined
However, you can create the following registry key to troubleshoot a rapidly growing information store on an Exchange Server 5.5 Service Pack 3 computer:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersPrivate Value Name: Apply Mailbox Quota to Rules
If this value is not 0, messages sent by rules still have the mailbox quota checked. If the value is not present or is 0 (the default in Service Pack 3), messages sent by rules ignore the mailbox quota for sending messages.Data Type: Reg_DWORD IMPORTANT: If you set mailbox quotas to rules, there may be side effects. For example, if you set a forward and delete rule, it may result in data loss, and if you set meeting requests to go only to the delegate, neither may receive the request if the mailbox is over the limit. APPLIES TO
| Article Translations
|


Back to the top
