Home› AOMEI Products Support

VSS Witer errors with AB Tech 3.5 on SBS 2011

SelfManSelfMan
edited August 2016 in AOMEI Products Support

There are followin 4 errors popping up on SBS2011 after the backup is run.

VSS

Event ID 8194

21.8.2016 3:31:45

8 occurences

Event  Details:   

Volume Shadow Copy Service error:  Unexpected error querying for the IVssWriterCallback interface. hr =  0x80070005, Access is denied. . This is often caused by incorrect security  settings in either the writer or requestor process. Operation: Gathering  Writer Data Context: Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}  Writer Name: System Writer Writer Instance ID:  {13a27cf5-9512-4b5d-a217-b6241203a4a6}

MSExchangeIS

9702

21.8.2016 3:31:25

1

Event  Details:   

Exchange VSS Writer (instance  35986dcf-145e-4b42-ae84-6334797a8c94:33) failed with error code 1295 when  processing the post-snapshot event.


ESE

2007

21.8.2016 3:31:15

1

Event  Details:   

Information Store (2072) Shadow  copy instance 33 aborted. For more information, click http://www.microsoft.com/contentredirect.asp.


MSExchangeIS

9609

21.8.2016 3:31:15

1

Event  Details:   

Exchange VSS Writer (instance  35986dcf-145e-4b42-ae84-6334797a8c94:33) failed with error code -2147221233  when preparing for Snapshot.


Comments

  • adminadmin

    Sorry for this problem. Maybe it fails to enable the VSS service. But please do not worry,it will invoke the AOMEI service to do the operation.

  • SelfManSelfMan

    I've checked the backup, it seems to be ok, but still.. a event log full of error is not what I want.

  • adminadmin

    Thanks for your feedback. We would check it and improve it.

  • yabedudeyabedude
    edited September 2016

    I too am getting two such errors when scheduled jobs start yet the backups appear intact. Am using AOMEI service not MS Task Scheduler. The login account is the local system account. Windows 10 Anniversary Edition.


    #1:


    Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied.
    . This is often caused by incorrect security settings in either the writer or requestor process.

    Operation:
       Gathering Writer Data

    Context:
       Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Name: System Writer
       Writer Instance ID: {5c0f9a2e-39e2-41e0-b79b-1b4a1cca0768}



    and #2:


    Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied.
    . This is often caused by incorrect security settings in either the writer or requestor process.

    Operation:
       Gathering Writer Data

    Context:
       Writer Class Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
       Writer Name: MSMQ Writer (MSMQ)
       Writer Instance Name: MSMQ Writer (MSMQ)
       Writer Instance ID: {8dd401b6-0ac7-4f1f-8620-02fa8c507dcf}



  • adminadmin

    Ok, thanks for your feedback. Please choose the AOMEI server to do the backup. There is something wrong with the anniversary win10 version. We will check this information you give us. Thanks.

  • SelfManSelfMan
    edited July 2017

    We are at version 4.0.4 and these errors are still generated. Is there any chance to get it fixed?

  • SelfManSelfMan

    PROBLEM FIXED

    I didnt have enough Worker Threads for the Sql writer. Read more below.

    For those having issues backing up servers and getting the above mentioned VSS errors, here are the possible reasons and their solutions:

    The VSS (Volume Shadow Compy) service, specifically one of it's writers fails to create a shadow volume copy of the opened files, hence causing the whole process to fail. This causes a cascade of errors logged in the application and system event logs. It also creates a faulty backup.

    One of the most possible causes is the failing SqlServerWriter.
    Some reasons why the SqlServerWiter is failing are:
    a) the SqlVDI driver is not installed
    FIX: (open CMD as Admin)
    net stop vss
    net stop SQLWriter
    cd "C:\Program Files\Microsoft SQL Server\80\COM"
    regsvr32 sqlvdi.dll /s
    net start vss
    net start SQLWriter

    b) There are many databases on the SQL server and the "Maximum worker threads" setting is too low as each database and each shadow copy of the database need an own worker thread. There are also some system worker threads to be counted in.
    FIX:
    Open SQL Management studio
    Open server properties
    Go to Processors and set an apropriate number for "Maximum worker Threads"
    (In case that the setting is not available, advanced options have to be enabled via SQL script.)
    for more info check: https://troubleshootingsql.com/2010/12/06/volume-shadow-barfs-with-0x80040e14-code/

    c) Some VSS operations are performed as NT AUTHORITY\Network Service which is not granted COM access.
    FIX:
    Launch dcomcnfg.exe
    go to Component Services > Computers > right click on your Computer.
    Get to the COM security tab, and grant Network Service the necessary permissions.
    WARNING: This is not true for the SqlServerWriter which runs under System account.

    If yoou have a problem with a different VSS writer, use the followinf command to see which writer is failing.
    run CMD as administor and enter the following command: vssadmin list writers
    (Idealy use it just right after the VSS process fails.)



Sign In or Register to comment.