Exchange 2k3 freezes when users search contacts in outlook 2k10

Hello everybody,
We have an exchange server 2k3  on windows 2k3 sp2, latelatly we upgrade the email client outlook from 2k3 to the latest 2k10. We notice now that everytime a user does a search in his outlook's contatcts the server crasches with the following error messages in the event logs:
Event Type:      Error
Event Source:      MSExchangeIS Mailbox Store
Event Category:      Logons
Event ID:      1022
Date:            11/10/2010
Time:            6:28:11 PM
User:            N/A
Computer:      TISNA-EXBE01
Description:
Logon Failure on database "VIPS Storage Group\VIPS MAIL" - Windows 2000 account TELE*******\robert; mailbox /o=tele******/ou=First Administrative Group/cn=Recipients/cn=r.mi****.
Error: -1069

For more information, click http://www.microsoft.com/contentredirect.asp.
The server is fully updated.....
User's mail box is about 8 Giga (storage group too big??) but we never had this problem before with outlook 2k3.
Please, help!!
ggmisadminAsked:
Who is Participating?
 
lucid8Commented:
  1. If you want to PROVE its Outlook 2010 doing this, Log the user onto a box with Outlook 2003 and have them take the same action and see what happens
  2. Sounds to me like you are stumbling across some mailbox corruption
    • I would start by running ISINTEG - FIX Alltests against the database to ensure that it is error free.  
  3. As an alternative you could also move the mailbox for the user in question to another store to see if that would help.
Troy Werelius
Lucid8.com
0
 
ggmisadminAuthor Commented:
Thnak you for your response....
I notices actually a error in the log before that one I listed , saying:
Event Type:      Error
Event Source:      ESE
Event Category:      Transaction Manager
Event ID:      623
Date:            11/10/2010
Time:            6:23:57 PM
User:            N/A
Computer:      TISNA-EXBE01
Description:
Information Store (540) VIPS Storage Group: The version store for this instance (1) has reached its maximum size of 108Mb. 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: 0xBD532FA0
      Session-context: 0x00000000
      Session-context ThreadId: 0x00001AA8
      Cleanup: 1

Now, althought we did some archive and reduced the size of storage, we still have the problem that we never had with office 2k3 and a bigger storage group.
Thank you!!!
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
lucid8Commented:
So am I correct that I gave you the correct answer but since you decided to confirm by contacting MS you want to close this without crediting me for the answer?
0
 
ggmisadminAuthor Commented:
ops...sorry i thought i did give you the credits...
0
 
ggmisadminAuthor Commented:
made wrong selection. I meant to assign points
0
 
lucid8Commented:
thanks for the update
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.