server 2003 exchange loosing sync

we have a server that is used for active directory and exchange that is having sync issues regularly.  We are running server 2003 for the OS and exchange server 2003 is installed on this server.  

Almost every day we are having to restart the exchange services in order for our clients to connect.

Errors we receive during this time:

Server activesync
event id: 3005
unexpected exchange mailbox server error: server: alpha.xxxxxxxxx.local
user: jdoe@xxxxxxxx.com HTTP status code: 503 Verify that the exchange mailbox server is working correctly

msexchangesa
event id: 9175
the mapi call 'openmsgstore' failed with the following error:  The attempt to log on to the Microsoft exchange server computer has failed.  The mapi provider failed
Microsoft exchange server information store
id no: 8004011d-0512-00000000

msexchangesa
event id: 1005
unexpected error <<0xc1050000 - The attempt to log on the the Microsoft exchange server computer has failed.  The mapi provider failed.  MIcrosoft exchange server information store ID no: 8004011d-0512-00000000>> occured

msexchangeis mailbox store
event id: 9689
exchange store 'first storage group\mailbox store alpha : The logical size of this database (the logical size equals the physical size of the .edb file and the .stm file minus the logical free space in each) is 50GB.  This database size has exceeded the size limit of 50 GB

If the logical size of this database is not reduced to less than the maximum size limit, this database will be dismounted the next time a database size check is performed

Please advise as the issue will not stop
johnpatbullockAsked:
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.

VirastaRUC Tech Consultant Commented:
Hi,

The main reason for the issue is the 'first storage group\mailbox store alpha reached its limit : 50 GB.

Follow the below steps in the URL and keep me posted.

Event ID: 9689
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=9689&EvtSrc=MSExchangeIS&LCID=1033
0

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
johnpatbullockAuthor Commented:
I actually did this right after i posted the question.  I increased the size form 50GB to 65GB

Thanks though cause it proved the move i made on that part was correct
0
VirastaRUC Tech Consultant Commented:
Hi, what other event you are currently getting now?

Did you restart the Microsoft System Attendant Service after you changed the value?

Actually this is for Exchange 2003:
Event ID: 9689
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.7638.0&EvtID=9689&EvtSrc=MSExchangeIS+Mailbox+Store&LCID=1033
0
VirastaRUC Tech Consultant Commented:
Hi,
I strongly recommend you to set the database to the 75GB ( if your Hard disk has enough room) now itself and keep an eye on database and logs.

Hope that helps :)
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
Internet / Email Software

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.