• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 177
  • Last Modified:

after recovering from a full drive, exchange 2000 continues to give c1041724 when trying to mount the mailbox stores.

On a Windows 2000 server running Microsoft Exchange 2000.  The public and private Mailbox stores won't mount.  This was initially caused by a full  hard drive, however even after freeing up plenty of space, the mailbox stores refuse to mount.  

No relevant errors are logged to the application or server event logs.  

When I try to mount the stores from the exchange system manager I get the well documented c1041724 error.  I have gone through all the troubleshooting documents related to this error with no success.  

I did discover that somehow the security settings for the mailbox stores weren't correct.  As noted in http://support.microsoft.com/?kbid=827283 the exchange domain servers group did not have full control of the mailbox stores.  I corrected this problem but there was no change to the larger symptoms.

I checked the states of both stores and found them to be in "clean shutdown" state.

My only thought is that this is the first time we've had to restart the exchange server since the DST updates were done before the actual DST switch.  Could something have gone haywire after the 11th of march?
0
NWHS
Asked:
NWHS
  • 3
  • 2
1 Solution
 
MATTHEW_LCommented:
Have you tried running eseutil on a copy of your mailbox store?  
0
 
NWHSAuthor Commented:
Yes, I ran eseutil /mh to check the state of the stores.  Both were in "clean shutdown" state.  I also ran eseutil /g on the public store (smaller of the two) and it came back as having good integrity.  I also ran eseutil /d on both just to try and clean things up a bit.  None of these had an effect on the problem.  It would seem that the mailbox stores them selves are fine.  Something else is the problem.

I did notice something a little odd while going through the security settings in exchange.  There was an unresolveable account listed as having rights to the mailbox store.  By unresolveable I mean that the account displayed as a numerical ID instead of an account name.  The account had almost no permissions so its probably not a big deal but it seems odd that it would be there.  Regardless, I suspect this is just a red herring.
0
 
NWHSAuthor Commented:
Looks like this is my own stupid fault.  The E00.log file got deleted accidentally during the process of cleaning up the unneeded transaction log files.  I was able to use eseutil /p to make the database mountable again.  all is happy with the world again.

Thanks anyway ExEx.

-Alex
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
MATTHEW_LCommented:
So eseutil fixed it up for you?
0
 
NWHSAuthor Commented:
No, actually I found the solution on goatse.cx  As I said before, I already knew about eseutil when I started.  Nice try though.

-Lex
0
 
Computer101Commented:
PAQed with points refunded (250)

Computer101
EE Admin
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.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now