User Tools

Site Tools

You are here: Ahsay Wiki » Welcome to AhsayWiki » 8072_issue » [V8] ISSUE: [VSSDatabaseExpt] VSS_E_UNEXPECTED_PROVIDER_ERROR (MS SQL database backup in VSS mode)

Sidebar

Announcement

Ahsay Backup Software

Backup Set Types

Supported Storage

Features in OBM / ACB

Features in CBS

Brand and Customize

License

Documentation

Performance Testing

FAQs and Known Issues

Can't Find What You Need?

public:8072_issue:mssql_server_database_backup_vssdatabaseexpt_e_unexpected_provider_error

This is an old revision of the document!

Table of Contents

ISSUE: MS SQL Server database backup "[VSSDatabaseExpt] ¢SS_E_UNEXPECTED_PROVIDER_ERROR" (VSS backup mode)

Article ID: 8072
Reviewed: 09/04/2020

Product Version:
AhsayOBM: 7.3.0.0 or above
OS: Windows

Problem Description

When performing either a scheduled or manual MS SQL Server database backup job in VSS backup mode. The following backup error are received in the backup report:

No. Type Timestamp Log
* info ... Using Temporary Directory ...
* erro YYYY/MM/DD hh:mm:ss Cannot start shadow copy, reason =¢SS_E_UNEXPECTED_PROVIDER_ERROR
* ... ... ...
* erro YYYY/MM/DD hh:mm:ss [VSSDatabaseExpt] ¢SS_E_UNEXPECTED_PROVIDER_ERROR
The backup error persists even after the following actions have been performed.

  1. The MS SQL Server version is updated to the latest service pack / rollup
  2. The MS SQL Server Server has been rebooted
  3. The VSS writers has been re-registered using the %OBM_INSTALL_PATH%\bin\RegisterVSS.bat
Checking the status of the VSS writers using the vssadmin list writers command shows the 'SqlServerWriter' is still in a "Failed" state.

Example: 

C:\Users\Administrator>vssadmin list writers
vssadmin 1.1 -Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Writer name: 'System Writer'
 Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
 Writer Instance Id: {a2f2507d-b348-493a-9685-da3f20959e9d}
 State: [1] Stable
 Last error: No error

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'
 Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
 Writer InstanceId: {1aab9829-3b91-46bc-a7f1-ae9e1123c2fe}
 State: [1] Stable
 Last error: No error

Writer name:'SqlServerWriter'
 Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
 Writer InstanceId: {3de4f842-4d57-4198-9949-3b3f8c2629dc}
 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: '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

Cause

There is not enough space on the MS SQL server to create a VSS snapshot of the database because the maximum size of the shadow storage area is too small.

Resolution

To resolve this issue, consider resizing the shadow storage area on the MS SQL server.

Please refer to the Microsoft Documentation for details on how to resize the shadow storage area

Keywords

UNEXPECTED, PROVIDER_ERROR, VSSDatabaseExpt, shadow storage, resize, VSS Writer, SqlServerWriter

public/8072_issue/mssql_server_database_backup_vssdatabaseexpt_e_unexpected_provider_error.1586411040.txt.gz · Last modified: 2020/04/09 13:44 by yuk.cheng

Page Tools