VSS Access Denied Errors On Admin Account - Event ID 8193 and 13

Question

VSS Access Denied Errors On Admin Account - Event ID 8193 and 13

Anonymous

OS: Windows Server 2022 Standard (this system was bought and set up within the last 8 months)

Errors: VSS Error ID 13 and 8193

Hello I am running into an issue with some form of access and VSS. This was working fine a few weeks ago and then last week I saw the backups failed so I went to check and saw that Veeam was unable to connect to the VSS server on the system. From there I tried to run "vssadmin list writers" on the issue system but that currently states: Error: "A Volume Shadow Copy Service component encountered an unexpected error. Check the Application event log for more information."

Checking the Event log then shows(creates these with each list writers command):

Event ID 13 - Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started. [0x80070005, Access is denied. ] Operation: Instantiating VSS server

Event ID 8193 - Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80070005, Access is denied. . Operation: Instantiating VSS server

What I have tried so far:

restarted the server a few times
restarted VSS service, COM+ service
chkdsk, sfc, and dsim found no issues with windows files.
I have gone through regedit and made sure the needed accounts were added to permissions in VSS/DIAG, this was listed as a fix in a few sources I checked on google. This includes administrators, DHCP, and NETWORK SERVICE
Added Admin, network service, and system to regedit VSS/VssAccessControl, as DWORD with values set to 1.
Added full control of the CLSID to the admin account as recommended by another source.
Checked the COM Security tab in component services, editing the access limits as recommended by another source, adding administrator to said tab.
Used Acronis VSSDoctor to attempt to fix, the batch it would run to fix the components availability does not seem to affect anything. Entering each line individually gives no errors.

The same Veeam server and account information is successfully backing up other systems, it is just this system that is having issues which is a big issue as it is the DC. So the account should not be encountering access issues as far as I can tell as it is working on other systems.

At this point trying to use vssadmin list writers still errors, attempting vssadmin list providers gives an access error. It seems something has somehow messed up the permissions, but is only causing issues on this system and not all across the domain. I am not sure if the issue is with account permissions or if somehow part of VSS is what is being denied. With the affected system being the domain controller and being so new I would rather not have to wipe and re-set up, but at this point I am not sure what else to do. I am iffy with just reinstating one of the backups from when it was "fine" as it may encounter this error again, leading to this issue again. If I have no other option but to reset up the server and then import the GPOs etc then I will but I would rather avoid it.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

4 answers

Answer 1

Hello,

Based on the error screenshot you provided, I suggest you try the following steps:

1.open Regedit and navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl.

Change the value of NT AUTHORITY\NETWORK SERVICE (REG_DWORD) to 1.

*Before changing the value of NT AUTHORITY\NETWORK SERVICE (REG_DWORD), please back up the registry editor by the following steps first.

a. Right-click HKEY_LOCAL_MACHINE then click Export.

b. Export the file to any location you want and name the file.

Run the vssadmin list writers command to verify the system writer is listed now.

Best regards

Zunhui

Answer 2

Anonymous

Thanks for the reply! I mentioned in the attempted fixes tat this was added along with other accounts recommended, but did not provide a screenshot. Here is that now:

As stated ever with this the error still occurs.

Answer 3

Anonymous

This appears to be the case already as shown below:

Upon updating this entry, the error still persists with no change.

Answer 4

Hi UnderAdmin,

This problem occurs because the registry path of the Eventcls.dll file is incorrect.

To resolve this problem, follow these steps:

Click Start, type regedit in the Search programs and files box, and then press ENTER.
Locate and then click the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\\{26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses\\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}
Double-click the TypeLib registry value.
In the Value Data box, type %systemroot%\system32\EVENTCLS.DLL, and then click OK.
Exit Registry Editor.
Click Start, type services.msc in the Search programs and files box, and then press ENTER.
Right-click the following services, one at a time. Click Restart for each service.
- COM+ Event System
- Volume Shadow Copy
Exit the Services snap-in.
Open an elevated command prompt, type vssadmin list writers, and then press ENTER.
Verify that the VSS writers are now listed.

Reference Links:No VSS writers are listed when you run the vssadmin list writers command in Windows Server - Windows Server | Microsoft Learn

Best regards

Zunhui

Share via

VSS Access Denied Errors On Admin Account - Event ID 8193 and 13

4 answers