SBS 2003 Exchange Data Base Damaged

A power surge toasted my Exchange Private and Public Stores.    I have been receiving Event ID Codes:

516 - Information Store (1236) First Storage Group: Database D:\Program Files1\Exchsrvr\mdbdata\priv1.edb: Page 3501093 (0x00356c25) failed verification due to a timestamp mismatch.  The expected timestamp was 0x19890d82 but the actual timestamp on the page was 0x1988ebad.  Recovery/restore will fail with error -566.  If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem.

9518 - Error 0xfffffdca starting Storage Group /DC=local/DC=AEI/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=AEI/CN=Administrative Groups/CN=first administrative group/CN=Servers/CN=AEISERVER/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.

454 - Information Store (1236) First Storage Group: Database recovery/restore failed with unexpected error -566.

I made backups of the .edb and .stm files and tried to run eseutil /p.  I also ran eseutil /d on both stores.   They completed successfully but I was getting a new error code:

494 - Information Store (9196) First Storage Group: Database recovery failed with error -1216 because it encountered references to a database, 'D:\Program Files1\Exchsrvr\mdbdata\priv1.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message.


In the interest of getting the users up, figuring I can restore later I renamed the private store files by adding .old to their file names as in this article   http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=48

I expected that not finding the original store would cause Exchange to create new stores.  Instead I keep getting messages like the one above.

1.  How can I get Exchange running with a new store so my users can send and receive email?
2.  How can I repair the existing stores and ultimately merge the two together?

Right now I'd settle for an answer to 1.

It takes hours to copy the files through the system  I'd rather work on the restore out of hours.

Thanks.
DocBrown88Asked:
Who is Participating?
 
WORKS2011Austin Tech CompanyCommented:
I believe with SBS2003 all you need to do is create a new store location, in the example I created the following:
- Transaction Log Location: D:\MDBDATA
- System Path Location: D:\MDBDATA
- Log File Prefix: E00

Make sure to dismount the store first, when you mount it will create a new database.edb file and logs.

Make sure you have enough free space.

database info
0
 
Simon Butler (Sembee)ConsultantCommented:
Empty database route is known as the dial tone restore method.
https://technet.microsoft.com/en-us/library/aa998947(v=exchg.65).aspx

However I suspect you may have more significant damage within the OS, the timestamp errors are more of a concern. Do you have another domain controller in the environment? If this wasn't something so old I would tell you to call Microsoft, but Exchange 2003 has been out of all support options for some time now.

Simon.
0
 
WORKS2011Austin Tech CompanyCommented:
I've come across some badly damaged exchange databases over the years and early on I would troubleshoot to get the store up and running without time in mind. Now when I come across a damaged store that likely won't be recovered from a backup or running simple eseutil commands I create a new store, confirm stability, and use a recovery tool for the sake of saving time.

There are plenty of edb recovery tools that pay for themselves easily with the time saved, one I use is http://www.systoolsgroup.com/exchange-recovery.html 

Please confirm if you have an empty store up and running, if you do above would be my approach. If you don't have a store up and running let me know and I'll walk you through it.
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

 
DocBrown88Author Commented:
I have not been able to get an empty store up and running even though I renamed the  files.      I would appreciate your guidance on that.   Right now I have them up on another Exchange server but I would like to restore this one to functionality. So far I haven't been able to create a new store.
0
 
DocBrown88Author Commented:
Simon, I did have more damage originally. IIS administration wouldn't come up.   I was able to restore it from the system back ups only to find exchange complaining of the timestamp issue. So far everything else seems to be functioning fine
0
 
WORKS2011Austin Tech CompanyCommented:
Don't worry about circular logging, I have it checked because I image the server and recover exchange via backup software.
0
 
DocBrown88Author Commented:
WORKS2011, I've tried this and I get a 494,454, 9518 series of errors.  The 494 seems to be the worst:

Information Store (5332) First Storage Group: Database recovery failed with error -1216 because it encountered references to a database, 'D:\Program Files1\Exchsrvr\mdbdata\priv1.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message


I even went and pointed the mailbox store and public folder store to MDBDATA too.   I'm not sure what I'm doing that's causing the 494.
0
 
WORKS2011Austin Tech CompanyCommented:
I'll look into it further. If this is for a client it would be a great time to discuss updating from 2003?
0
 
DocBrown88Author Commented:
Thanks.  I agree, but I want to recoverthe public folder information.
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.

All Courses

From novice to tech pro — start learning today.