The information in this article applies to:
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).
CAUSEUsually this problem is caused by looping Inbox Assistant or Public Folder 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.
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.
edbutil /d /ispub Q217139 XADM: Meeting Requests Are Not Delivered if Recipient's Mailbox Has Exceeded the Storage Limit and Has a Delegate DefinedHowever, 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 RulesIf 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. 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. Additional query words: tshoot
Keywords : XADM exc4 exc5 exc55 |
Last Reviewed: November 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |