locked
DPM Server Version and Agents Incorrect RRS feed

  • Question

  • We have installed the March 2011 update (KB2465832) and although the install completes successfully and the version of the DPM server is now 3.0.7707.0 we have a couple of odd problems

    1. The DPM Server Agent is reporting it is more recent that the server, the recommended action is to upgrade the server to 3.0.7707.0 or install the latest agent which it already is but when i try and run the latest agent install i cant because it fails telling me it is the DPM server.

    "The agent operation failed because DPM detected a more recent version of the DPM protection agent (version 3.0.7707.0) on server.domain. (ID 372)"

     

    2. Any updates available only seem to push agent version 3.0.7706.0 rather than 3.0.7707.0, the latest agent installs are in the C:\Program Files\Microsoft DPM\DPM\agents\RA folder but they are not pushed by the DPM server.  Also if i manually install 3.0.7707.0 to a client DPM then reports backups will fail because the agents is more recent than the server.

     

    So currently we are running the older agents however i am evaulating client protection and unfortunately can only install 3.0.7706.0 which wont allow me to do a recovery without being a local admin.  Has anyone seen this problem before?

     

    Saturday, November 19, 2011 8:43 AM

Answers

  • Hi,

    We have seen this just a couple of times where the patch did not update the sql tables.

    Attached is a SQL script to add the missing AM_AgentPatch entries.

     

    1)      Make a backup of the DPMDB  (dpmbackup –db)

    2)      Open Sql Server management studio and connect to the MSDPM2010 instance

    3)      Click on the new query button.

    4)      Paste in the contents of the SQL Script below.

    5)      Execute the query – then verify you have the two new table entries.

    6)      Go in DPM GUI, refresh the agents under the agents tab and see if things are better.

     

    use dpmdb
    insert into dbo.tbl_AM_AgentPatch
    values ('27CD4BD7-C41D-4A7B-B814-38839AB1FAEC','DC39E868-894B-4B76-9FE8-266E3C76F8FF',N'DPM RA Update v3.0.7707.0','1','3','0','7707','0',N'Agents\RA\3.0.7707.0\i386\1033','DPMProtectionAgent_KB2465832.msp',N'REBOOT=ReallySupress INSTALLDPMFILTER=0')
    
    insert into dbo.tbl_AM_AgentPatch
    values ('27CD4BD7-C41D-4A7B-B814-38839AB1FAEC','DC39E868-894B-4B76-9FE8-266E3C76F8FF',N'DPM RA Update v3.0.7707.0','2','3','0','7707','0',N'Agents\RA\3.0.7707.0\amd64\1033','DPMProtectionAgent_KB2465832.msp',N'REBOOT=ReallySupress INSTALLDPMFILTER=0')
    
    Select * from dbo.tbl_AM_AgentPatch

     

     

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, November 19, 2011 3:29 PM

All replies

  • Hi,

    We have seen this just a couple of times where the patch did not update the sql tables.

    Attached is a SQL script to add the missing AM_AgentPatch entries.

     

    1)      Make a backup of the DPMDB  (dpmbackup –db)

    2)      Open Sql Server management studio and connect to the MSDPM2010 instance

    3)      Click on the new query button.

    4)      Paste in the contents of the SQL Script below.

    5)      Execute the query – then verify you have the two new table entries.

    6)      Go in DPM GUI, refresh the agents under the agents tab and see if things are better.

     

    use dpmdb
    insert into dbo.tbl_AM_AgentPatch
    values ('27CD4BD7-C41D-4A7B-B814-38839AB1FAEC','DC39E868-894B-4B76-9FE8-266E3C76F8FF',N'DPM RA Update v3.0.7707.0','1','3','0','7707','0',N'Agents\RA\3.0.7707.0\i386\1033','DPMProtectionAgent_KB2465832.msp',N'REBOOT=ReallySupress INSTALLDPMFILTER=0')
    
    insert into dbo.tbl_AM_AgentPatch
    values ('27CD4BD7-C41D-4A7B-B814-38839AB1FAEC','DC39E868-894B-4B76-9FE8-266E3C76F8FF',N'DPM RA Update v3.0.7707.0','2','3','0','7707','0',N'Agents\RA\3.0.7707.0\amd64\1033','DPMProtectionAgent_KB2465832.msp',N'REBOOT=ReallySupress INSTALLDPMFILTER=0')
    
    Select * from dbo.tbl_AM_AgentPatch

     

     

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, November 19, 2011 3:29 PM
  • Mike that solution worked a treat, very bizzare that this happened but so far i have pushed the latest client (3.0.7707.0) and the user recovery option now works.

    Many thanks

    Monday, November 21, 2011 1:06 PM