User Tools

Site Tools


public:8071_issue:exchange_database_backup_vssdatabaseexpt_e_unexpected_provider_error

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
public:8071_issue:exchange_database_backup_vssdatabaseexpt_e_unexpected_provider_error [2020/04/09 13:42]
yuk.cheng
public:8071_issue:exchange_database_backup_vssdatabaseexpt_e_unexpected_provider_error [2020/11/17 23:40] (current)
edward.chan
Line 1: Line 1:
-=====  ISSUE: MS Exchange database backup ​"​[VSSDatabaseExpt] ¢SS_E_UNEXPECTED_PROVIDER_ERROR" ​=====+=====  ISSUE: ​[VSSDatabaseExpt] VSS_E_UNEXPECTED_PROVIDER_ERROR (MS Exchange database backup=====
  
 <​html>​ <​html>​
Line 17: Line 17:
  </​b>​  </​b>​
  <​br/>​  <​br/>​
- ​AhsayOBM: ​7.3.0.0 or above+ ​AhsayOBM: ​8.1.0.0 or above
  <​br/>​  <​br/>​
  OS: Windows  OS: Windows
Line 72: Line 72:
    </​td>​    </​td>​
    <​td bgcolor="#​ffffff"​ style="​BORDER-LEFT:​ #C0C0C0 1px solid; BORDER-RIGHT:​ #C0C0C0 1px solid; BORDER-BOTTOM:​ #C0C0C0 1px solid" valign="​middle">​    <​td bgcolor="#​ffffff"​ style="​BORDER-LEFT:​ #C0C0C0 1px solid; BORDER-RIGHT:​ #C0C0C0 1px solid; BORDER-BOTTOM:​ #C0C0C0 1px solid" valign="​middle">​
-    <font color=#​FF0000>​ Cannot start shadow copy, reason =¢SS_E_UNEXPECTED_PROVIDER_ERROR+    <font color=#​FF0000>​ Cannot start shadow copy, reason =VSS_E_UNEXPECTED_PROVIDER_ERROR
     </​font>​     </​font>​
    </​td>​    </​td>​
Line 119: Line 119:
 <ol> <ol>
  <​li><​font color=black> ​  <​li><​font color=black> ​
-  The MS Exchange version is updated to the latest service pack / rollup</​font>​+  The MS Exchange version is updated to the latest service pack / rollup.</​font>​
  </​li>​  </​li>​
  <​li><​font color=black> ​  <​li><​font color=black> ​
-  The MS Exchange Server has been rebooted+  The MS Exchange Server has been rebooted.
   </​font>​   </​font>​
  <​li><​font color=black> ​  <​li><​font color=black> ​
-  The VSS writers ​has been re-registered using the <b>%OBM_INSTALL_PATH%\bin\RegisterVSS.bat</b></​font>​+  The VSS writers ​have been re-registered using the %OBM_Install_home%\bin\RegisterVSS.bat</​font>​
  </​li>​  </​li>​
 </ol> </ol>
-Checking the status of the VSS writers using the <b>vssadmin list writers</​b> ​command shows the <​b>'​Microsoft Exchange Writer'</​b> ​is still in a <b>"​Failed"​</​b> ​state.+Checking the status of the VSS writers using the vssadmin list writers command shows the "Microsoft Exchange Writer" ​is still in a "​Failed"​ state.
 <br> <br>
 <br> <br>
-</​html>​ 
 Example: Example:
-<code+<br> 
-C:\Users\Administrator>​vssadmin list writers +<​br>​ 
-vssadmin 1.1 -Volume Shadow Copy Service administrative command-line tool +    <table border="​0"​ cellpadding="​0"​ cellspacing="​0"​ width="​850">​ 
-(C) Copyright 2001-2013 Microsoft Corp.+    <​tr>​ 
 +     <​td style="​BACKGROUND-COLOR:​ black">​ 
 +      <font size=2 color=white><​p style="​font-family:​courier;">​  
 +     ​ 
 +C:\WINDOWS\system32>​vssadmin list writers<br> 
 +vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool<br> 
 +(C) Copyright 2001-2013 Microsoft Corp.<​br>​ 
 +<​br>​ 
 +Writer name: '​System Writer'<​br>​ 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}<​br>​ 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​Writer Instance Id: {a2f2507d-b348-493a-9685-da3f20959e9d}<​br>​ 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​State:​ [1] Stable<​br>​ 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​Last error: No error<​br>​
  
-Writer name: 'System ​Writer'​ +... 
- ​Writer Id: {e8132975-6f93-4464-a53e-1050253ae220+<​br>​ 
- ​Writer Instance Id: {a2f2507d-b348-493a-9685-da3f20959e9d+<​br>​ 
- ​State:​ [1] Stable +Writer name: '​Microsoft Exchange Writer'<​br>​ 
- Last error: No error+&​nbsp;&​nbsp;&​nbsp;&​nbsp;​Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}<​br>​ 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​Writer Instance Id: {2e8409fa-1dd8-483c-ba95-5c9277be0509}<​br>​ 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​State:​ [7] Failed<​br>​ 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​Last error: No error<​br>​ 
 +<​br>​ 
 +Writer name: 'FRS Writer'​<br> 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}<br> 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​Writer Instance Id: {d35e3901-f9b9-4fa6-86af-36b8a4872933}<br> 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​State: [1] Stable<br> 
 +&​nbsp;&​nbsp;&​nbsp;&​nbsp;​Last error: No error<br>
  
-Writer name: 'COM+ REGDB Writer'​ +...
- ​Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} +
- ​Writer Instance Id: {60b9b261-ab81-4c4d-be0f-5d432a4dea64} +
- ​State:​ [1] Stable +
- Last error: No error+
  
-Writer name: 'ASR Writer'​ +     </​td>​ 
- Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} +    </​tr>​ 
- Writer InstanceId: {1aab9829-3b91-46bc-a7f1-ae9e1123c2fe} +   </​table> ​ 
- ​State:​ [1] Stable +</html  
- Last error: No error +    
- +   
-Writer name: '​Microsoft Exchange Writer'​ +
- ​Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7} +
- ​Writer Instance Id: {2e8409fa-1dd8-483c-ba95-5c9277be0509} +
- ​State:​ [7] Failed +
- Last error: No error +
- +
-Writer name: 'FRS Writer'​ +
- ​Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29} +
- ​Writer Instance Id: {d35e3901-f9b9-4fa6-86af-36b8a4872933} +
- ​State:​ [1] Stable +
- Last error: No error +
- +
-Writer name: 'IIS Metabase Writer'​ +
- ​Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366} +
- ​Writer Instance Id: {3303e28e-afae-4c99-8f1a-2ce23e6455a7} +
- ​State:​ [1] Stable +
- Last error: No error +
- +
-Writer name: '​Shadow Copy Optimization Writer'​ +
- ​Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} +
- ​Writer Instance Id: {8e19e851-95ca-4c97-813d-4bc51898c7ac} +
- ​State:​ [1] Stable +
- Last error: No error +
-</code>+
  
 ===== Cause ===== ===== Cause =====
 <​html>​ <​html>​
-There is not enough space on the MS Exchange server to create a VSS snapshot of the database ​because ​the maximum size of the shadow storage area is too small.+This issue can occur if there is not enough space on the Exchange server to create a VSS snapshot of the database. In other words, ​the maximum size of the shadow storage area is too small.
 </​html>​ </​html>​
  
Line 189: Line 181:
 ===== Resolution ===== ===== Resolution =====
 <​html>​ <​html>​
-<font color=black>​ To resolve this issue, consider ​resizing ​the shadow storage area on the MS Exchange server.<​font> ​+<font color=black>​ To resolve this issue, consider ​to resize ​the maximum ​shadow storage area on the MS Exchange server.<​font> ​ 
 +<​br><​br>​ 
 +Refer to the following Microsoft Document for details on how to resize the shadow storage area:
 <​br><​br>​ <​br><​br>​
- <a class="​postlink" ​href="​https://​docs.microsoft.com/​en-us/​windows-server/​administration/​windows-commands/​vssadmin-resize-shadowstorage">​ +<a href="​https://​docs.microsoft.com/​en-us/​windows-server/​administration/​windows-commands/​vssadmin-resize-shadowstorage">​https://​docs.microsoft.com/​en-us/​windows-server/​administration/​windows-commands/​vssadmin-resize-shadowstorage</a>
-  Please refer to the Microsoft Documentation for details on how to resize ​the shadow storage area</a>+
 </​html>​ </​html>​
  
 ===== Keywords ===== ===== Keywords =====
 UNEXPECTED, PROVIDER_ERROR,​ VSSDatabaseExpt,​ shadow storage, resize, VSS Writer, Microsoft Exchange Writer UNEXPECTED, PROVIDER_ERROR,​ VSSDatabaseExpt,​ shadow storage, resize, VSS Writer, Microsoft Exchange Writer
public/8071_issue/exchange_database_backup_vssdatabaseexpt_e_unexpected_provider_error.txt · Last modified: 2020/11/17 23:40 by edward.chan