Table of Contents
Today’s guide is designed to help you if you receive the capi2 error event id 513.
Updated
g.Event ID 513: Cryptographic Services failed while handling the OnIdentity () switch in the System Writer.
g.
- 2 minutes for aria-label = “Article read.
In This Article
This part provides a workaround for Event ID 513 when VSS is running on Windows Server.
Applies to: Server 2019 window, Server 2016 properties window
Original Knowledge Base Number: 3209092
Symptoms
In server windows, when the application calls Volume Shadow Copy Service (VSS) to perform backups, event 513 may be generated:
protocol name: applicationSource: Microsoft-Windows-CAPI2Event ID: 513Task Category: NoneLevel: errorDescription:An error occurred in Cryptographic Services while handling the OnIdentity () call on the System Writer.Details: Impossibleaddlegacydriverfiles: Enabled to save the binary image of the Microsoft Link-Layer Discovery protocol.System error:Access will most likely be denied.
Reason
What is cap12 error?
This issue occurs because the system VSS writer does not have NT AUTHORITY SERVICE read permission (service account). When System Writer runs as a cryptographic service and tries to use the Mslldp. System information from the Microsoft Link-Layer Discovery Protocol driver causes an “Access Denied” error.
This issue occurs because the VSS system writer does not have NT AUTHORITY SERVICE read permission (service account). If System Writer extends the AS Cryptographic Service and tries to allow them to read Microsoft Mslldp.sys information using only the Link Layer Discovery Protocol driver, an Access Denied summary is generated. p>
Workaround
This event log entry will be ignored. To prevent logging of records associated with specific records, allow Microsoft Link-Layer Discovery Protocol (Mslldp.dll) vehicles to handle system writers.
Updated
Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!
Open an authorized Command Prompt window and then run the following command to check your current permissions:
sc sdshow mslldp-
Copy the output line from Ladder 1, add it with
(A ;; CCLCSWLOCRRC ;;; SU), then use the following command to uniquely check the Mslldp access authorization to Add. dll:sc sdset mslldpFor example,
run the following command:
sc sdset mslldp D: (D ;; CCDCLCSWRPWPDTLOCRSDRCWDWO ;;; BG) (A ;; CCDCLCSWRPWPDTLOCRSDRCWDWO ;;; SY) (A ;; CCDCLCSWRPD;) 1P ;; LCR; 5-80-3141615172-2057878085-1754447212-2405740020-3916490453) (A ;; CCLCSWLOCRRC ;;; SU)
Problem
Performing a specific system restore, Backup Exec, DLO, or NetBackup backup generates the following error, and all subsequent scheduled tasks will also fail if the same error occurs.
Message
error
“Cryptographic Services was unable to process the OnIdentity () call here in the System Writer object.
Details: AddLegacyDriverFiles: Failed on the back image of the binary detection protocoltier communication Microsoft. System error: Access is currently denied.
Reason
Solution
Please be aware that this article refers to websites that are not owned or operated by Veritas and therefore Veritas is not responsible for ensuring that such content, including user-friendly content, is displayed on those websites. the party software on which this article depends. It is the responsibility of the user to carry out all necessary checks before fulfilling the requirements described in this article.
Windows Server 2016 – Event CAPI2 Error 513
How do I fix CAPI2 error?
First you need to enter the detailed information, which is not possible. Click Start> Control Panel> Administrative Tools> Event Viewer> Expand Applications and Services> Microsoft> Windows> CAPI2> right-click Operations> select Enable Log> then restart. 2.
Recurring process-related client errors
Cryptographic backup services are hitting a wall when processing an OnIdentity () call that is executing a System Writer object.
Details:
AddLegacyDriverFiles: The Microsoft Link-Layer Discovery protocol binary could not be saved.
1. Use the Microsoft SysInternals Accesschk utility to test secure access to MSLLDP and MUP:
You will find that the accountThe restricted SERVICE record is the largest.
2. Use the sc utility to express security descriptors
Copy from line to MSLLDP and add SERVICE access descriptor
4. Update the security settings of this select command using the SC SDSET command
5. Check the update result and event log the next time we create our backup.
This entry was posted on Tuesday, November 7, 2017 at 12:12 pm and is located under Server, Windows. You can follow any replies to this mailbox through the RSS 2.0 feed.You can stop replying or posting back from your website.
| event ID | 513 | |
| Source | Microsoft Windows CAPI2 | |
| Description | Cryptographic services crash during execution of OnIdentity () call for Object System Writer.% 1. Information | Fort |
| Event for Microsoft: Reason: This experience is logged when Cryptographic Services still cannot process the OnIdentity () call on the System Writer object. Solution: Edit the checklist of entries in the Registry Objects folder – Component Model (COM) applications must have access to the COM + catalog files that are actually stored in the COM catalog folder. If the default ACL in the COM directory folder in our own Windows folder is changed, the Shadow Copy Writer may not work correctly, the appropriate permission must be delegated. To edit the actual ACL in the COM Inventory folder: 1. Click Start and then Computer. 2. Go to% systemdrive% Windows. By default,% systemdrive% is located in C: . 3. Right-click Registry, select Properties, then click the Security tab. 4. Click “Advanced”, then “Change”. 5. When the User Account Control dialog box looks like this, make sure the displayed action still matches yours Your requirements, and then click Next. 6. Click Change to display the maximum number of special permissions required for this folder. 7. Verify that access to the edit list meets the following criteria: The local Administrators group has full control A to help this folder and files. The “Everyone” group contains the list data, the read attributes of the folder – / Read, the primary read attributes and read permissions for this folder and files. The local SYSTEM account provides full control over the permissions applied to this file and files. 8. If the permissions for this file do not match the permissions specified in this procedure, make the appropriate changes and click OK. Verification: To complete this procedure, you must be a member of the local Administrators group, or all users must have full rights. To make sure the Shadow Copy Recorder is working correctly: > 1. Click Start, select All Programs, and then click Accessories. 2. Right Click and “Command Prompt” and select “Run as administrator”. 3. If users When the User Account Control dialog box appears, make sure the company that displays the action displayed is the one you want and click Next. 4. In the Command Prompt window, enter vssadmin Guidelines Writer. 5. Make sure the author name is “System Editor”. appears in the list. |
||
| Reference Links | Microsoft-Windows-CAPI2 with Event ID 513 |
Stop Provocations Immediately
We work side by side with this person to quickly identify cyber threats and avoid food before they cause damage.
Capi2 오류 이벤트 ID 513을 수정하기 쉽습니다.
ID D’événement D’erreur Capi2 Facile à Corriger 513
Einfach Zu Behebende Capi2-Fehlerereignis-ID 513
Fácil De Reparar El Evento De Error Capi2 ID 513
Lätt Att Fixa Capi2 Felhändelse ID 513
Łatwy Do Naprawienia Identyfikator Zdarzenia Błędu Capi2 513
Eenvoudig Op Te Lossen Capi2-foutgebeurtenis-ID 513
ID 513 Do Evento De Erro Capi2 Fácil De Corrigir
Легко исправить ошибку Capi2, событие с кодом 513
ID Evento Errore Capi2 Facile Da Correggere 513
