Exchange2007: Corrupt Message detected
Corrupt Message detected.
Fid = 1-44DE34022 ; Mid = 1-8DAB83E4DA ;
Some or all properties of this message will not be transferred correctly.
Source: MSExchangeIS Mailbox Store
EventID: 9774
I have those errors Since one of disc In my server was crash down. On this disc was Active Directory settings and Exchange 2007 files 1st storage & 2nd storage.
I bought New disc and restore 2backups from my backup server:
1) FULL Backup was from 15 october,
2) Second backup for Only 1st storage & 2nd storage was from 5 November.
After 15 October I was create 1 user in AD & Exchange. He have >50 emails. After restore backup his email-box is empty.
Anny suggestions what is wrong now? How to find message: Fid = 1-44DE34022 ; Mid = 1-8DAB83E4DA ;
Please HELP.
November 12th, 2009 11:35am
I guess you can run isinteg on database in order to get rid of these logical errors. Eseutil/Isinteg - Email Store Troubleshooting http://www.exchangeinbox.com/article.aspx?i=87Vinod
|CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
Free Windows Admin Tool Kit Click here and download it now
November 12th, 2009 11:41am
Thanks for Your quick answer.I'ill try to use isinteg, and write errors [if any be].
November 12th, 2009 2:05pm
Hi,This error indicates database have some corruption, please Run offline defragmentation (eseutil /D) and IsInteg (isinteg -s <servername> -fix -test alltests until no fixes are observed in the output) on the Mailbox Store
Eseutil /D Defragmentation Modehttp://technet.microsoft.com/en-us/library/aa997972.aspx
Isinteghttp://technet.microsoft.com/en-us/library/bb125144.aspx Regards,Xiu
Free Windows Admin Tool Kit Click here and download it now
November 13th, 2009 9:19am
I came across the same issue. IsInteg should only be used if there are many MBX with errors on a particular DB. Else, move the MBX to a different DB ( you may move it back if u want ). This will solve the problem. How to make sure which mailbox to move!! well run PFDAVADMIN on the DB (if u have multiple DB run on all), select the output in a txt file, copy the Mailbox ID (MID) from the error message, do a Ctrl+F in the text file to search for the MID and you will come to know which is the culprit MBX. Move it and it will solve the issue. Enjoy!!! :)
November 21st, 2009 12:54am