Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.
Exchange 2003 Standard edition - recreating mailbox store
Good morning.
I have an issue with an Exchange 2003 Standard server running on Windows 2003 SP1.
Background: A client contacted me with information that his server had died. He had lost multiple drives from his RAID array and the server was experiencing power cutouts. After investigating, we found issues with the hardware in the box that required a full rebuild of the server. We reinstalled using the /disasterrecovery switch and went to install from the last backup. (this is the point where it goes off the rails) Unfortunately, the full backup had been done incorrectly using NTBackup. The administrator for the server had simply selected the folders that the database and transaction log files reside in instead of backing up the information store correctly. This resulted in:
1. .edb files and .stm files that were in an inconsistent state - "Dirty Shutdown"
2. a lack of a restore.env file.
After running eseutil /r and having it fail, we were forced to run eseutil /p against the database. The resulting database was not what we hoped. Luckily, we have been able to export every users data from the edb file to pst files with the intention of creating a new mailbox store, new mailboxes, and then importing the data from the pst files.
Here's my issue. Due to the fact that it is standard edition, we're limited to 1 Mailbox store. We deleted the original store and created a new one; but are unable to get it to mount -- in ESM, we get "An internal processing error has occurred..." ID c1041724
In the Event logs, we get:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9546
Date: 5/17/2000
Time: 5:53:44 PM
User: N/A
Computer: ComputerName
Description:
Failed to create the Event Registration Mailbox for Database First Storage Group\Mailbox Store (xxxxxx). Error - 0xbf69.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Date: 5/17/2000
Time: 5:53:44 PM
User: N/A
Computer: ComputerName
Description:
Error 0x80004005 starting database "First Storage Group\Mailbox Store (E2K-MSG1)" on the Microsoft Exchange Information Store.
I have reviewed kb articles that appear to be related with no luck. http://support.microsoft.com/kb/271339/EN-US/
What I need to do is get a new mailbox store mounted on this server so that I can recreate mailboxes for the users and then import their pst files. Any help would be appreciated.
I have an issue with an Exchange 2003 Standard server running on Windows 2003 SP1.
Background: A client contacted me with information that his server had died. He had lost multiple drives from his RAID array and the server was experiencing power cutouts. After investigating, we found issues with the hardware in the box that required a full rebuild of the server. We reinstalled using the /disasterrecovery switch and went to install from the last backup. (this is the point where it goes off the rails) Unfortunately, the full backup had been done incorrectly using NTBackup. The administrator for the server had simply selected the folders that the database and transaction log files reside in instead of backing up the information store correctly. This resulted in:
1. .edb files and .stm files that were in an inconsistent state - "Dirty Shutdown"
2. a lack of a restore.env file.
After running eseutil /r and having it fail, we were forced to run eseutil /p against the database. The resulting database was not what we hoped. Luckily, we have been able to export every users data from the edb file to pst files with the intention of creating a new mailbox store, new mailboxes, and then importing the data from the pst files.
Here's my issue. Due to the fact that it is standard edition, we're limited to 1 Mailbox store. We deleted the original store and created a new one; but are unable to get it to mount -- in ESM, we get "An internal processing error has occurred..." ID c1041724
In the Event logs, we get:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9546
Date: 5/17/2000
Time: 5:53:44 PM
User: N/A
Computer: ComputerName
Description:
Failed to create the Event Registration Mailbox for Database First Storage Group\Mailbox Store (xxxxxx). Error - 0xbf69.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Date: 5/17/2000
Time: 5:53:44 PM
User: N/A
Computer: ComputerName
Description:
Error 0x80004005 starting database "First Storage Group\Mailbox Store (E2K-MSG1)" on the Microsoft Exchange Information Store.
I have reviewed kb articles that appear to be related with no luck. http://support.microsoft.com/kb/271339/EN-US/
What I need to do is get a new mailbox store mounted on this server so that I can recreate mailboxes for the users and then import their pst files. Any help would be appreciated.
Asked:
-
2
-
2
1 Solution
Thanks for the response Simon.
I did try that; but no effect. The only other thing I could find was an article about the system mailbox needing to be deleted. I looked into that as well and was not able to get it working.
We're going to reinstall Exchange and go from there. Could it have been because the original reinstall was done with the /disasterrecovery switch?
I did try that; but no effect. The only other thing I could find was an article about the system mailbox needing to be deleted. I looked into that as well and was not able to get it working.
We're going to reinstall Exchange and go from there. Could it have been because the original reinstall was done with the /disasterrecovery switch?
The /disasterrecovery switch should only be used in very specific circumstances. Considering what you have wrote above, I don't think it was the right thing to do. You were not restoring a database, you are restoring the individual data. So a conventional reinstall followed by mail enabling the user accounts may well have been the best option.
It is difficult to say 100% on occasions like this, sometimes it comes down to instinct as to what is the best course of action.
Simon.
It is difficult to say 100% on occasions like this, sometimes it comes down to instinct as to what is the best course of action.
Simon.
Thanks for the response Simon. We ended up having to rebuild. It probably was the /disasterrecovery switch -- if the files had been properly backed up in the first place, that would have worked. Since they were not, we needed to rebuild from the ground up.
I'll award you the points for helping.
Thanks.
I'll award you the points for helping.
Thanks.
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 Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
I find it always pays to try the simple things first, then move on to the more complicated stuff later.
Simon.