Exchange 2003 store cannot be mounted.

We are in some 90% done to migrate all our users to Exchange 2010.  We still have one Exchange 2003 server on the network.  Last night, it has problem which the store cannot be mount and at the end, we had to follow kb830408 to reset the exchange log sequence to mount the store again.  

I just want to check if someone had experienced this kind of thing before, is there a way to avoid?  When this happened lastnight, all Exchange Services were up - include the IS service, server diskspace was good.  It was just the store could not be mounted.  

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

nav2567Author Commented:
Sorry, I forgot to mention, the problem happens on the exchange 2003 server.
while mounting the database, what is the error message appearing up?

You are not able to mount only one Database in exchange server 2003?

Is that database, recovered from backup? while mounting, can you check the event log and inform the event message.
nav2567Author Commented:
Event ID: 9518
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Description: Error 0xfffffddc starting Storage Group Path_of_Storage_Group on the Microsoft Exchange Information Store. Storage Group - Initialization of Jet failed.
SolarWinds® IP Control Bundle (IPCB)

Combines SolarWinds IP Address Manager and User Device Tracker to help detect IP conflicts, quickly identify affected systems, and help your team take near instantaneous action. Help improve visibility and enhance reliability with SolarWinds IP Control Bundle.

appears like log file sequence is at end. do you know how to reset the log file generation number\value?
nav2567Author Commented:
The issue has been resolved.  I am just trying to find out how to avoid this in the future if anyone knows.  

If you don't mind can you inform, How you resolved the issue? it will help others, if they face any issue like this.
nav2567Author Commented:
kb830408 - as mentioned in the beginning.
Performing a manual monitor or using any monitoring software will inform you, when the log generation number reaches the configured limit value.
Reseting the log sequence is the only option. We used to do it every 2 weeks for my previous client. Manual monitoring is another way. If you have so many logs generated, please make it a process to reset log file sequence every 2 weeks or 4 weekss.

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
Roshan MohammedCloud Engineering OfficerCommented:
Considering that you are migrating to 2010, from 2003. u don't need to worry about on how to avoid it in futuerl;

however, check the timings of the mailbox migrations, mailbox migration location free space, and backups runing at the time to narrow the issues.

Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
Like s00007359 said, you've migrated to Exchange 2010, so dont worry about the log sequence. It's as simple as that.
nav2567Author Commented:
thanks everyone.
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

From novice to tech pro — start learning today.