Another Shadow Copy Creation Is Already in Progress Wait a Few Moments and Try Again

Troubleshooting VSS (Volume Shadow Service) errors

1. Final updated

2. Save every bit PDF

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

Summary

This commodity lists solutions to different VSS (Book Shadow Copy) related problems that occur during support and restore.

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

Description

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

Cause

• The COM+ Upshot System service is not started.
• The Volume Shadow Copy service is non started.

Solution

Launch services.msc from the Run option on the Start card and set parameters of the post-obit services as shown in the table.

Services	Status	Outset up Type
COM+ Even Organisation	Automated	Started
Book Shadow Re-create	-	Transmission

Go to top

0x80042304: The book shadow copy provider is non registered in the organisation

Description

The client log shows this error: 0x80042304: The volume shadow copy provider is not registered in the arrangement.

Cause

Volume shadow copy DLLs are corrupted.

Solution

1. Stop the Volume Shadow Copy service. Open a Command prompt window using thecmd command. At the command prompt enter
   c:\> internet end vss
2. To alter the directory path, enter
   c:\> cd C:\WINDOWS\System32
3. Annals the following DLL files. Make sure y'all are in the Windows\System32 directory. At the command 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 /Register
   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 Re-create service. At the command prompt, enter:
   net start vss

Go to top

0x80042306: The shadow re-create provider had an fault. Please run into the organization and application event logs for more than data

Description

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

•   Installing a new tertiary party VSS provider.
•   An existing provider becoming corrupted.
•   Destination bulldoze not existence compatible with NTFS format.

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

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

Solution

• VSS Providers
  Check to run into if at that place are any non-standard providers that are causing the problem when creating a VSS snapshot. To do this, get to the command prompt and execute the following command:

  vssadmin listing providers

  If in that location are whatsoever non-standard providers listed, consider uninstalling them. Note that the Microsoft default providers are by and large very reliable, so uninstalling tertiary party providers may solve the trouble.
  If the "vssadmin list providers" command hangs, it is probable that a newly installed VSS provider is malfunctioning. In this example, uninstall these products to resolve the upshot.

• Multiple Backups
  Ensure that the fill-in is not running at the aforementioned time every bit another backup, as the custom provider may simply allow one snap-shot at a fourth dimension.

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

• VSS believes the organisation is in setup procedure
  Check the status of the system by post-obit these steps:

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

• VSS dll`due south are corrupted
  Re-install the VSS dll`s by following these steps:
  a. Using control prompt, CD to the WINDOWS\system32 directory.
  b. Stop the Volume Shadow Re-create service by executing the control "internet stop vss".
  c. Register the DLLs (click here).

• COM+ needs to exist re-installed
  Re-install COM+ past following these steps:
  a. Backup then delete HKLM\Software\Microsoft\COM3.
  b. Kicking to Recovery console and rename clbcatq.dll to ~clbcatq.dll. Make sure to utilize the tilde ("~") graphic symbol.
  c. Boot the car to normal mode and in Control Console, open the Add or Remove Programs tool and then open the Add together/Remove Windows Components tool. Do non Make any changes, just click Next. This reinstalls COM+.

• Destination drive is not formatted for NTFS

Go to pinnacle

0x80042308: The specified object was not found

Description

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

Crusade

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

According to Microsoft Premier Support this is the correct procedure to follow when re-registering the Book Shadow Re-create service DLL's.

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

2. Reboot your machine. Open a command prompt and run:
vssadmin list writers

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

Go to top

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

Clarification

When you try to revert a book on a shared cluster disk or on a cluster shared volume to an before version by using Volume Shadow Copy Service (VSS), the post-obit fault bulletin is logged in the VSS log file:

Shadow copying the specified book is not supported.

Crusade

The cause of this fault is usually a needed service has been disabled or is not starting properly.

Solution

Follow the process given below.

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

Next, curlicue down to the Volume Shadow Re-create service and perform the same steps. Get out and reboot the computer.

Become to tiptop

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

Clarification

The limitation in number of shadow copies per volume is 64. This is the reason that VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHED error occurs when you try to create 65th book shadow copy.

When the storage limit is reached, older versions of the shadow copies will exist deleted and cannot be restored. There is a limit of 64 shadow copies per volume that tin can exist stored. When this limit is reached, the oldest shadow copy will exist deleted and cannot exist retrieved.

Crusade

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

Solution

Delete the oldest shadow copy for the drive, this should articulate out the error. Following is the screenshot and the text of the command:

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

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

Note: The above is applicable for Window XP, Vista, Win 7 and Win 8 machines.

Go to top

0x80042313: The shadow re-create provider timed out while flushing data to the volume being shadow copied

Description

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

1. Go to offset, type services.msc in start search box and press Enter.
2. At present, bank check if Volume shadow copy is running. If not, set up information technology to Start.

Cause

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

Solution

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

Become to acme

0x80042314L: VSS encountered bug while sending events to writers

Clarification

The system was unable to hold I/O writes.

Crusade

This tin be a transient problem.

Solution

It is recommended to look ten minutes and try again.

Go to top

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

Cause

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

Solution

1. ClickShowtime, typeServices in Start Search. When theServices page is open up, check for Volume Shadow Copy service.
2. Right-click Book Shadow Copy service (VSS) and check its status.
3. Information technology is stopped, selectStart orRestart.

Get to top

0x80042316: Another shadow re-create creation is already in progress. Delight look a few moments and effort again

Description

This alert is given typically when the VSS is unable to run due to another instance of VSS already running.

Cause and Solution

1. More than than i fill-in programme installed.
   If you take more than one fill-in program installed on your motorcar, disable all of the programs except for ane and try running the fill-in task again.
2. Previous VSS snapshot has not completed properly and is nonetheless running.
   Stop and Re-start the Volume Shadow Copy service. You lot can do this past going to Control Panel > Administrative Tools > Services.
   Once in Services, find Volume Shadow Re-create and right click and select Restart.
   Besides a reboot of the machine is been known to clear this issue.
3. Re-register .dll files associated with VSS service. (click hither)
4. Utilize hotfix to XP X64 Bit.
   An update is available that fixes diverse Volume Shadow Copy Service issues in Windows  XP X64 Bit https://support2.microsoft.com/defau...b;en-united states of america;891957

Go to top

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

Description

This fault occurs when the creation of the Volume Shadow Copy has a timeout. This is more than common during periods of high disk activeness or on disks that are heavily fragmented.

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

Description

The writer infrastructure is non operating properly.

Solution

Bank check that the Event Service and VSS have been started and too cheque for errors associated with those services in the mistake log.

Go to top

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

Cause

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

Solution

To resolve this consequence follow these steps:

1. Ready MS Software Shadow Copy Provider service to Manual by going to Control Console > Authoritative Tools > Services.
2. If this does not resolve the problem follow step 3.
3. Open up a control prompt.
4. Blazon the following commands at a control prompt. Press ENTER subsequently you type each command.
   c:\>cd /d %windir%\system32
   c:\Windows\System32>Internet terminate vss
   c:\Windows\System32>Net stop swprv
   Annals the DLL (click here)

Notation: The last command 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

Get to top

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

Description

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

Crusade

The VSS returns an example 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 beingness reverted was lost during revert

Description

Sometimes, during the backup process some VSS writers might fail because of time-out errors that cause the backup to fail. A VSS author is a programme or a service that uses the VSS service to salve data to a shadow copy storage area.

Cause

You lot may experience a problem that causes certain VSS writers to time out during a lengthy shadow re-create creation. This trouble occurs especially on computers that have deadening hard disks, low memory, low CPU speed or on computers that have the disk write enshroud disabled.

0x80042321: Some shadow copies were not successfully imported

Description

When you apply VSS to create more than ten transportable hardware snapshots in Microsoft Windows XP X64 Bit, some of these snapshots may non exist imported within the allocated time. If the snapshots are not imported, the import operation fails.

Cause

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

Solution

To resolve this problem, obtain the latest service pack for Windows. The hotfix extends the time-out flow to allow for the VSS limit.  For further assistance please refer Microsoft KB http://support.microsoft.com/kb/896592

Go to tiptop

0x80042320: No shadow copies were successfully imported

Description

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

Cause

In a volume that spans multiple partitions or multiple disks, the VSS Service marks but the first partition. Because the additional partitions are non marked VSS cannot later import the shadow copies for the additional volumes.

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

Clarification

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

Solution

At that place 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 exist initiated until the current revert completes

Description

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

Solution

There is no specific resolution from Microsoft for this error.

Get to peak

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

Description

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

Solution

There is no specific resolution from Microsoft for this error.

Go to elevation

0x8004230d: The object already exists

Clarification

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

Solution

There is no specific resolution from Microsoft for this error.

Go to top

0x80040154: Fault creating shadow re-create provider COM class (Event ID: 12292 & Outcome 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 cosmos fails, inSync backup fails.  inSync does not accept book backups from the file arrangement.

Cause

A third party provider is existence used to perform a shadow re-create instead of the system provider (Microsoft Software Shadow Re-create provider ane.0). The third-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 step 5, status 0x8004230f[The shadow copy provider had an unexpected error while trying to process the specified operation.].                  

Consequence log (Source: VSS)

Date: 2020/01/31 15:59:28 Result ID: 12292 Job Category: None Level: Fault Keywords: classic User: Northward / A Computer: XXXXX.Xx.XX Description: Volume Shadow Copy Service fault: Fault creating shadow copy provider COM class on CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, class non registered ]. performance: 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} Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}                  

Awarding log (Source: VSS)

Engagement: 2020/01/31 15:59:28 Result ID: 22 Chore Category: None Level: Error Keywords: classic User: Due north / A Figurer:  XXXXX.XX.Xx Description: Book Shadow Copy Service error: A disquisitional component required by Volume Shadow Copy Service is not registered. An error may accept occurred during Windows Setup or the installation of the Shadow Copy Provider. The error returned from CoCreateInstance for form 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 re-create 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 third party provider on the machine. If yss, and then you lot will run across more than than one provider in the output of the above control.
3. Nosotros volition at present force VSS to ever use Microsoft Software Shadow Re-create provider by making the following registry entries:
   1. Click Start, click Run, type regedit, and and so click OK.
   2. Locate the following registry subkey, and then correct-click information technology:
      HKey_Local_Machine\SYSTEM\CurrentControlSet\Control\BackupRestore
   3. Point to New, and then click DWORD Value.
   4. Type UseMicrosoftProvider as the name for the new DWORD value, and then printing ENTER.
   5. Double-click UseMicrosoftProvider. To enable the new characteristic, blazon 1 in the Value box. To disable the new feature, type 0 in the Value box.
   6. Press ENTER, and and so exit Registry Editor.
4. Restart the server.

Disclaimer: Incorrect use of the Windows registry editor may forbid the operating arrangement from functioning properly. Exist careful when making whatsoever changes to a Windows registry. It is recommended to take a complete backup of the registry and workstation prior to making any registry changes.

Verification

1. Trigger a fill-in. The backup volition consummate successfully.
2. Uninstall the other software from the device whose provider was being used earlier.

Go to top

watermanfreg1972.blogspot.com

Source: https://docs.druva.com/Knowledge_Base/inSync/Troubleshooting/Troubleshooting_VSS_(Volume_Shadow_Service)_errors

Share this post