✎ [V8] FAQ: Troubleshooting problem with Volume Shadow Copy [Ahsay Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== [V8] FAQ: Troubleshooting problem with Volume Shadow Copy   =====

<html>
 <b>
  Article ID</b>: 8005
 <br>
 <b>
  Reviewed</b>: 2019-01-15
 <br>
 <br>
 <b>
  Product Version:</b>
   <br>
 AhsayACB / AhsayOBM: 8.1 to 8.x
 <br>
 OS: Windows
</html>


===== Description =====
<html>
Cannot backup exclusively opened file (on Windows platforms) on a local hard disk.
 <br>
 <br>
There are many underlying components in the operating system that may come into play during the backup process to cause the VSS error. This article offers a guideline on how to troubleshoot for errors related to Volume Shadow Copy.
</html>



===== Steps =====
<html>
The following are some steps to follow for troubleshooting errors related to Volume Shadow Copy (these steps may vary depending on the operating system):
 <br>
 <ul>
  <li><font color=black>
   <u>
    Prerequisites of Volume Shadow Copy
   </u>
   <br>
   Which version of Windows are you using?
   <br>
   <br>
   Ensure that the AhsayOBM / ACB client application is installed on a supported Windows platform. &nbsp; Refer to the following KB article for the software compatibility list:
   <br>
   <br>
   <a href="http://wiki.ahsay.com/doku.php?id=public:8001_faq:ahsay_software_compatibility_list_scl_for_version_8.1_or_above">FAQ: Ahsay Software Compatibility List (SCL) for version 8.1 or above</a>
   <br>
   <br>
   <br>
  </font></li>
  
  
  <li><font color=black>
   <u>
    Reboot the affected machine
   </u>
   <br>
   Have you restart the affected computer recently?
   <br>
   <br>
   Try rebooting the affected machine. In some instances, servers that have not been rebooted in a while may cause VSS malfunction. Reboot your server regularly as a preventive and cleanup measure for your system.
   <br>
   <br>
   <br>
  </font></li>
  
  
  <li><font color=black>
   <u>
    Volume Shadow Copy Service (VSS)
   </u>
   <br>
   Ensure that the VSS service is started or can be started properly. &nbsp;Restart the VSS service with the following procedure:
   <br>
   <br>
   <ul>
    <li><font color=black>
     Open Services.msc, click Control Panel, double-click Administrative Tools, then double click Services.
     <br>
     <br>
    </font></li>
    <li><font color=black>
     Right click Volume Shadow Copy, then Restart.
     <br><br>
        <img style="width:70%; border:thin solid black" src="http://wiki.ahsay.com/lib/exe/fetch.php?media=public:8005_1.png"/><br><br>
    </font></li>
    <li><font color=black>
   Restart the following related Windows Services as well: COM+ Event System, COM+ System Application, MS Software Shadow Copy Provider and Remote Procedure Call (PRC).</font></li></ul>
   <br>
   <br>
  </font></li>
  
 
  <li><font color=black>
   <u>
    Re-register VSS files
   </u>
   <br>
   Perform the following procedures to ensure that all VSS related components are correctly registered:
   <br>
   <br>
   In an administrative command prompt, execute the 'RegisterVSS.bat' script file available in the AhsayOBM installation home, reboot the machine afterward.
   <br>
   <br>
    <table border="0" cellpadding="0" cellspacing="0" width="600">
    <tr>
     <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white> >${Install-Home}\bin RegisterVSS.bat</font>
     </td>
    </tr>
   </table>  

   <font color=red>Important:</font> You can safely ignore the error message(s) displayed during the process, some of the DLL files are platform specific.
   <br>
   <br>
   <br>
  </font></li>
  <li><font color=black>
   <u>
    Latest Windows updates from Microsoft
   </u>
   <br>
   Have you installed the latest Windows Updates on the affected computer?
   <br>
   <br>
   Check if you have installed the latest Windows Updates. There may be known issues identified by Microsoft that can be resolved in a hotfix / update:
   <br>
   <br>
   <a href="https://support.microsoft.com/en-us/kb/2996928">https://support.microsoft.com/en-us/kb/2996928</a>
   <br>
   <br>
   <br>
  </font></li>
  <li><font color=black>
   <u>
    Damaged COM+ catalog (for older Windows platforms such as Windows Server 2003)
   </u>
   <br>
   Are the COM+ catalog on the affected computer damaged?
   <br>
   <br>
   Refer to the instructions provided in the following document to clean up the COM+ catalog:
   <br><br>
   <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;315296">http://support.microsoft.com/default.as ... -us;315296</a>
   <br>
   <br>
   <br>
  </font></li>
  <li><font color=black>
   <u>
    Microsoft Visio
   </u>
   <br>
   In some cases, Visio, which is part of Microsoft Office 2003 can cause Volume Shadow Copy to fail. Leverage the event logs found under Event Viewer.
   <br>
   <br>
   For machine with Visio installed, check if the following event is found:
   <br>
   <br>
   Event Type: Error
   <br>
   Event ID: 5013
   <br>
   Description:
   <br>
   Volume Shadow Copy Service error: Shadow Copy writer ContentIndexingService called routine VsServiceChangeState
   <br>
   which failed with status 0x8007041d (converted to 0x800423f4).
   <br>
   <br>
   To resolve the issue, delete the following registry key with regedit.exe, reboot the computer afterward:
   <br>
   <br>
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs\Visio
   <br>
   <br>
   <br>
  </font></li>
  <li><font color=black>
   <u>
    Volume Shadow Copy (VSS) related issue
   </u>
   <br>
   Troubleshoot for VSS related issue. Refer to the following instruction:
   <br>
   <br>
   Ensure that status of all VSS writers and providers are stable:
   <br>
   <br>
   <ul>
    <li><font color=black>
     To output the list of writers and their status, enter the following commands in an elevated command prompt:
     <br>
     <br>
    <table border="0" cellpadding="0" cellspacing="0" width="600">
    <tr>
     <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white> >vssadmin list writers</font>
     </td>
    </tr>
   </table>       
     <font color=red>Important:</font> All writer should have status of [1] Stable.
     <br>
     <br>
    </font></li>
    <li><font color=black>
     To output the list of providers present, enter the following command in an elevated command prompt:
     <br>
     <br>
    <table border="0" cellpadding="0" cellspacing="0" width="600">
    <tr>
     <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white> >vssadmin list providers</font>
     </td>
    </tr>
   </table>        
     If no provider is listed, there may be issue with the installation of operating system itself. &nbsp;Resolution should be pursued with Microsoft support staff.
    </font></li>
   </ul>
   <br>
   Ensure that left-over snapshots are cleaned up:
   <br>
   <br>
   <ul>
    <li><font color=black>
     Enter the following command in an elevated command prompt:
     <br>
     <br>
    <table border="0" cellpadding="0" cellspacing="0" width="600">
    <tr>
     <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white> >vssadmin delete shadows /all</font>
     </td>
    </tr>
   </table>       
     This will clean up all VSS snapshots.
     <br>
     <br>
     Defect operating system may often accumulate hundreds of VSS snapshots that persist in the system and cause Windows to become un-responsive.
    </font></li>
   </ul>
   <br>
   In some case, you may not be able to delete the VSS snapshots with the above command. Perform the following instead:
   <br>
   <br>
   <ul>
    <li><font color=black>
     To decrease the maximum shadow storage size, enter the following command in an elevated command prompt:
     <br>
     <br>
    <table border="0" cellpadding="0" cellspacing="0" width="600">
    <tr>
     <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white> >vssadmin resize ShadowStorage /For=C: /On=C: /MaxSize=300MB</font>
     </td>
    </tr>
   </table>      
     If there is no VSS writer error displayed, but the system is not creating a new VSS snapshot, increase the max shadow storage size on the system instead.
     <br>
     <br>
    </font></li>
    <li><font color=black>
     To increase the maximum shadow storage, enter the following command in an elevated command prompt:
     <br>
     <br>
    <table border="0" cellpadding="0" cellspacing="0" width="600">
    <tr>
     <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white> >vssadmin resize ShadowStorage /For=C: /On=C: /MaxSize=10GB</font>
     </td>
    </tr>
   </table>         
    </font></li>
   </ul>
   <br>

  </font></li>
  <li><font color=black>
   <u>
    Persisting issue
   </u>
   <br>
   <br>
   The problem persists after going through all steps outlined above?
   <br>
   <br>
   Issue related to the Volume Shadow Copy (VSS) Windows services, or the Windows operating system itself should be further pursued with Microsoft support staff.
  </font></li>
 </ul>
</html>


===== Keywords =====
 VSS, volume, shadow, copies, VSC, VS
User Tools

Site Tools

Page Tools
