Backup failed as Backup job was unable to be assigned (500, 401, 403, 404) / Job Assign Failed!
Backups fail with the error code:
"Job assign failed! -403/401/500"
In addition, the link "Show Agent Log" displays the preceding error:
|Example: "Backup job was unable to be assigned - 401"|
- The ShadowProtect, StorageCraft ShadowCopy Provider, or StorageCraft Raw Agent service may not be running on the protected system. See section 3.1. Check for services.
- The key file created during the registration pairing between the ShadowSnap Agent Service & the Datto Appliance may have been interrupted. See section 3.4. Repair agent communications.
- A proxy server or network security element may be interrupting communication between the ShadowSnap Agent and the Datto Appliance.
- The local firewall settings are blocking/filtering ports 25566 and 139.
- The server's local DNS is unable to resolve
- The ShadowProtect license is expired due to un-installation and re-installation of ShadowProtect. See section 3.3. Check the license.
- All volumes have been excluded for backup from the advanced options tab. See section 3.5. All volumes excluded from backup.
- The backup engine has not been populated. See section 3.4. Repair agent communications.
- A backup job may think it's currently in transit. See section 3.4. Repair agent communications.
2.1. Additional possible causes
If agents are taking constant full backups or differential merges at random intervals, or are encountering intermittent 401, 500, or VSS writer errors, this is a sign that there may be more than one Datto appliance on the network trying to back up the same protected machine.
Datto does not recommend protecting a production system with more than one Datto appliance at the same time. Even if the appliances have different scheduled backup times, both systems cannot work in tandem with each other, because they both store information in the same location on the protected server with the same naming schemes, and will overwrite each others' changes to those files.
Follow these steps to resolve this problem:
3.1. Check for services
Check that all 3 services are present on the target machine via services.msc
- StorageCraft Raw Agent
- StorageCraft Shadow Copy Provider
- ShadowProtect Service
Open up task manager, and end the processes of any instances of the following services:
Restart the services through the services.msc console.
3.2. Network settings
Ensure that all Local/Edge hardware or software have the proper exceptions configured. Depending on the software/hardware, you will need the following information:
- Website: activate.storagecraft.com
- IP address: 126.96.36.199
- Local Service: ShadowProtectSvc.exe
To view the proxy settings use the following commands from a CMD prompt:
Netsh.exe: Netsh winhttp show proxy(with Vista / Server 2008 or newer)
Reset the proxy to "Direct," which will delete any entries listed.
Proxycfg.exe: Proxycfg.exe –d
Netsh.exe: Netsh winhttp reset proxy(with Vista / Server 2008 or newer)
Check Windows Firewall or any Antivirus to make sure exceptions exist for the ShadowSnap application to access ports TCP 25566 and TCP 139.
3.3. Check the License Status
Open up ShadowProtect and determine the license status:
The license should read as active. If it is disconnected, retry the steps for restarting the services for ShadowProtect and ShadowSnap. Ensure that the ShadowProtect software is 5.0.x.
3.4. Repair Agent Communications
- On the Datto device, select Protect and Configure Agent Settings.
- At the bottom of the Configure Agent Settings page, click the Repair Agent Communications button.
- Check the volumes on the advanced options tab, and ensure that the correct volumes are selected for backup.
- Under basic options, change the backup engine to a different engine.
- The agent may think a backup job is already running. To fix this, rename the database where the job state is residing.
- Open services.msc, and stop the StorageCraft Raw Agent.
- Navigate to C:\Program Files (x86)\StorageCraft\ShadowProtect\ShadowSnap.
- Find the file called endptconfig.sqlite3 in that folder. Rename that file to .old
- Restart the StorageCraft Raw Agent Service.
- Repair agent communications on the device, and attempt another backup job.
3.5. All volumes excluded from backup
A protected system's backup jobs would fail if all volumes are excluded from backup. To check if this is the case for your system, follow these steps:
- In the device web interface, click Protect and go to Configure Agent Settings for the protected system.
- Go to the Advanced section and check the settings in Volume Level Backup Control. Make sure that at least one volume is not excluded.