exchange 2003 event 9791 and 1022 - intermittent issues

Hi Gurus,

I've been experiencing this intermittent issue that occurs every so often, say once a few months...Yesterday and today, it has occurred a total of 4 times.

During the occurrence, Exchange logs 4x Event 9791 which each pertain to one of my four exchange datastores:

Event Type:      Warning
Event Source:      MSExchangeIS Mailbox Store
Event Category:      Background Cleanup
Event ID:      9791
Date:            9/23/2010
Time:            8:03:13 AM
User:            N/A
Computer:      EXCHANGE
Description:
Cleanup of the DeliveredTo table for database 'First Storage Group\General Users' was pre-empted because the database engine's version store was growing too large. 0 entries were purged.


Then it's followed by a few Event 1022:

Event Type:      Error
Event Source:      MSExchangeIS Mailbox Store
Event Category:      Logons
Event ID:      1022
Date:            9/22/2010
Time:            4:31:10 PM
User:            N/A
Computer:      EXCHANGE
Description:
Logon Failure on database "First Storage Group\Super Users" - Windows 2000 account STARPOINT\jodyp; mailbox /o=Starpoint/ou=First Administrative Group/cn=Recipients/cn=JodyP.
Error: -1069

After which, random users get outlook issues where they can't send/receive...Outlook gives "Operation failed" errors and when closing outlook and restarting the application, Outlook can't open mailbox...After about 5-10 mins, everything is fine again.

I have 1x Exchange 2003 w/ SP2 in a windows 2003/2008 running in win2003 forest/domain level.

I've researched every where and can't find much info on Event 9791 (i already installed hotfix 919417 awhile ago) nor Event 1022 with Error: -1069.


LVL 1
jetli87Asked:
Who is Participating?
 
jetli87Connect With a Mentor Author Commented:
probelm fixed itself.
0
 
dan_blagutCommented:
Hello

Your store is maybe too large. The limit is usually set to 18Gb.
Here you can find the info:
http://technet.microsoft.com/en-us/library/aa998066(EXCHG.65).aspx

Dan
0
 
jetli87Author Commented:
well the we were on Standard and I upgraded to Enterprise about 2 years back, thus size limit shouldn't be an issue correct?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
dan_blagutCommented:
can you look the registry key value?
0
 
jetli87Author Commented:
ok I just did...all objects, but one had the DB Size limit entry which i then changed the value from 48 to 8000...Though the others had no DB size limit entry.

Note:  I took over this exchange/Network over from a previous Admin so I'm no exactly 100% aware of any previous configs.

Should I add the entry and set it to 8000?

I should also mention i had to create a remount task to run every morning @ 5:30am since one main store (the original first mailbox store) is about 180GBs and was dismounting every morning around 5am...I alway found it odd that I'm on enterprise edition and it would still do that, but I assumed it was an issue from ugprading Standard to Enterprise.
0
 
dan_blagutCommented:
I think so.
An will see if the database will be dismounted.

Dan
0
 
jetli87Author Commented:
Well should I add the reg entry for the stores that have no size limit entry?

Essentially, the above error messages affects all stores.
0
 
dan_blagutCommented:
All store has it own setting:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<SERVER NAME>\<store name pseudonim>

Dan  
0
 
jetli87Author Commented:
no solution provided...Problem fixed itself.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.