Also unable to mount store   

Similar to Lekan's problem, we had our exchange all of a sudden freeze on 
us.  On reboot, the store would not mount and gave the error, "An internal 
processing error has occurred.  Try restarting the Exchange System Manager 
or the Microsoft Exchange Information Store service, or both.  ID no: 
c1041724"  I did both, no luck.  I ran the Eseutil in D/R/MH/G and all come 
up clean and defragmented.  All services startup with no issues, but cannot 
mount the store.  Directory permissions are correct.  There is one log file, 
E00.log in the directory and probably that is the issue we are running into. 
Additionally we are getting this error - Initialization of Jet Failed.  The 
KB articles regarding this on MS are not available (9518 errors) and I am 
stuck.  The system is looking for a E00002F0.log file, but there is no such 
file.

Help me Obi Wan! Your my only hope!

Paul Clemmons, VP, PC Networks

date: Tue, 27 Feb 2007 07:30:08 -0800   author:   Paul Clemmons

Re: Also unable to mount store   

Hi,

Hopefully you have the store mounted by now.
Did you move all the log files to another location after you ran all the 
eseutil commands and before you tried to mount the store again?

Leif

"Paul Clemmons"  wrote in message 
news:uJPppQoWHHA.4240@TK2MSFTNGP06.phx.gbl...
> Similar to Lekan's problem, we had our exchange all of a sudden freeze on 
> us.  On reboot, the store would not mount and gave the error, "An internal 
> processing error has occurred.  Try restarting the Exchange System Manager 
> or the Microsoft Exchange Information Store service, or both.  ID no: 
> c1041724"  I did both, no luck.  I ran the Eseutil in D/R/MH/G and all 
> come up clean and defragmented.  All services startup with no issues, but 
> cannot mount the store.  Directory permissions are correct.  There is one 
> log file, E00.log in the directory and probably that is the issue we are 
> running into. Additionally we are getting this error - Initialization of 
> Jet Failed.  The KB articles regarding this on MS are not available (9518 
> errors) and I am stuck.  The system is looking for a E00002F0.log file, 
> but there is no such file.
>
> Help me Obi Wan! Your my only hope!
>
> Paul Clemmons, VP, PC Networks
>

date: Fri, 2 Mar 2007 18:21:48 +0100   author:   Leif Pedersen [MVP]