VSS System Writer is not found on this system

While backing up Windows servers with Networker you may encounter any of the following errors:

• Error :- No Error
• Error:- 98266:save: The VSS System Writer is not found on this system. The backup is stopping because the System Writer is required for a successful system state backup. Have the system administrator check the VSS infrastructure and fix the issue.
• Error:- 61320:save: Cannot bind socket to connection port in configured port range on system "Client Name": The requested address is not valid in its context.

There are many causes for these errors. In a nutshell this boils down to a common permission issues to files in the %windir%\winsxs\filemaps\ or %windir%\winsxs\temp\PendingRenames.

According to Microsoft, you should try the folowing solution, then try a test backup:

1. COM+ Event System
2. COM+ System Application
3. Distributed Transactions Coordinator
4. Microsoft Software Shadow Copy Provider
5. Volume Shadow Copy service
6. Networker remote exec service

The simplest method of performing theses tasks is to run the following commands in an elevated command prompt:

takeown /f %windir%\winsxs\temp\PendingRenames /a
icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\temp\PendingRenames /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\temp\PendingRenames /grant BUILTIN\Users:(RX)

takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)

net stop cryptsvc
net start cryptsvc

Then verify that the system writers are now available by running the following:

vssadmin list providers
vssadmin list writers
vssadmin list shadowstorage

If the system writer is missing, check the application event log. Review https://support.microsoft.com/es-ar/kb/2009272#/es-ar/kb/2009272 for more information.

I found that in most cases "vssadmin [providers|writers|shadowstorage]" are incorrectly configured.