Main Threads:Volume Shadow Copy Service error
  • I'm running Backupper Pro on a 64 bit Windows 10 (clean install) and the following errors related to my scheduled backups appear twice for each backup task in Computer Management>Event Viewer>Windows Logs>Application


    Event 8194, Vss


    General tab:

    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: {8f787654-2e0f-4109-b23b-65e21e5fe73f}



    Details tab (XML view):

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    - <System>

      <Provider Name="VSS" />

      <EventID Qualifiers="0">8194</EventID>

      <Level>2</Level>

      <Task>0</Task>

      <Keywords>0x80000000000000</Keywords>

      <TimeCreated SystemTime="2017-02-21T22:00:16.299974600Z" />

      <EventRecordID>4718</EventRecordID>

      <Channel>Application</Channel>

      <Computer>Eagle</Computer>

      <Security />

      </System>

    - <EventData>

      <Data>0x80070005, Access is denied.</Data>

      <Data>Operation: Gathering Writer Data Context: Writer Class Id:
    {e8132975-6f93-4464-a53e-1050253ae220} Writer Name: System Writer Writer
    Instance ID: {8f787654-2e0f-4109-b23b-65e21e5fe73f}
    </Data>

      <Binary>2D20436F64653A20575254575254494330303030313238392D2043616C6C3A20575254575254494330303030313234332D205049443A202030303030313535362D205449443A202030303030393730382D20434D443A2020433A5C57696E646F77735C53797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>

      </EventData>

      </Event>


    The two errors logged for each scheduled backup task occur about 7 to 10 seconds apart.  One backup is a disk backup and the other is a system backup.  Both use the default (recommended) Vss configuration.


    Can someone exand on what these errors are telling me, their severity, and what to do to correct the problem?

  • Please just ignore this error message. When the software start to run the backup task, it will try to enable the VSS to do the backup. But when it failed to enable it, the software will invoke the AOMEI service to continue to finish the operation. So just ignore it.

    Or you can set the backup task run with the AOMEI service. Please check the schdule setting to change it to use the Aomei service to do the backup.


  • I didn't find a setting for using AOMEI's service in either of the two backup tasks I have, but I did find it under the Menu>Settings on the home screen.  I changed it to use AOMEI's built-in technique and selected it there.  However, the errors still appeared from today's backups.


    I do use Windows Task Scheduler to run the backup tasks because if offers me the option to wake the computer to run the backups if needed.  Windows Task Scheduler offers much more management functionality.

  • OK, if you need to use the windows task scheduler, for the VSS error message, please just ignore it. The task will finish normally.

  • The answers of admin annoys me onece more when he/she says "ignore it".

    There is a problem and it produces an error which is reported in the event log. And it
    can be fixed

    It is not a problem of Aomei Backupper.

    VSS IVssWriterCallback Error Occurs When Creating Backup), this error is caused by incorrect or missing COM access permissions and does not affect the use of Image for Windows.

    Look at
    http://www.eventid.net/display-eventid-8194-source-VSS-eventno-4061-phase-1.htm

    I am not sure if Windows Home Editions are able to do dcomcnfg. Maybe a Wx Home user can clarify.

    For Wx Pro user you can follow the instructions found in the above link.

    Aomei should provide this info to there customers, and if they are not on a Wx Pro, provide
    the necessary Registry fix.


    I am honestly appalled by the nonchalantly advise of admin

  • I added the DCOM network service as described in the link you provided.  I'll post the results after the next set of backups run on March 1.

  • Is it ok now?image

  • The Vss error was replaced with the following error:


    -System


    -Provider



    [
    Name]
    Microsoft-Windows-CAPI2



    [
    Guid]
    {5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}



    [
    EventSourceName]
    Microsoft-Windows-CAPI2


    -EventID513



    [
    Qualifiers]
    0



    Version0



    Level2



    Task0



    Opcode0



    Keywords0x8080000000000000


    -TimeCreated



    [
    SystemTime]
    2017-03-02T22:30:28.833020800Z



    EventRecordID8746



    Correlation


    -Execution



    [
    ProcessID]
    1600



    [
    ThreadID]
    12664



    ChannelApplication



    ComputerEagle



    Security
    -EventData



    Details:
    AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer
    Discovery Protocol. System Error: Access is denied.


    I did some research and found a possible solution here:


    https://answers.microsoft.com/en-us/windows/forum/windows8_1-update/event-513-errors-when-setting-a-restore-point-or/0ac566b0-b16b-4e6f-9344-27800151e21d?page=3&auth=1


    Although it was originally for Windows 8.1, I believe the information also applies to Windows 10.


    I
    added access rights for NT AUTHORITY\SERVICE to MSLLDP.  I'll see if
    that clears the error after today's backup and report the result here.



  • The last change I made detailed in my post #7 cleared the error.  It seems that AOMEI Backupper encountered Windows permissions problems when attempting to back up some items.  I'm not sure if and how Backupper should handle these types of situations.  However, there didn't seem to be any indication from or in Backupper that there was an issue.  Perhaps when this happens, it should at least be written to the log file.  The user should also be made aware that issue occurred, including in the email notification fir the task.  I think it would be sufficient to make a reference to see the forum, and possibly pointing to this post.
  • SOLUTION BELOW:


    I am an IT Professional and have been using AOMEI Backupper for years.  You can resolve this issue by going into Component Services -> Computers -> My Computer and open Properties.  Select the COM Security tab and add Network Service account and grant permissions to both Access Permission (Local Access, not remote) and Launch and Activation (Local for launch and activate, not remote).

    If you do not know how to open Component Services on Windows (Google it).




Start a New Discussion

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!