Hi Ladies and Gentlemen, Tuesday evening, I had an issue where an Exchange DB was corrupted. Managed to get it going with an ESEUTIL /p and /d after and all has been mounted okay. We did a Dial Tone restore whilst the eseutil was running so users could get their mail and carry on working. After the defrag had finished, we then merged the mailboxes from the Dial Tone restore into the repaired (corrupted) database so that they had their recent mail. This seems to have caused a few issues for some people's calendars. I'm seeing 8199 errors on the event logs for different users. Calendaring agent failed in message save notification with error 0x80040219 on user@contoso.com: /Calendar/sadjlaskjd.EML. This is logged when trying to send a meeting request to the user. The following NDR is recieved by the meeting organiser: Delivery has failed to these recipients or distribution lists: USER There's a problem with the recipient's mailbox. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator. _____ Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: svr-exchange3.contoso.com user@contoso.com #550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionFailCallback:16.18969:1C130000, 17.27161:0000000066020000000000000000000000000000, 255.23226:00000000, 255.27962:7A000000, 255.27962:0A000000, 255.27962:0E000000, 255.27962:0A000000, 255.27962:0C000000, 255.17082:19020480, 0.18273:15000000, 4.21921:19020480, 255.27962:FA000000, 255.1494:30110000, 255.1238:4F000000, 4.23921:EC030000, 6.21970:0F0104800B0008670F010480, 4.23921:EC030000, 6.21970:0F0104800201E3650F010480, 4.23921:EC030000, 6.21970:0F0104800201E2650F010480, 4.23921:EC030000, 6.21970:0F0104800201E0650F010480, 4.23921:EC030000, 6.21970:0F01048040008F660F010480, 4.23921:EC030000, 6.21970:0F01048014004B670F010480, 0.21097:0F010480, 4.8756:BFF9FFFF, 4.4353:BFF9FFFF, 0.17114:0F010480, 4.6153:BFF9FFFF, 0.21810:0F010480, 4.5249:BFF9FFFF, 4.13576:BFF9FFFF, 4.11528:BFF9FFFF, 4.5598:BFF9FFFF, 4.4884:19020480, 4.4465:19020480, 4.6926:19020480, 255.1750:6E673A20, 255.31418:2B0A0000, 0.21457:77612E67, 4.19665:19020480". ## Original message headers: Received: from mail.contoso.com ([10.1.4.31]) by mail.contoso.com ([10.1.4.32]) with mapi; Thu, 9 Aug 2012 15:04:34 +0800 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: User 1 <user1@contoso.com> To: User <user@contoso.com> Date: Thu, 9 Aug 2012 15:04:33 +0800 Subject: asdas Thread-Topic: asdas Thread-Index: Ac11/Th1XKPIXqrkQYmVH64WyjMzmgAAAHlg Message-ID: EE16B230AAED654FB8CEB7542F7003CFA14BDDF9@mail.contoso.com Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <EE16B230AAED654FB8CEB7542F7003CFA14BDDF9@mail.contoso.com> MIME-Version: 1.0 <//span>

Hi, Is this person successfully able to receive emails successfully? if so try to move this mailbox to different database and check the same.Kottees : My Blog : Please mark it as an answer if it really helps you.

As imkottees suggest you can try doing a mailbox move to resolve this users issues, however more importantly have you done an ISINTEG against that database? if not that would be job 1 to ensure that the DB is truly healthy else you may experience other issuesThat said even post ISINTEG I would suggest moving ALL users to another database since once a DB is repaired via ESEUTIL /P it is NEVER the same.You may also need to recover damaged items from a previous backup and RSG or a 3rd party product like Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp which will allow you to open any offline EDB within an intuitive GUI so that you can Browse, Search, Export Mailboxes, Folders and Items to PST & MSG or recover/migrate/import direct from an OFFLINE EDB into a production Exchange Server, even cross version i.e. 2003 --> 2007 --> 2010 etc. Troy Werelius www.Lucid8.com Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope

On Thu, 9 Aug 2012 07:27:43 +0000, DaveEmpiredAU wrote: >Tuesday evening, I had an issue where an Exchange DB was corrupted. > >Managed to get it going with an ESEUTIL /p and /d after and all has been mounted okay. > >We did a Dial Tone restore whilst the eseutil was running so users could get their mail and carry on working. > >After the defrag had finished, we then merged the mailboxes from the Dial Tone restore into the repaired (corrupted) database so that they had their recent mail. That's probably the wrong direction! You don't want to keep a repaired database in production. Who knows what's been removed from the database (and we're talking entire database pages, not just individual items). >This seems to have caused a few issues for some people's calendars. I'm seeing 8199 errors on the event logs for different users. After you ran the eseutil, did you run isinteg? Did you run isinteg as many times as necessary until the error and repaired counts stopped decreasing (or were zero)? If you didn't there are (potentially) may problems in the database. Even after you run isinteg you want to get the mailboxes out of that repaired database -- unless you enjoy mysterious problems cropping up. If I were you, I'd run isinteg as many times as necessary and then move the mailboes off that database to a new one. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 9 Aug 2012 12:57:01 +0000, Troy Werelius wrote: >1. As imkottees suggest you can try doing a mailbox move to resolve this users issues, however more importantly have you done an ISINTEG against that database? if not that would be job 1 to ensure that the DB is truly healthy else you may experience other issues2. That said even post ISINTEG I would suggest moving ALL users to another database since Amen! >once a DB is repaired via ESEUTIL /P it is NEVER the same. And neither is your life after that! :-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP