[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Eseutil /R  "timestamp in next log does not match expected"

Posted on 2004-11-24
7
Medium Priority
?
4,505 Views
Last Modified: 2008-05-23
I have had corrupt system and I am about to get it restored but I have been trying to run Eseutil /r on the PRIV DB, I get this error about the "timestamp in next log does not match expected" and I can't get around it.  I have the PUB recovered but the PRIV is still not mounting.

Please resond ASAP. I need to get this fixed in a day or two.

Thank you !!!
0
Comment
Question by:UMOS
  • 4
  • 3
7 Comments
 
LVL 7

Expert Comment

by:vasanthgnb
ID: 12672187
Hai,
  The error indicates that your one of your log file has got corrupted. It is ecommended to either restore from the latest backup or just run eseutil /p to repair the database and mount it. Run eseutil /p in the corrupted database. Then run eseutil /d to defragment it. Mount the database and dismount it imeediately. Then run isinteg - fix to fix all the logical errors in the database. But if you do this, possibilities of loosing some data is there. Because when you run eseutil /p it will delete the corrupted pages out of the database. Then when you run Isinteg, it will remove the logical pointers to the deleted pages (orphaned links) from the database. So users may loose some mails. So its upto you to choose between restoring from a backup and repairing a database.
  One more thing. If you repair the databases, remove all the files from the MDBDATA directory except priv.edb, priv.stm, pub.edb and pub.stm. Do not forget to take a backup of the corrupted database before doing all this.

Regards,
B.Vasanth.
0
 

Author Comment

by:UMOS
ID: 12676145
OK thanks, but I have run Esutel/p and /d but they both end abnormaly becasue the Ebd was not cloesed properly.  I got called in to this 4 days after it crashed, and I don't think they have a back up of there edb's THey are using Veritus with out the exchange client. :(

I have also removed all the files like you suggested and I was able to get the pub.edb to start, but the priv.edb is still corrupted. After removing the files and staring Exchange I tired to run eseutil /r to rebuild the priv but it finished abviously very quickly but was it was still a no go.  So I replaced all the files back into MDBDATA and tried it again and then I get the time stamp error.  Oh by the way this is another issue of AV cleaning out a log file and delting it as I found out late last night.

Got any other suggestions ?  I am about to just start from scratch with the Priv.edb.

Thanks
Ken
0
 
LVL 7

Expert Comment

by:vasanthgnb
ID: 12678971
Hai,
  Do you mean to say that running eseutil with /p and /d switches ended abnormally? If so what is are the messages you got. Check the amount of free spave you have in your harddrive where the databases reside. Because /d switch requires 120% of free space as the size of the database. If you don't have enough free space, use the /t switch for mentioning an alternate location for the temporary database. Post the error messages you are getting when you run /p and /d switches. How big is your database?

refer to this link.
http://support.microsoft.com/kb/192185/EN-US/

Regards,
B.Vasanth.
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 

Author Comment

by:UMOS
ID: 12682926
Ok I fallowed the MS KB artical  Q272570 and when I run :\exchsrvr\bin>eseutil /p /ispriv  I get an error "a read was issued to a location beyond EOF (writes will expand the file)" Error -4001

0
 
LVL 7

Expert Comment

by:vasanthgnb
ID: 12686140
Hai,
   I am sorry to say this, but this is what has happened. The AV has eaten up one or more of the log files. The database got corrupted. This particular error message which you have got clearly states that the database is BEYOND REPAIR. All the steps you have done are exactly correct. Check for bad sectors in the physical harddisk. But I am damn sure that this database has got corrupted to an extent beyond repair. So explain your users clearly and if they have a backup, better restore from that or give them a clean database. If they are ready to spend, you can consult third party companies which extract the data out of corrupted databases which cannot be repaired. Ontrack is one such company which is popular.
Regards,
B.Vasanth.
0
 
LVL 7

Accepted Solution

by:
vasanthgnb earned 2000 total points
ID: 12686153
There is one more step which you can do. If you are running Exchange 2000, install Exchange 2003 in another machine and try repairing the database with the exchange 2003 version of eseutil and isinteg. If your server is exchange 2003, install sp1 and all other patches and then try repairing the database. I would recommend you to do this in a test server. It may work. Its worth giving it a try.
If it works, use exmerge to extract mails into psts for all users and give them a fresh database in the production server.
Regards,
B.Vasanth.
0
 

Author Comment

by:UMOS
ID: 12717334
Thanks I tired that too and the Priv was still corrupted.  After all this I found out that they didn't really use the Exchange server much, and they were building a new one the next week. LOL  I guess this was a good lesson for them to get a good backup system inplace.

Thanks for the input !!!!
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this post, I will showcase the steps for how to create groups in Office 365. Office 365 groups allow for ease of flexibility and collaboration between staff members.
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Suggested Courses
Course of the Month19 days, 17 hours left to enroll

873 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question