Backup fails with VSS_E_BAD_STATE error (4033126)

Any backup Plugin that uses VSS can have get the error "VSS_E_BAD_STATE". in this example, it is the Plugin for Exchange. 

In the binary log we see 'EXCHANGE-CLIENT' fail to create a snapshot with VSS_E_BAD_STATE error.

At the same time we see a VSS errors in the EXCHANGE-CLIENT application event log, closely proceeded by “Application Error   1000   Application Crashing” in the application log of the client. 

Looking at the “Application Error   1000   Application Crashing” we see “Faulting application name: navssprv.exe”.

This is 'Data ONTAP VSS Hardware Provider'.

To verify that this VSS provider is being used on the client, open a CMD and issue command below and it will display all available providers.

vssadmin list providers

Example output of provider:

Provider name: 'Data ONTAP VSS Hardware Provider'
  Provider type: Hardware
  Provider Id: {ddd3d232-a96f-4ac5-8f7b-250fd91fd102}
  Version: 6. 5. 0. 5474

Binary log extract:

Error   2019/07/01 09:17:51   31153   Data Plugin   EXCHANGE-CLIENT   Failed to create VSS Snapshot on server 'EXCHANGE-CLIENT'

Error   2019/07/01 09:17:51   31153   Data Plugin   EXCHANGE-CLIENT   Failed to add index entries for proxy master 'EXCHANGE-CLIENT'

Error   2019/07/01 16:42:44   31153   Data Plugin   EXCHANGE-CLIENT   Set Backup Complete, VSS Return code: VSS_E_BAD_STATE, number 0x

Application event log entries:

Error   01/07/2019 10:17:51   VSS   12293   None


Error   01/07/2019 10:17:49   Application Error   1000   Application Crashing Events

Faulting application name: navssprv.exe, version: 6.5.0.5474, time stamp: 0x50d04a52
Faulting module name: ntdll.dll, version: 6.1.7601.24441, time stamp: 0x5cb9356e
Exception code: 0xc0000005
Fault offset: 0x000000000002a1ff
Faulting process id: 0x18e24
Faulting application start time: 0x01d52fedd2ce6393
Faulting application path: C:\Program Files\NetApp\SnapDrive\navssprv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 181d3753-9be1-11e9-a8b0-0017a477002e
Faulting package full name: %14
Faulting package-relative application ID: %15