VSS is Complex OS Component and this time Backup Failures VSS Events 137 and 57 source NTFS which relates to StorageCraft Shadow Copy provider. System State Backups uses VSS to taken open file backups and it always calls provider to take control and backup the required component listed in system state.
This is Windows Server 2008 R2 64 bit which generating lots of NTFS events specially below events
Which do result backup failures as per the first look this does give a clear understanding some corruption volume level which can be fixed from chkdsk on the impacted volume or drive.
Note: You must keep a note before running chkdsk /f on a volume make sure drive is not used by any critical applications or by OS – for example SQL Database is not hosted on that volume or system page file (virtual memory) is not configured on that volume. We need to do some alterations before we run chkdsk /f on volume which holds page files.
To fix the NTFS Windows System error #137 and error # 57
In Windows Server 2008 R2 64 bit I found some error 57 several times followed by error 137. This pattern repeated itself regular interval. The server was experiencing Backup problems other than this repeating error message.
Specifically, it can happen with Vista, Windows 7, and with 2008 release candidate one. The underlying cause is a corrupted file, which can be easily reset. To resolve the issue, follow these procedures:
Open a command prompt: Login to the machine experiencing the error
Run the DOS command prompt with administrative privileges
Run a reset command: At the DOS prompt: “fsutil resource setautoreset true c:”
Validate that the command completes successfully
Close the DOS prompt: exit
Reboot the machine: From the start menu, run shutdown | restart
Note: if this option is not available, you can run in the DOS prompt: shutdown -r
You Might Like : How to Delete Windows Server Backup Copies?
Apart from this I do also suggest to check the vssadmin writers status and other related components
I have ran “vssadmin list writers” which results all writers stable
You must also have check on some old shadows on disks by running a command “vssadmin list shadows”
In our case there is no other shadows listed on the Server – then I would like move on to check the type of providers are there to check that you need to run a command as “vssadmin list providers”
Ok here I can see the issue two providers are running at the same time and that means when VSS calls provider in that both providers like Microsoft Provider and StorageCraft Volume Snapshot Software Provider will try to own the process – this cause a conflict and results a backup failure.
It’s always good practice it use single VSS provider and we will go for native provider rather choosing a 3rd party hardware or software provider.
Just go to services.msc and look for StorageCraft Volume Snapshot Software Provider
Right click and stop the services
Again right click and go to properties and select startup type from manual to disable
And verify the Microsoft Software Shadow Copy Provider Services is set to manual
Please take a clean reboot after the changes – share your views and comments below help others if you get something different – but this does solves issue for me to to Fix Events 137 and 57 source NTFS which relates to StorageCraft Shadow Copy provider.