none
SBS 2011 Backup stuck on “Running Consistency Check for Application Exchange” for Exchange 2010

    Question

  • Hi we have SBS 2011 running exchange 2010 and the backup gets stuck on running consistency check for application exchange. I've ran the following CMD and get the error below, can we please see how to get the database repaired so our backup works. Thanks.

    D:\Program Files\Microsoft\Exchange Server\V14\Mailbox>cd D:\program files\microsoft\exchange server\v14\mailbox\mailbox database 2012010716

    D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 2012010716>ESEUTIL/K E00

    Extensible Storage Engine Utilities for Microsoft(R) Exchange Server

    Version 14.03

    Copyright (C) Microsoft Corporation. All Rights Reserved.

    Error: Access to source database 'E00' failed with Jet error -1811.

    Initiating CHECKSUM mode...

    Verifying log files...

    Base name: E00

    Operation terminated with error -1811 (JET_errFileNotFound, File not found) after 0.16 seconds.

    D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 2012010716>ESEUTIL /K "mailbox database.edb"

    Extensible Storage Engine Utilities for Microsoft(R) Exchange Server

    Version 14.03

    Copyright (C) Microsoft Corporation. All Rights Reserved.

    Error: Access to source database 'mailbox database.edb' failed with Jet error -1

    811.

    Operation terminated with error -1811 (JET_errFileNotFound, File not found) after 0.15 seconds.

    D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 2012010716>ESEUTIL /K "mailbox database 2012010716.edb"

    Extensible Storage Engine Utilities for Microsoft(R) Exchange Server

    Version 14.03

    Copyright (C) Microsoft Corporation. All Rights Reserved.

    Initiating CHECKSUM mode...

    Database: mailbox database 2012010716.edb

    Temp. Database: TEMPCHKSUM14748.EDB

     

     

    File: mailbox database 2012010716.edb

     

                         Checksum Status (% complete)

     

              0    10   20   30   40   50   60   70   80   90  100

              |----|----|----|----|----|----|----|----|----|----|

              .................................................FAILURE: GetQueuedCom

    pletionsStatus:  (23), Data error (cyclic redundancy check).

    (Completion Info: ipage=276056, cpage=2, dwTickDuration=56222)


    Thank you. Chandu Kerai

    Thursday, September 19, 2013 8:03 AM

Answers

All replies

  • Hi,

    Thanks for posting in the forum.

    Regarding the current issue, I suggest we could refer to the following article for troubleshooting.

    Windows Server Backup stuck on “Running Consistency Check for Application Exchange” for Exchange 2010

    http://beccabits.com/2011/09/20/windows-server-backup-stuck-on-running-consistency-check-for-application-exchange-for-exchange-2010/

    As it mentioned, the current issue may be related to the VSS writers, double-check that there are no errors by running the following:
    vssadmin list writers
    And please restart the backup and increase the diagnostics level of the VSS writer.  Then examine the application event log for any warnings/erros while the backup runs.  Post any errors here, so we can take a look together.  From the Exchange Management Shell, execute:
    Set-EventLogLevel "MSExchangeIS\9002 System\Exchange Writer" -Level expert
    and to return it to the defaults:
    Set-EventLogLevel "MSExchangeIS\9002 System\Exchange Writer" -Level lowest

    Here is the similar thread as reference, hope it helps.

    Exchange 2010 and Windows server backup hanging

    http://social.technet.microsoft.com/Forums/exchange/en-US/88adaae6-2930-4785-a85f-9ae4d837eca2/exchange-2010-and-windows-server-backup-hanging

    Best Regards,

    Andy Qi

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Andy Qi
    TechNet Community Support


    Friday, September 20, 2013 6:41 AM
    Moderator
  • Hi Andy,

    The VSS writers seem to be fine as you can see below, however I'm getting the below errors when I run the backup whether its with the advanced diagnostics level or not:

    Microsoft Windows [Version 6.1.7601]

    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Windows\system32>vssadmin list writers

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

    (C) Copyright 2001-2005 Microsoft Corp.

    Waiting for responses.

    These may be delayed if a shadow copy is being prepared.

    Writer name: 'Task Scheduler Writer'

       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

       State: [1] Stable

       Last error: No error

    Writer name: 'VSS Metadata Store Writer'

       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

       State: [1] Stable

       Last error: No error

    Writer name: 'Performance Counters Writer'

       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

       State: [1] Stable

       Last error: No error

    Writer name: 'System Writer'

       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

       Writer Instance Id: {e44ff263-2088-466d-b71a-1298ad98289c}

       State: [1] Stable

       Last error: No error

    Writer name: 'SqlServerWriter'

       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

       Writer Instance Id: {7baefb00-a552-41a9-b564-990697bf9b34}

       State: [1] Stable

       Last error: No error

    Writer name: 'ASR Writer'

       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

       Writer Instance Id: {2a2a48a7-b91a-442a-88f4-16ab673f1008}

       State: [1] Stable

       Last error: No error

    Writer name: 'FSRM Writer'

       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}

       Writer Instance Id: {c830f078-d93a-4bea-a6d9-a40dae25d893}

       State: [1] Stable

       Last error: No error

    Writer name: 'SharePoint Services Writer'

       Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}

       Writer Instance Id: {2a8691d6-7fc6-48ef-a6ea-2fdf6b7c76d1}

       State: [1] Stable

       Last error: No error

    Writer name: 'FRS Writer'

       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}

       Writer Instance Id: {926f9287-91c7-443b-9a91-f692fc8597c2}

       State: [1] Stable

       Last error: No error

    Writer name: 'IIS Config Writer'

       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

       Writer Instance Id: {95524d83-9b99-4b50-9f75-a0823990fb9a}

       State: [1] Stable

       Last error: No error

    Writer name: 'TS Gateway Writer'

       Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}

       Writer Instance Id: {7e097d3d-5720-4c71-a4bc-aaf9e1304e17}

       State: [1] Stable

       Last error: No error

    Writer name: 'IIS Metabase Writer'

       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

       Writer Instance Id: {12fa5e93-877c-47d6-a584-3796b1d5c872}

       State: [1] Stable

       Last error: No error

    Writer name: 'Certificate Authority'

       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}

       Writer Instance Id: {ed04276a-6570-4408-b523-ac9af6d2772b}

       State: [1] Stable

       Last error: No error

    Writer name: 'Dhcp Jet Writer'

       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}

       Writer Instance Id: {ea2815ce-1324-43d7-81be-e81ef532739d}

       State: [1] Stable

       Last error: No error

    Writer name: 'SPSearch4 VSS Writer'

       Writer Id: {35500004-0201-0000-0000-000000000000}

       Writer Instance Id: {a57710a5-e43a-48cb-8de4-f0574561c5bc}

       State: [1] Stable

       Last error: No error

    Writer name: 'MSSearch Service Writer'

       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}

       Writer Instance Id: {e5d924e3-0072-43b0-bebe-55b701247f51}

       State: [1] Stable

       Last error: No error

    Writer name: 'Microsoft Exchange Writer'

       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

       Writer Instance Id: {3f7481a2-b3a6-4b29-9bf6-a4ba4624228d}

       State: [1] Stable

       Last error: No error

    Writer name: 'NPS VSS Writer'

       Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}

       Writer Instance Id: {5333e5fd-cf40-41ca-8dcc-a97944bc6269}

       State: [1] Stable

       Last error: No error

    Writer name: 'BITS Writer'

       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

       Writer Instance Id: {d51a6656-9f6c-4fdc-8938-d0e4982eedc0}

       State: [1] Stable

       Last error: No error

    Writer name: 'WMI Writer'

       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

       Writer Instance Id: {e5e4b277-cf91-438c-89ee-f6f2ce1ed080}

       State: [1] Stable

       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'

       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

       Writer Instance Id: {90979272-7056-43be-881a-1586524fa0fe}

       State: [1] Stable

       Last error: No error

    Writer name: 'NTDS'

       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

       Writer Instance Id: {14d854ff-58fb-4e0d-ac3a-5f32232d7590}

       State: [1] Stable

       Last error: No error

    Writer name: 'COM+ REGDB Writer'

       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

       Writer Instance Id: {03383c99-d079-49f0-b3f2-c24baff9b3e8}

       State: [1] Stable

       Last error: No error

    Writer name: 'Registry Writer'

       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

       Writer Instance Id: {cb684edc-40bf-4076-996e-33cabf0aa1e8}

       State: [1] Stable

       Last error: No error

    C:\Windows\system32>

    Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.

    Error-specific details:

       Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist.

    Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.

    Operation:

       Gathering Writer Data

       Executing Asynchronous Operation

    Context:

       Execution Context: Requestor

       Current State: GatherWriterMetadata

    Error-specific details:

       Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist.

    The start address sts4://kk-srv1/contentdbid={cf0e5a8b-306c-4db2-bd09-9a846f94dd8f} cannot be crawled.

    Context: Application 'Search_index_file_on_the_search_server', Catalog 'Search'

    Details:

                    The object was not found.   (0x80041201)

    Event code: 3001

    Event message: The request has been aborted.

    Event time: 20/09/2013 11:28:58

    Event time (UTC): 20/09/2013 10:28:58

    Event ID: 84ca89ebaf6941109221cdc7ca947ea8

    Event sequence: 232

    Event occurrence: 77

    Event detail code: 0

     

    Application information:

        Application domain: /LM/W3SVC/1572271583/ROOT/ServerSyncWebService-4-130240927892150662

        Trust level: Full

        Application Virtual Path: /ServerSyncWebService

        Application Path: C:\Program Files\Update Services\WebServices\ServerSyncWebService\

        Machine name: KK-SRV1

     

    Process information:

        Process ID: 14540

        Process name: w3wp.exe

        Account name: NT AUTHORITY\NETWORK SERVICE

     

    Exception information:

        Exception type: HttpException

        Exception message: Request timed out.

     

    Request information:

        Request URL: http://kk-srv1:8530/ServerSyncWebService/serversyncwebservice.asmx

        Request path: /ServerSyncWebService/serversyncwebservice.asmx

        User host address: fe80::3958:8373:80bd:5a99Full

        User: 

        Is authenticated: False

        Authentication Type: 

        Thread account name: NT AUTHORITY\NETWORK SERVICE

     

    Thread information:

        Thread ID: 1

        Thread account name: NT AUTHORITY\NETWORK SERVICE

        Is impersonating: False

        Stack trace:

     

     

    Custom event details:


    Thank you. Chandu Kerai

    Friday, September 20, 2013 10:34 AM
  • Andy

    Before I carry this out live, if I want to test this offline beforehand can I copy the exchange database and mount this on a clone of the SBS? or do I need to copy the log files for the database to?


    Thank you. Chandu Kerai

    Tuesday, October 08, 2013 12:01 PM