Windows 10: Crash on a server Exchange 2003

Hi guys!
We had a crash on a server Exchange 2003. After that we made a copy of the mdbdata. Of course we reinstalled it. Now we're trying to mount the mailbox store (Priv1.edb 5 GB) but we receive this error:
The database files in this storage is inconsistent.
Next, following the MS article n. 327156 Eseutil.exe says that we have a "Dirty shutdown" database
"Eseutil /p" remains in "stand by" on "repair damaged database" step at 90% (the day after was still at 90%).

:)

 

I am not able to confihure my exchange server 2003 in my new WP 8,err code 85002028

Do you know if the server is up-to-date? Because Exchange 2003 is so old, it requires Exchange 2003 Service Pack 2 and all the Windows Updates released to date to support Windows Phone 8.

Or, is this actually an Exchange Server, or is it another kind of mail server that uses Exchange ActiveSync? Third-party mail servers that use EAS at the Exchange 2003 level (EAS v.2.5) have compatibility issues with modern mobiles.

 

Set up Mail for Exchange when Outlook connects using HTTP?

Mail for Exchange requires Exchange Server 2003 SP2 (at least) to be configured for "Exchange ActiveSync":

http://www.microsoft.com/technet/prodtechnol/exchange/2003/actsyncfaq.mspx

http://www.microsoft.com/exchange/evaluation/features/MobileAccessWP.mspx

Is that set up already for your server(s)?

 

Guys, I hope for your advice!

 

Have just spent most of this week getting our e2k server up and running again. What about backups? We spent 2 days running eseutil /p and isinteg - finally got the information stores mounted but found approx 50% of users had absolutely nothing in their accounts.

Then resorted to restoring from backup (we used MS backup)- was surprisingly straightforward and hassle free.

If you haven't backups and eseutil /p will not run you will need to try a eseutil /r to get the databases into a 'consistent' or clean shutdown state before it will let you run the /p option. Our database was 12Gb and the /p took 8 hours to run.

 

As a fallback you can try to use another tool like Exchange Server Recovery Toolbox for email recovery exchange server 2003. Here is the link to their website.
http://www.oemailrecovery.com/exchan..._recovery.html
After that you'll need to do an isinteg - but be aware there can be significant data loss.
Good luck.

 

You've been very kind in your efforts to help. Thanks for that. Solved!