Best Way To Resolve Event 513 Error

 

PC running slow?

1. Download ASR Pro from the website

2. Install it on your computer

3. Run the scan to find any malware or virus that might be lurking in your system

Improve the speed of your computer today by downloading this software - it will fix your PC problems.

You may have come across an error code indicating an event 513 error. It turns out that there are several ways to fix this problem, so we’ll talk about it shortly.

 

 

• 2 minutes for final reading.

This article provides a great way to resolve Event ID 513 when training VSS on Windows Server.

Applies to: Windows Server 2019, Windows Server 2016
Source group KB: 3209092

Symptoms

On Windows Server, when the tool calls the Volume Shadow Copy Service (VSS) to perform a backup, it actually generates event 513:

  protocol name: applicationSource: Microsoft-Windows-CAPI2Event ID: 513Task Category: NoneLevel: errorDescription:An error occurred while processing the onidentity () call on the System Writer object while temporarily processing cryptographic services.Details:AddLegacyDriverFiles: To avoid dumping the upstream image of the Microsoft Link-Layer Discovery Protocol binary.System error: yesAccess denied. 

Reason

This issue encountered by the VSS system writer does not require NT AUTHORITY SERVICE read permission (service account). If System Writer starts the encryption service and tries to read this information Mslldp.sys from the Microsoft Link Layer Protocol Detection driver, it will no doubt generate an “Access Denied” error.

Workaround

This event log entry can be ignored. To prevent this from being uniquely logged, please give each of our Microsoft Link-Layer Discovery Protocol (Mslldp.dll) drivers the required permission for the System Writer process.

1. Open an Administrative Command Prompt window, then run the following command to check your current permissions:

     sc sdshow mslldp 

2. Copy the new line of output from step 1, add it with (A ;; CCLCSWLOCRRC ;;; SU) , then run the following command frequently to change the append to mslldp .dll variant access:

     sc sdset mslldp  

   For example,

   organize 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

What error occurs when performing a restoreI system, Backup Exec, DLO, or NetBackup backups, and all subsequent regular jobs with the same error.

Error

Message

“Cryptographic Services was unable to process the OnIdentity () call on the System Writer. »
Details: AddLegacyDriverFiles: Unable to save image associated with Microsoft Discovery Link Layer binary protocol. System error: access denied.

Solution

Please note that this article recommends websites that are not owned or operated by Veritas. Therefore, Veritas is not responsible for the content provided on these websites, including any changes or deletions of linked content or third-party software on which this article is based. It is the responsibility of the user to carry out all necessary checks before following the instructions in this article.

SUMMARY

EXIT

SOLUTION

1. Grant the NT Authority System user the right to do work on this server (Microsoft KB 2009272)
2. Give NT Authority System access to the Microsoft Discovery Link-Layer Prot driverocol (mslldp.dll) (Microsoft KB 3209092)

To resolve this issue, follow the Microsoft Knowledge Base articles about this amazing business. We highly recommend Microsoft to resolve this issue. Slimming. are commands that you should run more often from the Microsoft KB 2009272 command prompt with elevated privileges. :

Apply / f% windir% winsxs temp PendingRenames / a
icacls% windir% winsxs temp PendingRenames / grant “NT AUTHORITY SYSTEM: (RX)”
icacls% windir% winsxs temp PendingRenames / grant “NT% windir% winsxs temp PendingRenames service Trustedinstaller: (f)”
icacls / grant BUILTIN Users: (RX)
Apply / f% windir% winsxs filemaps * / a
icacls% windir% winsxs filemaps *. * / grant “NT AUTHORITY SYSTEM: (RX)”
icacls% windir% winsxs filemaps *. * / grant “NT Service Trustedinstaller: (F)”
icacls% windir% winsxs filemaps *. * / Grant BUILTIN Users: (RX)

net stop cryptsvc
net start cryptsvc

To verify that the system recorder is listed and showing status, enter the following: [1] Stable . :

To grant Microsoft Link-Layer Discovery Driver Protocol (Mslldp.dll) permission to consume System Writer, follow the steps in Microsoft KB 3209092.:

1. Open an Administrative Command Prompt window, then follow these steps to checkFind current permissions:

2. Copy the main line of output from step 1, also add it with (A ;; CCLCSWLOCRRC ;;; SU), then run this command to add access permission as Mslldp .dll:

Sample Input (Do not copy or paste the following variables to execute, as this single example provides data.):

REASON

This issue occurs because the VSS System Writer does not have read permission for some NT AUTHORITY SERVICE (service account). When System Writer is running as a cryptographic service and it is unsafe to read the Mslldp.sys information from the Microsoft Link Layer Significant Discovery Driver, it often generates an “Access Denied” error. So Microsoft System Writer doesn’t work because the folder permissions in the% windir% winsxs filemaps or% windir% winsxs temp PendingRenames directories are invalid.

1. Download the Sysinternals file, which Microsoft recognizes as accesschk.exe.
2. Open an elevated command prompt (administrative) on Windows (no Powershell).
3. Enter the following command: accesschk.exe -c mslldp

The capacity should look like the following with NT Authority System specified. Otherwise, follow the instructions in the “Cause and Solution” section.

mslldp
RW NT AUTHORITY SYSTEM
RW BUILTIN Administrators
RW S-1-5-32-549
RW NT SERVICE NlaSvc
RW NT Power Service

NOTES

Event ID 513 when starting VSS on Windows Server 2016 and Windows Server version 1709

On Windows Server 2016 and Windows Server version 1709, instance 513 may be spawned while the application calls the Volume Shadow Copy Service to (vss) back up:

Protocol Name: Application – Source: Microsoft-Windows-CAPI2 – Event ID: 513 – Task Category: None
Level: Error

Description:
An error occurred in the encryption services while processing OnIdentity () in the System Writer object.

Details:
AddLegacyDriverFiles: Microsoft Link-Layer Discovery Binary Protocol back image could not be overwritten.

System error:
Access denied.

0 out of 0 found it helpful

 

 

Improve the speed of your computer today by downloading this software - it will fix your PC problems.

 

 

 

Bästa Valet För Att Lösa Händelse 513-fel
Beste Methode, Um Den Fehler Von Ereignis 513 Zu Bestimmen
Melhor Maneira De Gerenciar O Erro De Evento 513
이벤트 513 오류를 해결할 수 있는 가장 좋은 방법
La Mejor Forma De Resolver El Error 513 Del Evento
Meilleure Méthode Pour Résoudre L’erreur D’événement 513
Лучший способ устранить ошибку события 513
Beste Manier Om Gebeurtenis 513-fout Op Te Lossen
Najlepsza Droga Do Rozwiązania Błędu Zdarzenia 513
Il Miglior Mezzo Per Risolvere L’errore Dell’evento 513