Windows Backup Failing with error code GetDiskComponents 0x80042302

Rahul Sharma 26 Reputation points
2020-12-11T11:01:50.087+00:00

Hello All,

One of our customer facing below error while executing "vssadmin list writers" command:

Log Name: Application
Source: VSS
Event ID: 8193
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Description:
Volume Shadow Copy Service error: Unexpected error calling routine IVssAsrWriterBackup::GetDiskComponents. hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
.
Operation:
OnIdentify event
Gathering Writer Data
Context:
Execution Context: ASR Writer
Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Name: ASR Writer
Writer Instance ID: {9762616a-76cc-4cac-b81b-1de18ee1dba2}

Operating system is 2012 R2. All the writers state are showing stable and we have tried to re-register the DLL's, chkdsk /f, sfc /scannow, but still this error appears every single time during the execution of "vssadmin list writers" command

Require someone assiatance and guidance on it.

..

Thanks,
Rahul$

Windows Server Backup
Windows Server Backup
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Backup: A duplicate copy of a program, a disk, or data, made either for archiving purposes or for safeguarding valuable files from loss should the active copy be damaged or destroyed.
464 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Mico Mi 1,921 Reputation points
    2020-12-14T07:34:38.53+00:00

    Hi, Here are some basic steps to troubleshoot:

    1. Make sure you have the latest patches installed for Windows.
    2. Run the following command: vssadmin delete shadows /all
    • This will clean up any orphaned shadows. System with too many orphaned shadows can become unresponsive.
    • This does not work with XP or Vista.
    1. Restart the service that is throwing the errors found in either the event log or the list writer command such as Hyper-V VSS writer service.
    2. Restart the following services:
    • COM+ System Application Service
    • Distributed Transaction Coordinator Service
    • Volume Shadow Copy Service
    • Make sure that the Volume Shadow Copy Service/ System Restore Service/ Microsoft Software Shadow Copy Provider are Running and set on Automatic.
    1. For Virtual Machines make sure your guest tools are updated.
    2. Remove 3rd party VSS Writers and test. These are often installed by backup providers like Acronis.
    3. If the machine is hosting virtual machines:

    Thanks for your time! Best Regards, Mico Mi

    If the Answer is helpful, please click "Accept Answer" and upvote it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Rahul Sharma 26 Reputation points
    2020-12-14T11:51:50.073+00:00

    Hi,

    We have done with the basic troubleshooting. The important point here is to identify at which stage this task is failing. As i said before even executing the "vssadmin list writers" command, we are gettting event 8193.

    The error that we are frequently getting, It’s related to “GetDiskComponents”, ASR writer trying to get the disk component information to initiate the backup process but it’s getting failed.

    Diagram mentioned in below article illustrate interactions between the requester, the VSS service, the VSS kernel support, any VSS writers involved, and any VSS hardware providers.

    https://video2.skills-academy.com/en-us/windows/win32/vss/overview-of-processing-a-backup-under-vss

    And it's failing at the "OnIdentify" stage

    ..

    Thanks
    Rahul$

    0 comments No comments

  3. Mico Mi 1,921 Reputation points
    2020-12-15T09:29:43.617+00:00

    Hi, the research forum can do is limited, if you want to do some further research, it is suggested to go to open a case in the following link.
    https://support.microsoft.com/en-us/gp/customer-service-phone-numbers
    Thanks for your time!
    Best regards,
    Mico Mi

    0 comments No comments