If you just installed an agent on %ServerName;, the computer might be restarting. Wait a few minutes after Windows starts ...

If you just installed an agent on %ServerName;, the computer might be restarting. Wait a few minutes after Windows starts for the agent to become available. Otherwise, troubleshoot the problem as follows:
1) Check recent records from the DPMRA source in the Application Event Log on %ServerName; to find out why the agent failed to respond.
2) Make sure that the DPM server is remotely accessible from %ServerName;.
3) If a firewall is enabled on the DPM server, make sure that it is not blocking requests from %ServerName;.
4) Restart the DPM Protection Agent service on %ServerName;. If the service fails to start, re-install the protection agent.

If you expect the SharePoint farm to grow further, consider protecting the SharePoint SQL Server databases independently. ... If you have another copy of this tape, use that instead for the re-catalog operation. If this is the only copy of the tape ... If you have another copy of this tape, use that instead for the recatalog operation. If this is the only copy of the tape ... If you have re-imported the management pack recently, the role configuration may be corrupted. Open the DPM-specific roles ... If you just installed an agent on %ServerName;, the computer might be restarting. Wait a few minutes after Windows starts ... If you just installed an agent on %ServerName;, the computer might be restarting. Wait a few minutes after Windows starts ... If you just installed an agent on %ServerName;, the computer might be restarting. Wait a few minutes after Windows starts ... If you just installed an agent on %ServerName;, the server might be restarting. Wait a few minutes after Windows starts for ... If you just installed an agent on %ServerName;, the server might be restarting. Wait a few minutes after Windows starts for ...