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.
Thanks.
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.
Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
appears like log file sequence is at end. do you know how to reset the log file generation number\value?
ASKER
The issue has been resolved. I am just trying to find out how to avoid this in the future if anyone knows.
Thanks.
Thanks.
If you don't mind can you inform, How you resolved the issue? it will help others, if they face any issue like this.
ASKER
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
cheers
however, check the timings of the mailbox migrations, mailbox migration location free space, and backups runing at the time to narrow the issues.
cheers
Like s00007359 said, you've migrated to Exchange 2010, so dont worry about the log sequence. It's as simple as that.
ASKER
thanks everyone.
ASKER