Replibit Unable to Get Customers Please Try Again

Troubleshooting VSS (Volume Shadow Service) errors

1. Last updated

2. Relieve as PDF

Disclaimer: The steps mentioned in this article should be performed only after consulting your System Admin. VSS is an Os component, hence it is advisable to consult Microsoft or your system admin before proceeding.

Summary

This article lists solutions to unlike VSS (Book Shadow Copy) related problems that occur during back up and restore.

0x8000ffff: [Catastrophic failure]. Standing with bodily volume...

Description

The client log shows the error: 0x8000ffff[Catastrophic failure]. Continuing with actual book...

Cause

• The COM+ Issue System service is non started.
• The Book Shadow Copy service is not started.

Solution

Launch services.msc from the Run option on the Start menu and ready parameters of the following services as shown in the table.

Services	Status	Start up Type
COM+ Fifty-fifty System	Automatic	Started
Volume Shadow Copy	-	Manual

Go to acme

0x80042304: The volume shadow copy provider is not registered in the system

Clarification

The customer log shows this fault: 0x80042304: The volume shadow copy provider is not registered in the organization.

Cause

Volume shadow copy DLLs are corrupted.

Solution

1. Cease the Volume Shadow Copy service. Open a Command prompt window using thecmd command. At the control prompt enter
   c:\> internet stop vss
2. To change the directory path, enter
   c:\> cd C:\WINDOWS\System32
3. Register the following DLL files. Brand certain you lot are in the Windows\System32 directory. At the control prompt enter:
   c:\Windows\System32>regsvr32 ole32.dll
   c:\Windows\System32>regsvr32 oleaut32.dll
   c:\Windows\System32>regsvr32 vss_ps.dll
   c:\Windows\System32>Vssvc /Annals
   c:\Windows\System32>regsvr32 /i swprv.dll
   c:\Windows\System32>regsvr32 /i eventcls.dll
   c:\Windows\System32>regsvr32 es.dll
   c:\Windows\System32>regsvr32 stdprov.dll c:\Windows\System32>regsvr32 vssui.dll
   c:\Windows\System32>regsvr32 msxml.dll c:\Windows\System32>regsvr32 msxml3.dll
   c:\Windows\System32>regsvr32 msxml4.dll
4. Restart the Volume Shadow Copy service. At the command prompt, enter:
   net get-go vss

Go to superlative

0x80042306: The shadow copy provider had an error. Please see the system and application event logs for more information

Description

This fault occurs when a VSS provider blocks the creation of the VSS snapshot. This may be caused by:

•   Installing a new 3rd party VSS provider.
•   An existing provider becoming corrupted.
•   Destination drive not existence compatible with NTFS format.

To cheque this problem, run NTBackup and try performing a manual backup of your System State. If it is a VSS trouble, the backup will fail.

If NTbackup is successful, check your scheduling to make sure that the backup does not disharmonism with other system activeness. Otherwise, follow the instructions given below.

Solution

• VSS Providers
  Check to see if at that place are any non-standard providers that are causing the trouble when creating a VSS snapshot. To exercise this, go to the command prompt and execute the post-obit command:

  vssadmin list providers

  If at that place are whatsoever non-standard providers listed, consider uninstalling them. Note that the Microsoft default providers are generally very reliable, so uninstalling 3rd party providers may solve the problem.
  If the "vssadmin list providers" command hangs, information technology is probable that a newly installed VSS provider is malfunctioning. In this instance, uninstall these products to resolve the issue.

• Multiple Backups
  Ensure that the backup is not running at the aforementioned time as another fill-in, as the custom provider may merely permit i snap-shot at a time.

• Corrupted data on the bulldoze to be backed up
  Run the CHKDSK control on each drive with the /f switch to fix any errors on the disk.

• VSS believes the system is in setup process
  Check the status of the system by following these steps:

  a. Get to the Registry Editor and locate HKEY_LOCAL_MACHINE\Organisation\Setup
  b. Ensure that the following registry values are set to 0:
  SystemSetupInProgress
  UpgradeInProgress

• VSS dll`s are corrupted
  Re-install the VSS dll`s past following these steps:
  a. Using command prompt, CD to the WINDOWS\system32 directory.
  b. Terminate the Book Shadow Re-create service by executing the command "net stop vss".
  c. Annals the DLLs (click here).

• COM+ needs to be re-installed
  Re-install COM+ by post-obit these steps:
  a. Backup then delete HKLM\Software\Microsoft\COM3.
  b. Boot to Recovery panel and rename clbcatq.dll to ~clbcatq.dll. Brand certain to use the tilde ("~") character.
  c. Boot the machine to normal style and in Control Panel, open the Add or Remove Programs tool and so open the Add/Remove Windows Components tool. Practice non Make any changes, but click Next. This reinstalls COM+.

• Destination drive is not formatted for NTFS

Get to top

0x80042308: The specified object was not institute

Clarification

This error indicates that the backup procedure is having difficulties with backing upwards Open up Files.

Cause

This is due to a problem with the VSS  when performing backups of whatsoever open files or files that are in use at the time of the backup.

Solution

Co-ordinate to Microsoft Premier Back up this is the right procedure to follow when re-registering the Volume Shadow Re-create service DLL'south.

one. Change directory to System32
c:\>cd c:\Windows\System32
c:\Windows\System32>Net stop vss
c:\Windows\System32>Net stop swprv
Register the DLLs (click here)

2. Reboot your machine. Open a control prompt and run:
vssadmin listing writers

three. Ensure that all your writers are displayed without errors.

Go to height

0x8004230c: Shadow copying of the specified volume is not supported

Description

When you try to revert a book on a shared cluster deejay or on a cluster shared book to an earlier version past using Volume Shadow Copy Service (VSS), the following error message is logged in the VSS log file:

Shadow copying the specified book is not supported.

Cause

The crusade of this error is unremarkably a needed service has been disabled or is not starting properly.

Solution

Follow the procedure given below.

1. Open the Control Panel.
2. ClickClassic View in theTasks pane.
3. Double-clickAuthoritative Tools.
4. Double-clickServices.
5. Scroll down and double click theMicrosoft Software Shadow Copy Provider.
6. In theStart-up Type card, selectAutomated.
7. Click theStart button, ClickApply / OK.

Adjacent, coil downward to the Book Shadow Re-create service and perform the aforementioned steps. Exit and reboot the reckoner.

Get to elevation

0x80042312: The maximum number of volumes for this performance has been reached. /  0x80042317: The specified volume has already reached its maximum number of shadow copies

Description

The limitation in number of shadow copies per book is 64. This is the reason that VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHED mistake occurs when yous attempt to create 65th book shadow copy.

When the storage limit is reached, older versions of the shadow copies volition exist deleted and cannot exist restored. In that location is a limit of 64 shadow copies per volume that tin can be stored. When this limit is reached, the oldest shadow re-create will exist deleted and cannot be retrieved.

Cause

The specified volume has already reached its maximum number of shadow copies.

Solution

Delete the oldest shadow copy for the drive, this should clear out the error. Post-obit is the screenshot and the text of the command:

C:\Windows\system32> vssadmin list shadows
vssadmin ane.i - Volume Shadow Copy Service authoritative control-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Contents of shadow re-create set up ID: { 0ea487ca-41a3-450b-8291- 9c4f3e214fd2 }
   Contained 1 shadow copies at creation fourth dimension: 21-05-2015 23:08:45
      Shadow Copy ID: { 4c1fa853-90ae-4562-9f41- 99ae8b57d4e7 }
         Original Book: (C:)\\?\Volume{ 094952b7-2dd7- 11e4-824f-806e6f6e6963 }\
         Shadow Copy Book: \\?\GLOBALROOT\Device\ HarddiskVolumeShadowCopy1
         Originating Auto: DDSPL1251.druva.local
         Service Machine: DDSPL1251.druva.local
         Provider: 'Microsoft Software Shadow Re-create provider 1.0'
         Type: ClientAccessibleWriters
         Attributes: Persistent, Client-attainable, No car release, Differential, Auto recovered

C:\Windows\system32>vssadmin delete shadows /For=C: /Oldest
vssadmin 1.1 - Volume Shadow Copy Service authoritative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Do you really want to delete one shadow copies (Y/Due north): [N]? y
Successfully deleted one shadow copies.

Note: The above is applicative for Window XP, Vista, Win seven and Win 8 machines.

Go to top

0x80042313: The shadow copy provider timed out while flushing information to the volume being shadow copied

Clarification

Check whether the Volume Shadow copy services are started. To start the service, follow the instructions:

1. Go to first, blazon services.msc in outset search box and press Enter.
2. At present, check if Volume shadow copy is running. If not, set it to Outset.

Cause

The VSS backups are declining due the high deejay activity. High deejay activity does not allow VSS to create a shadow copy in the default time menstruum when the volumes are frozen for snapshot.

Solution

Perform the backups when the disk activity is less to avoid third party applications meddling effectually.

Go to top

0x80042314L: VSS encountered issues while sending events to writers

Description

The system was unable to hold I/O writes.

Cause

This can be a transient trouble.

Solution

It is recommended to wait x minutes and try once more.

Become to peak

0x80042315: An error occurred while trying to contact VSS writers. Check for associated errors in the upshot log

Cause

This fault is caused due to a problem with the VSS performing backups of whatever open files or files that are in use at the fourth dimension of the backup.

Solution

1. ClickStart, typeServices in Start Search. When theServices folio is open, cheque for Book Shadow Copy service.
2. Correct-click Volume Shadow Copy service (VSS) and bank check its status.
3. It is stopped, selectStarting time orRestart.

Become to summit

0x80042316: Some other shadow re-create cosmos is already in progress. Delight await a few moments and try over again

Description

This warning is given typically when the VSS is unable to run due to some other case of VSS already running.

Cause and Solution

1. More than one fill-in program installed.
   If you lot have more than one fill-in program installed on your machine, disable all of the programs except for one and effort running the backup task once more.
2. Previous VSS snapshot has non completed properly and is still running.
   Stop and Re-start the Book Shadow Copy service. You can do this by going to Command Panel > Authoritative Tools > Services.
   In one case in Services, detect Volume Shadow Copy and right click and select Restart.
   Also a reboot of the machine is been known to clear this event.
3. Re-register .dll files associated with VSS service. (click here)
4. Apply hotfix to XP X64 Bit.
   An update is available that fixes various Volume Shadow Copy Service issues in Windows  XP X64 Bit https://support2.microsoft.com/defau...b;en-usa;891957

Become to top

0x80042319: A writer did not reply to a GatherWriterStatus call the writer may either take terminated or it may be stuck

Description

This error occurs when the cosmos of the Volume Shadow Copy has a timeout. This is more common during periods of high disk action or on disks that are heavily fragmented.

0x80042318: An error occurred while trying to contact VSS writers. Check for associated errors in the consequence log

Description

The writer infrastructure is not operating properly.

Solution

Check that the Result Service and VSS have been started and also check for errors associated with those services in the fault log.

Get to top

0x8004230f: The shadow copy provider had an unexpected error while trying to process the specified operation

Cause

This issue occurs considering the VSS system files are not registered or the MS Software Shadow Copy Provider service is not started.

Solution

To resolve this issue follow these steps:

1. Fix MS Software Shadow Re-create Provider service to Manual past going to Command Panel > Administrative Tools > Services.
2. If this does not resolve the problem follow step 3.
3. Open a command prompt.
4. Type the post-obit commands at a control prompt. Printing ENTER later you blazon each command.
   c:\>cd /d %windir%\system32
   c:\Windows\System32>Internet stop vss
   c:\Windows\System32>Net stop swprv
   Register the DLL (click here)

Note: The last control may not run successfully. Perform a backup operation to verify that the issue is resolved.

For further assistance please refer Microsoft KB http://support.microsoft.com/kb/940032

Go to tiptop

0x80042301: The fill-in components object is not initialized, this method has been called during a restore performance, or this method has not been called within the correct sequence

Description

A VSS writer depends on another author on a computer that is running Windows  XP X64 Chip Service Pack 2 (SP2).This other writer has a component listing that has no local components.  In this scenario, the VSS writer is non successful when information technology tries to create a snapshot and yous receive the following error code: 0x80042301.

Cause

The VSS returns an case of the error 0x80042301 (VSS_E_BAD_STATE) if a snapshot does include remote components and does not include any local components.

0x80042326: The volume being reverted was lost during revert

Description

Sometimes, during the backup procedure some VSS writers might neglect because of time-out errors that cause the fill-in to fail. A VSS author is a plan or a service that uses the VSS service to save data to a shadow re-create storage area.

Cause

You may experience a problem that causes certain VSS writers to time out during a lengthy shadow copy creation. This problem occurs especially on computers that have slow hard disks, low memory, low CPU speed or on computers that take the deejay write cache disabled.

0x80042321: Some shadow copies were not successfully imported

Description

When yous use VSS to create more than 10 transportable hardware snapshots in Microsoft Windows XP X64 Bit, some of these snapshots may not exist imported inside the allocated time. If the snapshots are not imported, the import functioning fails.

Cause

This problem occurs because of depression time-out values. VSS does not wait long enough for the logical unit of measurement numbers (LUNs) to come up online. This problem occurs when hardware arrays approach the VSS limit of 64 shadow copies per shadow copy set.

Solution

To resolve this trouble, obtain the latest service pack for Windows. The hotfix extends the fourth dimension-out period to allow for the VSS limit.  For further assistance delight refer Microsoft KB http://support.microsoft.com/kb/896592

Go to acme

0x80042320: No shadow copies were successfully imported

Description

When a VSS-based awarding uses the IVssBackupComponents::ImportSnapshots() API to import a shadow re-create that was created on a Microsoft Windows based figurer, the ImportSnapshots() telephone call may fail with a "VSS_E_NO_SNAPSHOTS_IMPORTED" error. This effect occurs when the shadow copy was created from volumes that span multiple partitions.

Crusade

In a volume that spans multiple partitions or multiple disks, the VSS Service marks simply the start partition. Because the additional partitions are not marked VSS cannot afterward import the shadow copies for the additional volumes.

0x80042324: The remote is running a version of the Volume Shadow Re-create Service that does non support remote shadow-copy creation

Description

A remote machine that exposes the share to snapshot runs a VSS version that does not back up creation of snapshots for shares. The remote is running a version of the VSS that does not support remote shadow-copy cosmos.

Solution

There is no specific resolution from Microsoft for this error.

Go to top

0x80042325: A revert is currently in progress for the specified volume. Another revert cannot be initiated until the current revert completes

Description

A revert is currently in progress for the specified volume.  Another revert cannot be initiated until the current revert completes.

Solution

In that location is no specific resolution from Microsoft for this fault.

Go to tiptop

0x8004230e: The given shadow copy provider does not support shadow copying of the specified book

Clarification

The shadow copy provider does not back up shadow copying the specified volume.

Solution

At that place is no specific resolution from Microsoft for this error.

Go to peak

0x8004230d: The object already exists

Description

The object is a duplicate. A component with the same logical path and component name already exists.

Solution

At that place is no specific resolution from Microsoft for this mistake.

Go to top

0x80040154: Error creating shadow re-create provider COM grade (Event ID: 12292 & Event ID: 22)

Description

When a backup starts, inSync creates a snapshot of backup folders using VSS. Then, inSync creates a backup of this snapshot. If the snapshot creation fails, inSync backup fails.  inSync does not have volume backups from the file system.

Cause

A third party provider is being used to perform a shadow copy instead of the organisation provider (Microsoft Software Shadow Copy provider 1.0). The 3rd-party shadow provider keeps failing while taking a shadow copy.

Traceback

inSync log

[2020-01-27 18:xviii:03,680] [INFO] Windows VSS failed to create a snapshot for C:\ at stride 5, status 0x8004230f[The shadow copy provider had an unexpected error while trying to process the specified operation.].                  

Issue log (Source: VSS)

Date: 2020/01/31 xv:59:28 Event ID: 12292 Task Category: None Level: Mistake Keywords: classic User: N / A Computer: XXXXX.Xx.20 Description: Volume Shadow Copy Service fault: Error creating shadow copy provider COM course on CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, class not registered ]. operation: Gets the callable interface for this provider Creates a listing of interfaces for all providers that support this context Delete shadow re-create context: Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092} Grade ID: {3e02620c-e180-44f3-b154-2473646e4cb8}                  

Application log (Source: VSS)

Appointment: 2020/01/31 fifteen:59:28 Event ID: 22 Task Category: None Level: Error Keywords: classic User: N / A Computer:  XXXXX.Xx.Twenty Description: Volume Shadow Re-create Service error: A critical component required by Volume Shadow Copy Service is not registered. An fault may have occurred during Windows Setup or the installation of the Shadow Copy Provider. The error returned from CoCreateInstance for class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} and name SW_PROV is [0x80040154, form not registered ] is. operation: Gets the callable interface for this provider Creates a list of interfaces for all providers that back up this context Delete shadow copy context: Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092} Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}                  

Solution

1. Check the VSS providers using the following command:
   > vssadmin list providers
2. Confirm if there is a 3rd party provider on the motorcar. If yss, then you volition see more than than 1 provider in the output of the to a higher place command.
3. We will now force VSS to always employ Microsoft Software Shadow Copy provider by making the post-obit registry entries:
   1. Click First, click Run, type regedit, and and so click OK.
   2. Locate the post-obit registry subkey, and then correct-click it:
      HKey_Local_Machine\SYSTEM\CurrentControlSet\Control\BackupRestore
   3. Betoken to New, and then click DWORD Value.
   4. Type UseMicrosoftProvider as the name for the new DWORD value, and then press ENTER.
   5. Double-click UseMicrosoftProvider. To enable the new feature, type i in the Value box. To disable the new characteristic, type 0 in the Value box.
   6. Printing ENTER, and then exit Registry Editor.
4. Restart the server.

Disclaimer: Incorrect utilise of the Windows registry editor may prevent the operating system from operation properly. Be conscientious when making whatsoever changes to a Windows registry. It is recommended to take a complete backup of the registry and workstation prior to making whatsoever registry changes.

Verification

1. Trigger a backup. The fill-in will complete successfully.
2. Uninstall the other software from the device whose provider was existence used earlier.

Go to top

wilsontront1939.blogspot.com

Source: https://docs.druva.com/Knowledge_Base/inSync/Troubleshooting/Troubleshooting_VSS_%28Volume_Shadow_Service%29_errors

Share this post