Exchange 2003 EDB corrupt

Status
Not open for further replies.

bertramtanner33

New Member
Outlook version
Outlook 2013 32 bit
Email Account
POP3
i have customer recently where their Exchange 2003 edb file get corrupted.

now we plan to re-create new EDB file to exchange and link back to users account.


is the step just need to create a new storage group, which will also will create new edb file..?

after i create new edb/mailbox store, how can i link back to my existing user account...?
 

Diane Poremsky

Senior Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
As long as you didn't touch the AD and only the database is corrupt, creating a new db and moving the mailboxes to it should work. (I think!)

Export mail from outlook to a pst before doing anything because the new database will be empty and it will cause outlook to empty the ost file. You'll need to import the pst into the new mailbox.
 

labeebshahidi

New Member
Outlook version
Outlook 2010 32 bit
Email Account
IMAP
But still, you don’t need to fright, since you can restore the damaged/corrupt Priv1.edb file with a manual method [ link removed ]


1. First of all you need to initiate the Exchange information store and then write down all of the errors.


2. Now halt Exchange information store and then from the ‘Bin’ folder, run the commands given below:


C:\exchsrvr\bin>eseutil /mh ..\mdbdata\priv1.edb"


3. You need to now authenticate the ‘State’ line in the output. Also, make sure that all the files are steady. In case, you discover any of the files incompatible, carry out a soft recovery process. And, to execute such recovery process, you just need to move to the folder where the log files along with the database are placed. After performing this, just make sure to run the subsequent at the command prompt:


C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /r E00


4. Once again, it is vital for you to make sure the steadiness of both the public and private information store.


5. If the files are steady, then skip the next step.


If the databases are found to be inconsistent, then it is significant for you to carry out a hard repair. To perform this, run the commands given below:


C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /p priv1.edb


6. From Mbdata folder, eliminate the log files now which is very crucial.


7. Eliminate the 'Temp.edb' file. and '.chk' file.

8. You need to now mount the databases and then, dismount them immediately.


9. At last, you need to discontinue the ESS(Exchange information store ) and then you should defragment both private and public store DBs. To do the same, run the following commands:


For Pub.edb:
C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\pub1.edb

For Priv.edb:
C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\priv1.edb



10. Now, run the 'Isinteg.exe' utility just to make sure that each database is steady.


C:\Program Files\exchsrvr\BIN>isinteg -s (servername) -fix -test alltests


11. Lastly, restart the Exchange information store to recover the corrupt PRIV, PRIV1, Pub, and Pub1 Exchange Database Files.
 

sageflynn

New Member
Outlook version
Outlook 2013 32 bit
Email Account
[link to spam deleted]
 
Last edited by a moderator:

Diane Poremsky

Senior Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
Please stop posting links on other sites are full of links to spammy software sites. Those links will be removed. If you can't post helpful information, then please don't post anything at all. I don't want to lock this thread but will if the spamming does not stop.
 

dimitrigigot

New Member
Outlook version
Older version
Email Account
POP3
As I know the same issue was resolved about a year ago over there [link to spam on TechNet removed]
 
Last edited by a moderator:

Diane Poremsky

Senior Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
Not, it wasn't solved. That thread attracted spammers posting their commercial solutions - and there is a good chance it was a thread planted by the spammer whose reply was marked the answer.
 
Status
Not open for further replies.
Top