Prev: Can SBS03/Exchange be setup with a Satelite ISP?
Next: Symantec Corporate Edition consistent errors
From: Tom Morris on 21 Mar 2007 23:28
Several times a day Event 9791 warnings appear n the Application log; usually
a mailbox expand 10 times their customary size. For example, one grew from
40,000KB to 1,500,000KB.

Recovering the space sometimes only requires opening the mailbox with
Outlook; often export/import of the mailbox. By the way, the ost files do not
reflect the same size increment.

All server rentention is turned off.

Anybody have any ideas what causes the error? And how to fix it?

Thanks,
Tom


----------------------

Event Type: Warning
Event Source: MSExchangeIS Mailbox Store
Event Category: Background Cleanup
Event ID: 9791
Date: 3/21/2007
Time: 11:47:24 AM
User: N/A
Computer: SERVER
Description:
Cleanup of the DeliveredTo table for database 'First Storage Group\Mailbox
Store (SERVER)' was pre-empted because the database engine's version store
was growing too large. 0 entries were purged.

From: "Jacky Luo [MSFT]" on 23 Mar 2007 08:21
Hi tom,

From the description, I understand the issue is that you get 9791 event id
error regarding exchange mailbox store. If I am off base, please don't
hesitate to let me know.

Let us refer to the following steps to troubleshoot the issue:

The error is warning message,It is related to performance issue on Exchange
Server.

1.restart microsoft exchange information store service.

2.dismount mailbox store and remount. to do so
a.go to exchange system manager
b.expand servers,first storage group,maibox store,right click and click
dismount store
c.then click mount store.

3.If issue persists,Please refer to the following steps to defragment
exchange database to see if it helps:

a. Check Database consistency using Eseutil utility:

Please run eseutil /mh on the database to check if the status of Exchange
databases is OK. You may refer to the following Knowledge Base Article:

How to defragment with the Eseutil utility (Eseutil.exe)

http://support.microsoft.com/default.aspx?scid=kb;en-us;192185

b. Run command to verify there is no error/warning. If there is warning
displayed, please repeat the Isinteg command until the number of database
fixes reaches 0 (zero) or does not change.

To do so, please follow the process below:

I. Dismount the Store by right-clicking it in ESM and choose Dismount Store.

II. Open a command prompt window and change the currently directory to
"<system drive>:\Program Files\Exchsrvr\Bin".

III. Run the following command:

isinteg -s <Exchange Server Name> -fix -test alltests

IV. Follow the instruction to scan the database.

V. Re-run the command in step IV until you found the fixes number is near
to 0 (zero).

For more information, please refer to the following Knowledge Base Article:

Exchange Command-Line Parameters for the Isinteg.exe Tool

http://support.microsoft.com/?id=301460

Please perform offline defragment on the exchange database. you can refer
to the article below:

328804 How to defragment Exchange databases

http://support.microsoft.com/?id=328804

Then please try to monitor the server for some time to check if the issue
persists.

4.restart the server

I appreciate your time. I am happy to be of assistance and look forward to
your reply.


Have a nice day!

Best regards,

Jacky Luo (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting

from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================

From: Eriq Neale [SBS-MVP] on 23 Mar 2007 08:23
Tom Morris wrote:
> Several times a day Event 9791 warnings appear n the Application log; usually
> a mailbox expand 10 times their customary size. For example, one grew from
> 40,000KB to 1,500,000KB.
>
> Recovering the space sometimes only requires opening the mailbox with
> Outlook; often export/import of the mailbox. By the way, the ost files do not
> reflect the same size increment.
>
> All server rentention is turned off.
>
> Anybody have any ideas what causes the error? And how to fix it?
>
> Thanks,
> Tom
>
>
> ----------------------
>
> Event Type: Warning
> Event Source: MSExchangeIS Mailbox Store
> Event Category: Background Cleanup
> Event ID: 9791
> Date: 3/21/2007
> Time: 11:47:24 AM
> User: N/A
> Computer: SERVER
> Description:
> Cleanup of the DeliveredTo table for database 'First Storage Group\Mailbox
> Store (SERVER)' was pre-empted because the database engine's version store
> was growing too large. 0 entries were purged.

A quick check of the error number at www.eventid.net pointed me to this
KB and a hotfix for the error:

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

HTH...

-Eriq

--
Eriq Neale - SBS MVP, Small Business Specialist, MCSE, Mac Guy
EON Consulting - www.eonconsulting.net
Author of Microsoft Small Business Server 2003 Unleashed
Listen to the eOnCall Radio broadcast at AIRTunZ
(www.airtunz.com) or hear past episodes at www.eoncall.com
 | 
Pages: 1
Prev: Can SBS03/Exchange be setup with a Satelite ISP?
Next: Symantec Corporate Edition consistent errors