Eseutil Bad Checksum Error Count Found
Contents |
| My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out How to fix "bad checksums" eseutil /k exchange 2010 after I ran Eseutil.exe /k Users viewing this topic: none Logged in operation terminated with error -1003 (jet_errinvalidparameter, invalid api parameter) as: Guest Tree Style Printable Version All Forums >> [Microsoft Exchange 2003] >> General >> How to fix
Eseutil /p
"bad checksums" after I ran Eseutil.exe /k Page: [1] Login Message << Older Topic Newer Topic >> How to fix "bad checksums" after I ran Eseuti... - 16.Jul.2005 11:01:00 AM
Eseutil Error -501
mgtang Posts: 15 Joined: 4.Jul.2002 From: Shanghai Status: offline Dear all,I found I was unable to do a full backup on my Exchange server 2003. The error I've got in my CA Brightstor ArcServe V9 is "E8602 Failed to read from database --EC= Backup Agent Error --(69) Read/Write error in named pipes". So I use eseutil.exe /k to check the eseutil /d database of my Exchange server, I got this result:File: d:\program files\exchsrvr\mdbdata\board.edb Checksum Status (% complete) 0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| ...............................ERROR: page 956171 checksum failed ( 0x779e779ecac5729d / 0x77c277c2c187091b )......ERROR: page 1130500 checksum failed ( 0x64786478ce5a4091 / 0x64786478ce5a4081 )ERROR: page 1130516 checksum failed ( 0x79aa0655e4ab0b31 / 0x79aa0655e4ab0b21 )..............1534146 pages seen3 bad checksums1286 uninitialized pages0 wrong page numbers0xee43d02 highest dbtime (pgno 0xd4)95885 reads performed5992 MB read55 seconds taken108 MB/second56732585 milliseconds used591 milliseconds per read37281 milliseconds for the slowest read79 milliseconds for the fastest readFile: d:\program files\exchsrvr\mdbdata\board.STM Checksum Status (% complete) 0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| ...................................................543744 pages seen0 bad checksums77269 uninitialized pagesOperation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 105.31 seconds.Could anybody tell me how to fix this "bad checksums" error? Thank you! Post #: 1 Featured Links* RE: How to fix "bad checksums" after I ran Es... - 16.Jul.2005 10:45:00 PM jmcbee Posts: 123 Joined: 9.May2005 From: Honolulu, HI Status: offline As you have found, you have corruption in your databa
being unable to download mail items via ActiveSync on any device. The odd thing was that the folder structure would come down
Eseutil /p Exchange 2010
but no mail items would be synched. The customer said it isinteg was working fine until about a week previously. Troubleshooting Looking through Event Viewer in the Application logs eseutil /ml led me to the following events from “MSExchangeIS Mailbox Store”: 10030 A mismatch was detected between a view of a folder and the actual contents of the folder. The http://forums.msexchange.org/How_to_fix_%26quot%3Bbad_checksums%26quot%3B_after_I_ran_Eseutil%25exe_%2Fk/m_150575500/tm.htm mismatched item was ignored. Attempts may be made to rebuild the view, but if this message continues to persist for this mailbox, moving the mailbox to a different database may resolve the issue. Database: Mailbox Database Folder: [MBX:John Smith][AllItems] MsgHeader ID: 1110-1E6B08 Folder ID: 1110-3DA14B View ID: 1110-3DA582 View Name: 1110-3DA14B +A-D-T301c Document ID: 294529 Function: EcPopulateInitialMsgViewTable(Search) Followed https://exchangemaster.wordpress.com/tag/eseutil/ by: 10031 A folder view which previously experienced consistency issues has been deleted and will be rebuilt the next time it is needed. Database: Mailbox Database Folder: [MBX:John Smith][AllItems] MsgHeader ID: 1110-1E6B08 Folder ID: 1110-3DA14B View ID: 1110-3DA582 View Name: 1110-3DA14B +A-D-T301c Function: EcAgeOutOneView After seeing these events I came to the conclusion that there was logical corruption in this user’s Mailbox preventing ActiveSync from pulling the mail items down. So I immediately went to the handy replacement for ISINTEG, “New-MailboxRepairRequest”. (Reference1 Reference2) So in this case I ran the following command: New-MailboxRepairRequest -Mailbox John.Smith -CorruptionType FolderView,ProvisionedFolder,AggregateCounts,SearchFolder The command lets you know the request was created but not much more than that. To view the logs on Mailbox Repair Requests you need to head back to the Application Log in Event Viewer (Reference ) We can see the below entries in the log: 10047 Mailbox level online integrity check for request ec853fb3-1999-4911-9782-5170a31a37cb started: Database=Mailbox Database Mailbox=4F1B824D-5C81-477E-B40B-418C888109F3 Flags=Detect, Fix Tasks=SearchFolder, View, AggregateCount, ProvisionedFid 10062 Corruptions detected during online integrity check for request ec853fb3-1999-4911-9782-5170a31a37cb Mailbox:4F1B824D-5C81-477E-B40B-41
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://serverfault.com/questions/447405/exchange-2010-database-dirty-shutdown and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: exchange 2010 Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Exchange 2010 Database dirty shutdown up vote 2 down vote favorite We experienced a power failure, after i bring the server up the Mailbox database is on a dirty shutdown state. I've ran eseutil /r E00 and got PS E:\BACKUPS_MDB_EXCHANGE\Mailbox Database 1773415643> eseutil bad checksum eseutil /r E00 Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 14.00 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating RECOVERY mode... Logfile base name: E00 Log files: