Synology I/o Error Occurred. Please Try Again Later.

Troubleshooting VSS (Volume Shadow Service) errors

1. Final updated

2. Save as PDF

Disclaimer: The steps mentioned in this article should be performed only after consulting your Arrangement Admin. VSS is an Os component, hence it is appropriate to consult Microsoft or your arrangement admin earlier proceeding.

Summary

This article lists solutions to unlike VSS (Volume Shadow Re-create) 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+ Event System service is non started.
• The Book Shadow Copy service is non started.

Solution

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

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

Go to top

0x80042304: The volume shadow re-create provider is non registered in the organisation

Description

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

Cause

Book shadow copy DLLs are corrupted.

Solution

1. Stop the Volume Shadow Copy service. Open up a Control prompt window using thecmd command. At the command prompt enter
   c:\> net end vss
2. To alter the directory path, enter
   c:\> cd C:\WINDOWS\System32
3. Register the following DLL files. Make sure you 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 Book Shadow Re-create service. At the control prompt, enter:
   net start vss

Go to top

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

Clarification

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

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

To check this problem, run NTBackup and try performing a manual fill-in of your Organization State. If it is a VSS trouble, the backup will neglect.

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

Solution

• VSS Providers
  Cheque to see if in that location are any non-standard providers that are causing the problem when creating a VSS snapshot. To exercise this, get to the command prompt and execute the following command:

  vssadmin list providers

  If there are whatever not-standard providers listed, consider uninstalling them. Annotation that the Microsoft default providers are generally very reliable, and then uninstalling 3rd party providers may solve the trouble.
  If the "vssadmin list providers" command hangs, information technology is likely 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 same time equally some other fill-in, every bit the custom provider may just permit i snap-shot at a time.

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

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

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

• VSS dll`due south are corrupted
  Re-install the VSS dll`s by post-obit these steps:
  a. Using command prompt, CD to the WINDOWS\system32 directory.
  b. Stop the Book Shadow Copy service by executing the control "cyberspace terminate vss".
  c. Annals the DLLs (click hither).

• COM+ needs to be re-installed
  Re-install COM+ past following these steps:
  a. Backup and then delete HKLM\Software\Microsoft\COM3.
  b. Boot to Recovery panel and rename clbcatq.dll to ~clbcatq.dll. Make sure to apply the tilde ("~") character.
  c. Boot the machine to normal way and in Control Panel, open the Add together or Remove Programs tool and and then open the Add/Remove Windows Components tool. Do not Brand any changes, merely click Next. This reinstalls COM+.

• Destination bulldoze is non formatted for NTFS

Go to elevation

0x80042308: The specified object was not found

Description

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

Cause

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

Solution

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

1. Change directory to System32
c:\>cd c:\Windows\System32
c:\Windows\System32>Net stop vss

c:\Windows\System32>Cyberspace stop swprv
Register the DLLs (click here)

two. Reboot your machine. Open a command prompt and run:
vssadmin listing writers

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

Go to top

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

Clarification

When you effort to revert a volume on a shared cluster disk or on a cluster shared volume to an before version past using Book Shadow Copy Service (VSS), the following error message is logged in the VSS log file:

Shadow copying the specified volume is not supported.

Cause

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

Solution

Follow the process given below.

1. Open up the Control Panel.
2. ClickArchetype View in theTasks pane.
3. Double-clickAdministrative Tools.
4. Double-clickServices.
5. Curl down and double click theMicrosoft Software Shadow Copy Provider.
6. In theFirst-up Type menu, selectAutomatic.
7. Click theStart button, ClickEmploy / OK.

Adjacent, scroll down to the Volume Shadow Copy service and perform the same steps. Get out and reboot the computer.

Go to top

0x80042312: The maximum number of volumes for this operation 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 volume is 64. This is the reason that VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHED error occurs when you endeavor to create 65th book shadow re-create.

When the storage limit is reached, older versions of the shadow copies will be deleted and cannot exist restored. There is a limit of 64 shadow copies per book that tin exist stored. When this limit is reached, the oldest shadow copy will be 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 bulldoze, this should clear out the fault. Following is the screenshot and the text of the command:

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

C:\Windows\system32>vssadmin delete shadows /For=C: /Oldest
vssadmin i.one - Book Shadow Copy Service administrative control-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Do yous actually want to delete i shadow copies (Y/Northward): [N]? y
Successfully deleted 1 shadow copies.

Note: The to a higher place is applicable 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 book beingness shadow copied

Description

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

1. Become to first, type services.msc in start search box and printing Enter.
2. At present, check if Book shadow copy is running. If non, set it to First.

Cause

The VSS backups are failing due the high disk activity. High deejay activity does not allow VSS to create a shadow re-create in the default time flow when the volumes are frozen for snapshot.

Solution

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

Go to top

0x80042314L: VSS encountered bug while sending events to writers

Description

The organization was unable to concur I/O writes.

Cause

This can exist a transient trouble.

Solution

It is recommended to expect 10 minutes and try once more.

Go to top

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

Cause

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

Solution

1. ClickStart, typeServices in Get-go Search. When theServices page is open up, check for Book Shadow Copy service.
2. Correct-click Volume Shadow Re-create service (VSS) and cheque its status.
3. Information technology is stopped, selectStart orRestart.

Become to top

0x80042316: Another shadow copy creation is already in progress. Delight wait a few moments and try again

Clarification

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

Cause and Solution

1. More than than one backup program installed.
   If you have more than one backup program installed on your automobile, disable all of the programs except for one and try running the fill-in job again.
2. Previous VSS snapshot has not completed properly and is still running.
   Stop and Re-start the Volume Shadow Copy service. You lot can practice this past going to Control Console > Administrative Tools > Services.
   In one case in Services, find Volume Shadow Copy and correct click and select Restart.
   As well a reboot of the automobile is been known to articulate this upshot.
3. Re-register .dll files associated with VSS service. (click here)
4. Apply hotfix to XP X64 Fleck.
   An update is available that fixes various Volume Shadow Copy Service issues in Windows  XP X64 Scrap https://support2.microsoft.com/defau...b;en-us;891957

Get to top

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

Clarification

This error occurs when the creation of the Book Shadow Re-create has a timeout. This is more mutual during periods of high disk activity or on disks that are heavily fragmented.

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

Clarification

The writer infrastructure is non operating properly.

Solution

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

Go to pinnacle

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

Crusade

This upshot occurs because the VSS system files are non registered or the MS Software Shadow Re-create Provider service is not started.

Solution

To resolve this issue follow these steps:

1. Set MS Software Shadow Re-create Provider service to Manual by going to Control Console > Authoritative Tools > Services.
2. If this does non resolve the problem follow footstep 3.
3. Open up a control prompt.
4. Type the following commands at a command prompt. Press ENTER later you lot blazon each command.
   c:\>cd /d %windir%\system32
   c:\Windows\System32>Net stop vss
   c:\Windows\System32>Internet stop swprv
   Register the DLL (click here)

Notation: The last command may not run successfully. Perform a fill-in operation to verify that the upshot is resolved.

For further assistance delight refer Microsoft KB http://back up.microsoft.com/kb/940032

Become to meridian

0x80042301: The backup components object is non initialized, this method has been chosen during a restore operation, or this method has not been chosen inside the correct sequence

Clarification

A VSS writer depends on another writer on a figurer that is running Windows  XP X64 Bit Service Pack two (SP2).This other writer has a component list that has no local components.  In this scenario, the VSS writer is not successful when it tries to create a snapshot and you receive the post-obit fault code: 0x80042301.

Cause

The VSS returns an instance of the fault 0x80042301 (VSS_E_BAD_STATE) if a snapshot does include remote components and does not include whatsoever local components.

0x80042326: The volume existence reverted was lost during revert

Description

Sometimes, during the backup procedure some VSS writers might fail considering of time-out errors that cause the backup to fail. A VSS writer is a program or a service that uses the VSS service to relieve information 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 trouble occurs especially on computers that have deadening hard disks, low retentiveness, low CPU speed or on computers that accept the disk write cache disabled.

0x80042321: Some shadow copies were not successfully imported

Clarification

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

Crusade

This problem occurs because of low 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 menstruation to allow for the VSS limit.  For farther assistance please refer Microsoft KB http://support.microsoft.com/kb/896592

Go to top

0x80042320: No shadow copies were successfully imported

Description

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

Cause

In a book that spans multiple partitions or multiple disks, the VSS Service marks only the first partitioning. 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 Volume Shadow Re-create Service that does not support remote shadow-re-create creation

Description

A remote machine 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 non support remote shadow-copy creation.

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.  Some other revert cannot be initiated until the current revert completes.

Solution

There is no specific resolution from Microsoft for this error.

Get to top

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

Description

The shadow re-create provider does not support shadow copying the specified volume.

Solution

There is no specific resolution from Microsoft for this mistake.

Become to top

0x8004230d: The object already exists

Description

The object is a indistinguishable. A component with the same logical path and component proper noun already exists.

Solution

There is no specific resolution from Microsoft for this error.

Go to elevation

0x80040154: Mistake creating shadow copy provider COM grade (Result 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 take 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 one.0). The third-party shadow provider keeps failing while taking a shadow re-create.

Traceback

inSync log

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

Event log (Source: VSS)

Date: 2020/01/31 fifteen:59:28 Event ID: 12292 Task Category: None Level: Error Keywords: classic User: N / A Computer: XXXXX.XX.20 Description: Book Shadow Copy Service error: Error creating shadow copy provider COM form on CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, form not registered ]. performance: Gets the callable interface for this provider Creates a list of interfaces for all providers that support this context Delete shadow copy context: Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092} Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}                  

Awarding log (Source: VSS)

Engagement: 2020/01/31 fifteen:59:28 Result ID: 22 Task Category: None Level: Fault Keywords: classic User: N / A Computer:  XXXXX.Twenty.20 Description: Volume Shadow Re-create Service error: A critical component required by Book Shadow Re-create Service is not registered. An mistake may take occurred during Windows Setup or the installation of the Shadow Re-create Provider. The fault returned from CoCreateInstance for class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} and name SW_PROV is [0x80040154, course non 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. Bank check the VSS providers using the following command:
   > vssadmin listing providers
2. Confirm if there is a 3rd party provider on the motorcar. If yss, then you will see more than than one provider in the output of the higher up command.
3. We will now force VSS to always use Microsoft Software Shadow Copy provider past making the following registry entries:
   1. Click Start, click Run, type regedit, and then click OK.
   2. Locate the following registry subkey, and so correct-click it:
      HKey_Local_Machine\SYSTEM\CurrentControlSet\Control\BackupRestore
   3. Point to New, and so click DWORD Value.
   4. Type UseMicrosoftProvider as the proper noun for the new DWORD value, and then press ENTER.
   5. Double-click UseMicrosoftProvider. To enable the new feature, type 1 in the Value box. To disable the new characteristic, blazon 0 in the Value box.
   6. Press ENTER, and then exit Registry Editor.
4. Restart the server.

Disclaimer: Incorrect utilize of the Windows registry editor may preclude the operating system from functioning properly. Be conscientious when making any changes to a Windows registry. Information technology is recommended to have a complete fill-in of the registry and workstation prior to making whatever registry changes.

Verification

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

Go to top

knoxfroment96.blogspot.com

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

Share this post