If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting the computer for the protection agent to become available. If the problem persists, do the following: 1) Verify that %ServerName; is remotely accessible from the DPM server. 2) If a firewall is enabled on %ServerName;, verify that it is not blocking requests from the DPM server. 3) If %ServerName; is a workgroup server the password for the DPM user accounts may have changed or expired. To resolve this error, run SetDpmServer with the -UpdatePassword flag on the protected computer and Update-NonDomainServerInfo.ps1 on the DPM server. 4) Restart the DPM Protection Agent service on %ServerName;. If the service fails to start, uninstall the protection agent by using Add or Remove Programs in Control Panel on %ServerName;. Then in the Management task area, on the Agents tab, in the Actions pane, click Install to reinstall the protection agent on %ServerName;.
If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting ...
If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting ...
If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting ...
If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting ...
If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting ...
If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting ...
If you see this error on the primary DPM server then, 1) Check to see if you can reduce the number of express fulls (or file ...
If you see this error on the primary DPM server then, 1) Check to see if you can reduce the number of express fulls (or file ...
If you see this error on the primary DPM server then, 1) Check to see if you can reduce the number of express fulls (or file ...