none
CAPI2 Errors During Backup - Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object

    Question

  • I'm running nightly scheduled wbadmin commands to backup my system to an external USB hard drive. The commands include the -vssFull to integrate them with the volume shadow copy service.

    I'm seeing the following messages logged multiple times in the Application event log, though other indications are that the backup is healthy.  I'd rather not see error messages, but I'm not sure how to resolve this.
     

    Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

    - System
    - Provider
    [
    Name]
    Microsoft-Windows-CAPI2
    [
    Guid]
    {5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}
    [
    EventSourceName]
    Microsoft-Windows-CAPI2
    - EventID 513
    [
    Qualifiers]
    0
    Version 0
    Level 2
    Task 0
    Opcode 0
    Keywords 0x8080000000000000
    - TimeCreated
    [ SystemTime] 2013-12-08T12:29:55.151776500Z
    EventRecordID 4549
    Correlation
    - Execution
    [ ProcessID] 1272
    [ ThreadID] 3692
    Channel Application
    Computer NoelC4
    Security
    - EventData
    Details:
    AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer
    Discovery Protocol. System Error: Access is denied.

     

      • These have occurred since I did the full, clean install of Windows 8.1 roughly a month ago (this was NOT an upgrade).  Four or five of them are logged during the backup, a few seconds or minutes apart.
         
      • These errors did NOT occur back when I had Windows 7 on this same hardware.
       
    • The article here does not resolve the problem; permissions are already right and the System Writer IS listed amongst the known and valid writers.  Notably no error is listed...

    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\TEMP>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    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: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {6d4bc611-4d99-45ba-b86a-bd5209da16db}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {7229e013-1bf8-49e0-8504-fe72982021e6}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {04e0407e-2669-42ff-bd46-08a341f5e508}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {15e1def6-3c7c-4a45-959c-9ce9c3eaa2e6}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {9d76658c-893d-4547-ae52-901a5b3c6c1f}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {78ecea4c-0f0b-4c16-836b-4662698d2386}
       State: [5] Waiting for completion
       Last error: No error


    C:\TEMP>

    Anyone got any ideas whether there's something I can tweak to eliminate these CAPI2 error messages?  If there's nothing I can do, Microsoft, can you please look into fixing this?  I don't care if you ARE deprecating Windows Backup - it's still provided in this release and needs to work error-free.

    Thanks.

       

    -Noel


    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options

    Sunday, December 08, 2013 12:54 PM

All replies

  • Hi Noel, 

    Have you tried solution in this article? If not, please follow it to check the results: 

    Event 513 errors in Windows 8.1

    http://kb.macrium.com/KnowledgebaseArticle50202.aspx

    Hope this could be helpful.


    Kate Li
    TechNet Community Support


    Wednesday, December 11, 2013 6:56 AM
  • Hi Kate,

    Thanks, but that's the exact same information listed at the Microsoft knowledge base link I posted in the original message.  The protections are all set properly.  I just checked them again to be sure.

     

    -Noel


    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options

    Wednesday, December 11, 2013 4:07 PM
  • A bit more information...  The problem is easily reproducible by simply running the vssadmin list writers command listed at the knowledge base links above

    Please see if you can reproduce an error logged in the Application log. 

    Do this:

    • Start an elevated CMD window.
       
    • Type the command
      vssadmin list writers
      and press Enter.
       
    • Look in the Application event log.  Do you see a fresh CAPI2 error there?
        
    EventData

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

     

    -Noel


    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options

    Wednesday, December 11, 2013 4:25 PM
  • Same CAPI2, 513 Error discussed here and here!
    Wednesday, December 11, 2013 4:39 PM
  • A bit more information...  The problem is easily reproducible by simply running the vssadmin list writers command listed at the knowledge base links above

    Please see if you can reproduce an error logged in the Application log. 

    Do this:

    • Start an elevated CMD window.
       
    • Type the command
      vssadmin list writers
      and press Enter.
       
    • Look in the Application event log.  Do you see a fresh CAPI2 error there?
        
    EventData

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

     

    -Noel


    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options


    Also easy to reproduce just by manually creating a restore point.
    Wednesday, December 11, 2013 4:41 PM
  • Looking at he original error message: we need to find where the BINARY IMAGE of the "Microsoft Link-Layer Discovery Protocol" is stored and look at access rights to this image.

    Interestingly on my Laptop where only WiFi is active as a network connection LLDP is not enabled in the adapter settings and the Laptop does NOT produce the CAPI2 513 error on backup and VSS.

    On my Desktop however, LLDP is enabled for the Ethernet adapter and the error is logged.

    ALso there is a difference as to Laptop running 32bit and Desktop 64bit versions of Windows 8.1 respectively.

    Wednesday, December 11, 2013 4:44 PM
  • Thanks for your comments, Win7ine.  Glad to hear I'm not alone.

    I'm a bit too bleary-eyed from a long day of work to attack this any further tonight and try to figure out where LLDP is in the file system, but tomorrow is another day!

     

    -Noel


    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options

    Thursday, December 12, 2013 3:01 AM
  • Well, I searched and poked around and I cannot find a file or folder that seems to be protected in a way that this error should occur.  The wording of the message implies something a bit more complex than file access problems anyway.

    Kate and company at Microsoft, please see that this information is rolled-up to whomever is involved with wbadmin and the BLock Level Backup Engine service, as I'd really like to get this one last error message out of my Application log.  Everything's clean there but this.  Though I have tested a system image backup to ensure a system could be restored from it, messages like this make me nervous.

     

    -Noel


    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options

    Friday, December 13, 2013 1:51 AM
  • Hi Noel, 

    As I known, vss feature is removed from Windows 8.1. That means even we have vss service but we need to develop to use this feature. 

    To backup a system image in Windows 8.1, how about following script:

    wbAdmin start backup -backupTarget:D: -include:C: -allCritical -quiet


    Kate Li
    TechNet Community Support

    Wednesday, December 18, 2013 1:09 PM
  • Thanks, but respectfully, please check your facts again

     

    Nowhere is it documented that a shadow copy-integrated System Image backup is removed from Windows 8.1.

     

    The -vssFull switch is documented by the wbadmin command itself.  I suggest you run the following command to see this yourself:

      wbadmin start backup -?

    in fact this works, and creates a System Image backup that's incremental, and can be restored (I've tested it):

      wbadmin start backup -allCritical -vssFull -quiet -backupTarget:G:\

    Not only does the -vssFull switch still exist, but there is a way to create a System Image backup right from the GUI:

     

      

     

    The only thing that's been removed, as I can see, is the way to use the Windows GUI to schedule the above operation to occur repeatedly via the Task Scheduler, so I have scheduled the wbadmin start backup command I listed above myself.

    So no, it's not removed.  It's available, documented, and needs to be made to work without emitting error messages.

    Thanks.

     

    -Noel


    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options



    • Edited by Noel Carboni Wednesday, December 18, 2013 1:31 PM
    Wednesday, December 18, 2013 1:27 PM
  • Hi Noel,

    I had exact the same issue, this Microsoft hotfix helped, 'System Writer' is showing when I type vssadmin list writers command.

    http://support.microsoft.com/kb/2807849

    The only difference was that in your case, System Writer was showing, but it was waiting for the completion.


    If this helped you resolve your issue, please mark it Answered, thanks! Kind regards

    Monday, June 23, 2014 11:07 AM
  • Thanks, Vladimir,

    I had already solved it, but unfortunately I neglected to post back here.  The (rather convoluted) solution, involving granting additional access rights, is here:

    http://answers.microsoft.com/en-us/windows/forum/windows8_1-hardware/cryptographic-services-failed-while-processing-the/c4274af3-79fb-4412-8ca5-cee721bda112

    At the moment, knocking on wood, I'm logging no errors on a regular basis.

     

    -Noel


    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options

    Monday, June 23, 2014 1:15 PM
  • Hi Noel,

    thanks for sharing. I hope this will help others in solving this particular issue.


    If this helped you resolve your issue, please mark it Answered, thanks! Kind regards

    Monday, June 23, 2014 1:25 PM