Exchange log on and transaction errors.

We are experiencing errors on our exchange server.

Note: there are many of the 1022 errors for various users throughout the organization.  The 9791 errors show up intermittently as do the 623 errors.  The errors began today around 2pm and are continuous until now (4pm).  Users are getting error messages in their mailboxes and Outlook client performance is very slow to unresponsive at times causing some to have to restart their Outlook application to full reboots of their desktops.

What might the issue be??



Event Type:      Error
Event Source:      ESE
Event Category:      Transaction Manager
Event ID:      623
Date:            4/5/2012
Time:            3:31:01 PM
User:            N/A
Computer:      <Server Name>
Description:
Information Store (4520) First Storage Group: The version store for this instance (0) has reached its maximum size of 155Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.
Possible long-running transaction:
      SessionId: 0xBD534080
      Session-context: 0x00000000
      Session-context ThreadId: 0x0000169C
      Cleanup: 1

For more information, click http://www.microsoft.com/contentredirect.asp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      MSExchangeIS Mailbox Store
Event Category:      Logons
Event ID:      1022
Date:            4/5/2012
Time:            3:31:08 PM
User:            N/A
Computer:      <Server Name>
Description:
Logon Failure on database "First Storage Group\Mailbox Store (<Server Name>)" - Windows 2000 account <account name> ; mailbox /o=< sanitized> ou=Administration/cn=Recipients/cn=< sanitized> .
Error: -1069

For more information, click http://www.microsoft.com/contentredirect.asp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      MSExchangeIS Mailbox Store
Event Category:      Logons
Event ID:      1022
Date:            4/5/2012
Time:            3:31:18 PM
User:            N/A
Computer:      < sanitized>
Description:
Logon Failure on database "First Storage Group\Mailbox Store (< sanitized> )" - Windows 2000 account < sanitized> ; mailbox /o=< sanitized> /ou=Administration/cn=Recipients/cn=< sanitized>
Error: -1069

For more information, click http://www.microsoft.com/contentredirect.asp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Warning
Event Source:      MSExchangeIS Mailbox Store
Event Category:      Background Cleanup
Event ID:      9791
Date:            4/5/2012
Time:            3:31:19 PM
User:            N/A
Computer:      < sanitized>
Description:
Cleanup of the DeliveredTo table for database 'First Storage Group\Mailbox Store (< sanitized> )' was pre-empted because the database engine's version store was growing too large. 0 entries were purged.

For more information, click http://www.microsoft.com/contentredirect.asp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Jim BarberTelecom/Network Systems ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
markgossettCommented:
right off hand it would appear since you've reached your DB max size that would be a place to start. If it can't write transaction logs and the like it would probably start throwing those errors. I would recommend cleaning up your DB and of course what R-R said above
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.