1. Support
  2. Knowledge base
  3. 100023013

Backup job hangs at 5% while creating a recovery point generating a Windows Application event.

Article: 100023013
Last Published: 2017-12-05
Ratings: 0 2
Product(s): System Recovery

Problem

During a backup, at the stage when a snapshot is to be taken of the drives the Backup job hangs generating the error below:

Error Message

Application log error:

Volume Shadow Copy Service warning: ASR writer Error 0x80042404

Cause

Another VSS-aware backup application may be using the Symantec VSS Provider and not releasing it after it is done.

Solution

This issue may be caused by another VSS-aware backup application using the Veritas VSS Provider and not releasing it after it is done.
  1. Go to Control Panel |Administrative Tools |Component Service.
  2. Click on Component Services.
  3. Go to Component Services | Computers | My Computer | COM+ Applications.
  4. Identify then Right Click on Veritas Software VSS Provider and select Delete.
  5. Close the component services
  6. Open a command prompt window.
  7. Type CD \Program Files\Symantec\Backup Exec System   Recovery\Shared\Drivers .
  8. Run the following command:

NOTE: If the operating system is Microsoft 2003/2008, use the SymsnapProvider.dll file to register the service in the command line. For 64bit OS SymsnapProviderx64.dll.

VssProviderInstall.exe -register "Veritas Software VSS Provider" SymSnapProviderXP.dll "Veritas Software VSS Provider" "Backup Exec System Recovery"

  1. Retry the backup job process.

Note: If the issue persist, see if the SymDB.DashBoard Class has been recorded under \\HKEY_CLASSES_ROOT\AppId.

To make a record. Perform the following steps :-
  1. Go to Control Panel | Administrative Tools | Component Service.
  2. Click on Component Services.
  3. Go to Component Services | Computers | My Computer | DCOM Config.
If the ' SymDB.DashBoard' Class is not recorded, It will generate following prompt :
 
 
 
  1. Click on 'YES' to create a record for SymDB.exe under registries.

Note: If it is necessary to continuously use this method to get BESR to work, identify which application is causing the error and force that application to use something other than the Veritas VSS Provider when performing its snapshots.

Was this content helpful?

Article Languages