Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Synchronisation jobs fail with errorcode: 0x809909B0

1,381 views
Skip to first unread message

Marco van den Berge

unread,
Apr 29, 2009, 8:30:19 AM4/29/09
to
Hi All,

We are using DPM for a few months now and recently all the sync-jobs are
failing on me with the following error code;

The protection agent on dpm01.domain.local was temporarily unable to respond
because it was in an unexpected state. (ID 60 Details: Internal error code:
0x809909B0)

Our DPM server is a Windows 2003 Enterprise server (32bit) with 8GB ram,
ther shouldn;t be any resource problems.
I did check if all the services where running and i installed the latest
hotfix; KB968579.
After this i restarted all our servers (including DPM) And still i recieved
all failures.

at this point i am not sure what the problem might be so if someone could
give any advice, that would be much appreciated!

Thanks in advace!

IT Staff

unread,
Apr 30, 2009, 6:11:56 AM4/30/09
to
What is the protection agent protecting ? Vista ?


Marco van den Berge

unread,
May 1, 2009, 3:06:03 AM5/1/09
to
it's protecting our servers.
2x Windows 2003 x32
1x windows 2003 x64 (also exchange 2007)
2x windows 2008 x32

Praveen T [MSFT]

unread,
May 3, 2009, 8:31:51 PM5/3/09
to
please check the eventlogs on dpmserver & productionserver, you might find
evidence for agent crash (dpmra terminated unexpectedly). If you can pass on
the stack trace for the crash, it will help in futher diagnosis.

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


"Marco van den Berge" <Marcovan...@discussions.microsoft.com> wrote in
message news:BC3CF3B5-A1F4-4C6E...@microsoft.com...

sascha a.

unread,
May 12, 2009, 8:19:03 AM5/12/09
to
Check this:

Subject: RE: Agent Not Reachable 3/6/2009 4:12 AM PST
By: sascha a. In: microsoft.public.dataprotectionmanager

Trye the http://support.microsoft.com/?kbid=950224 fix. Before we've
installed the fix, we've had a lot of "agent not reachable" errors. After
this kb-fix, only agents they are realy offline/unreachable are logged in the
error-tab.


"Chad Bailey" wrote:

> I have a primary DPM backup server on my local network. We also have a
> secondary DPM server (which acts as failover for the primary) at an
> offsite data center connected via 10MB link.
>
> This secondary server constantly has issues with jobs not completing due
> to "Agent Not Reachable". It doesn't have a problem with all computers,
> just a few. If I go to the management tab > agents, and take a look at
> the agent status, it shows ok. It seems to only be a problem during the
> actual backup phase.
>
> The primary server on the local LAN has no problem at all backing up
> these same server.
>
> Any thoughts or troubleshooting suggestions?
>
> Thanks.
> Chad

0 new messages