Hello Friends, I have a serious problem, I have a Database of company I work about 74 GB of data. In the middle of month of May, there was a power outage, and returned with the Exchange Database Corrupted. I can extract the PST by software others, however, is missing many emails. I did the procedure repair by ESEUTIL complete, but to no avail, the error is constant Log corrupted when assembling the base. I'll post the log that shows the where this problem, many thanks for the kindness of friends who can help me PS: I do not have the logs described in the last line below is List is huge, I'm posting only the last lines. Thanks!! Lucas
LOG ##################
Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E0000030328.log - OK Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E0000030329.log - OK Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E000003032A.log - OK Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E000003032B.log - OK Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E000003032C.log - OK Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E000003032D.log - OK Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E000003032E.log - OK Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E000003032F.log - OK Missing log file: E0000030330.log Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E0000030331.log ERROR: Log damaged (unusable). Last Lgpos: (0x30331, 8.0). Error -501. Log file: C: \ Mailbox Database 1981968534 - C ¾ pia \ E00.log ERROR: Missing log file (s). Log file generation is 197424 (0x30330), but expected generation is 197426 (0x30332).
Operation terminated with error -528 (JET_errMissingLogFile, Current log file missing) after 1789.94 seconds.
Hello, I have changed the server, this problem happened just after the power in the company, and the server restarted ... I do not know what else to do. there is some method to mount this log is missing? just to mount the database? Thanks, Lucas- Brazil
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Do you have another replica in a DAG? If you do it's easiest to just stop replication, delete everything in there and then reseed.
If you don't have a copy you are going to have to accept data loss. This: http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/ is a good article to teach you how to bring your Exchange back up and running up to a point in time. The log file you posted contains the failed log point so you know how far you can get to.
Review the article and then make a fresh question here if you need assistance on a particular point.
Hello Mark my friend, had already followed this procedure, the problem is that the Database is Clean Shutdown, precisely because of the logs corrupteds. Still, the database will not mount. Meanwhile I am trying in many ways! I really appreciate your attention to me. Regards, Lucas
Mark, if I try to mount the Base Clean Shutdown mode, without the log files, this error appears when installing the file. EDB. Take a look
-------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- Failed to mount database 'Mailbox Database 1226870436'.
Mailbox Database 1226870436 Falha Erro: Unable to mount the specified database. Specified database: Mailbox Database 1226870436; Code Error: Operation failed Active Manager. Error: Action failed database. Error: The operation failed with the message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=1276) . [Database: Mailbox Database 1226870436, Server: msgsrv.grafica.local].
-------------------------------------------------------- OK --------------------------------------------------------
I read the tutorial link given by Mark in the reply. Shadow, the guidelines are perfect. Try to redo all the things what you did and get back the data and reply. I guess it will work. Also, you may contact Microsoft if they can help you out.
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Many people have followed the guidelines you were given.
The best thing for you would be to open a case with Microsoft. Either that or go and buy Kroll PowerControls to crack open the store and recover what you can.
I assume you started the users off with a dial-tone store and are merely trying to get their old email back, right?
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Excellent news.One word of warning though. If you do have any replica's there you will need to reseed them. The eseutil /d breaks the replica's. If you haven't got any replica's or only set up DAG replication after the /d then ignore, you're good to go.
error: Failed to connect to destination server "MSGSRV." Error: WMI Exception on server 'msgsrv.grafica.local': Call canceled
Attempting to use the command from the Exchange Management Shell: mailboxdatabase-new-Server 'MSGSRV'-Name 'recovery'-EdbFilePath 'D: \ Program Files \ Microsoft \ Exchange Server \ V14 \ Mailbox \ Mailbox Database 1981968534 \ Mailbox Database 1981968534.edb'-LogFolderPath 'D: \ WINDOWS Software \ Microsoft \ Exchange Server \ V14 \ Mailbox \ Mailbox Database 1981968534 '
1. Look folder c:\\Program Files\Exchsrvr\MDBDATA 2. Copy last E000xxx.log, E00.log and E00.chk to other place 3. Delete E00.log 4. Rename last E000xxx.log to E00.log 5. Execute c:\\Program Files\Exchsrvr\MDBDATA>"c:\\Program Files\Exchsrvr\bin\Eseutil" /r e00 5. You may need this procedures with following order: c:\\Program Files\Exchsrvr\MDBDATA>"c:\\Program Files\Exchsrvr\bin\Eseutil" /g
If above solution fails to solve the issue, you may use a third party Exchange server recovery software to repair and recover Exchange database. Such applications use advance scanning technique to repair the corrupted or damaged database files. One of the most globally used tool is mentioned here: http://www.recover-computerdata.com/exchange-server-recovery.html
After recovering the database with this tool, you can easily mount it on the Server. this tool is compatible with all versions of MS Exchange Server i.e. 2010, 2007, 2003, 2000, and 5.5.