Windows 7 - Agent not reachable (on ALL protected servers)

Asked By jo

23-Oct-07 05:08 PM

Hello again!  DPM was working without a hitch for me (RC0) for a couple
weeks.  Now, suddenly, the management \ agents section reports "Error" on the
agent status for every protected and unprotected server in my organization.

What I've done:
1. Verified no firewall is blocking connectivity between DPM server and
protected server
2. Verified that DPMRA is running on protected servers (and attempted to
restart the service)
3. Verified that protected servers can talk to DPM and vice versa
(connectivity via ping, SQL browser, file shares, etc.)
4. Verified state of domain on DPM and protected servers (dcdiag / netdiag)
5. Restarted DPM Server

Nothing's helping.

Protected servers report (every 30 Min):
Event Type:	Error
Event Source:	DPMRA
Event Category:	None
Event ID:	83
Date:		10/23/2007
Time:		4:44:44 PM
User:		NT AUTHORITY\SYSTEM
Computer:	ACI-MDC-1
Description:
A DPM agent failed to communicate with the DPM service on MYDPM because the
host is unreachable. Make sure that MYDPM is online and remotely accessible
from the computer running the DPM agent. If a firewall is enabled on MYDPM,
make sure that it is not blocking requests from the computer running the DPM
agent (Error code: 0x800706ba, full name: MYDPM).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

DPM Server reports all kinds of errors, mostly ID 3159's (failed to
communicate with the protection agent on MYSERVER because the agent is not
responding. (ID 43)

Management \ Agents reports "Error" under agent status for all agents

Monitoring \ Alerts reports "Agent Not Reachable" for all servers with the
following message:

The DPM protection agent on MYSERVER could not be contacted.  Subsequent
protection activities for the computer may fail if the connection is not
established.  The attempted contact failed for the following reason: (ID 3122)
The protection agent operation on MYSERVER failed because the service did
not respond (ID 316 Details: Internal error code: 0x8099090E)

Any ideas on this one?  All services on DPM that should be started appear to
be started and working properly.

23-Oct-07 05:16 PM

worth mentioning too:
If I shutdown a protected server, and refresh the information in Management
\ Agents, it shows up as "Unavailable" instead of "Error", so it looks like
there is at least connectivity to the servers...

25-Oct-07 12:43 AM

Hi,

If this error happens for every production server, then there is
configuration changes on the DPM server side.This error occurs when
production server is unable to talk to DPM server. Make sure that production
server is pinging to the right IP address of FQDN DPM Server.

On Production server ping <FQDN DPM server>
On DPM server ping <FQDN DPM server>

Both should resolve to same IP address. If not, there is issue with network
settings.

Thanks,
krisnaru

--
This posting is provided "AS IS" with no warranties, and confers no rights.

25-Oct-07 09:36 AM

Right, I've already:
Verified that protected servers can talk to DPM and vice versa

I can RDP there, I can access UNC shares, ping each way, etc.

The issue just kind of went away on its own, but it left me unprotected for
2.5 days...

It's working now.

16-Nov-07 12:01 PM

We are having the same problem here as well.. no luck in any fixes ...

08-Jan-08 08:19 PM

try re-reg the agent on the dpm client computer using <drive letter>:\Program
Files\Microsoft Data Protection Manager\bin SetDpmServer.exe -dpmservername

15-Jan-08 04:33 AM

I have the same Problem with DPM 2006. There is no "setDpmServer.exe" on my
DPM-Client. Do You have an other idea?

thank you
Michael (hannover)

15-Feb-08 08:51 AM

Thanks Luke, it appears that this may have fixed my problem.  Client has been
running for about 36 hours straight since I ran SetDPMServer.  And I have
since run it on two others that dropped.