Communication Error With The Protection Agent. Id 53
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Microsoft System Center Home 2012 Previous Versions Library Forums Gallery We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. DPM 2010 Troubleshooting Guide DPM 2010 Error Codes DPM 2010 Error Codes (ID: 1 - ID: 99) DPM 2010 Error Codes (ID: 1 - ID: 99) Error ID: 53 Error ID: 53 Error ID: 53 Error ID: 7 Error ID: 1
DPM 2012R2 RU5. All three cluster nodes are connected to an iSCSI SAN using CSV volumes. Windows backup is installed on the cluster nodes and the DPM server. The Hyper-V role is also installed on the DPM server. The VMs have the current integration services installed and enabled. All of the Hyper-V hosts installed the DPM agent correctly and are backing up to the DPM server. When I add one of the virtual machines to a protection https://technet.microsoft.com/en-us/library/ff973587.aspx group, the first attempted replica fails with this error: "DPM failed to communicate with dpmserver.domain because of a communication error with the protection agent. (ID 53 Details: Not implemented (0x80000001))" It fails after just under two minutes with0 data transferred. I noticed that this alert says it is failing to communicate with the DPM server and not the http://www.networksteve.com/enterprise/topic.php/VM_replica_on_Hyper-V_cluster_host_fails_with_ID_53_not_implemen/?TopicId=72182&Posts=4 client agent. From there the DPM server continues to attempt consistency checks that fail with this error: "An unexpected error occurred while the job was running. (ID 104 Details: The RPC server is unavailable (0x800706BA))" It also fails after just under two minutes with0 data transferred. I have disabled all firewalls and that hasn't helped. If I watch the Hyper-V host, I can see a checkpoint get created for the VM and then the VM says "backing up". After the ~2 minutes it merges and deletes the checkpoint. I also watch process and TCP connections and don't see any failed attempts. I'm adding the VM to the protection group on the DPM server by choosing to modify the protection group. Then Iexpand the Hyper-V cluster, Hyper-V, and select the \online\VMName item. It modifies the protection group and says it's creating the initial replica which fails with the errors above. So, it looks like DPM is reaching in and checkpointing the VM, but it is not streaming it back to the DPM server.
Log in Join myITforum Community Country* United StatesAfghanistanAlbaniaAlgeriaAmerican SamoaAndorraAngolaAnguillaAntarcticaAntigua and BarbudaArgentinaArmeniaArubaAustraliaAustriaAzerbaijanBahamasBahrainBangladeshBarbadosBelarusBelgiumBelizeBeninBermudaBhutanBoliviaBosnia and communication error HerzegowinaBotswanaBouvet IslandBrazilBritish Indian Ocean TerritoryBrunei DarussalamBulgariaBurkina FasoBurundiCambodiaCameroonCanadaCape VerdeCayman IslandsCentral African RepublicChadChileChinaChristmas IslandCocos (Keeling) IslandsColombiaComorosCongoCongo, the Democratic Republic of theCook IslandsCosta RicaCote d'IvoireCroatia (Hrvatska)CubaCyprusCzech communication error with RepublicDenmarkDjiboutiDominicaDominican RepublicEast TimorEcuadorEgyptEl SalvadorEquatorial GuineaEritreaEstoniaEthiopiaFalkland Islands (Malvinas)Faroe IslandsFijiFinlandFranceFrance MetropolitanFrench GuianaFrench PolynesiaFrench Southern TerritoriesGabonGambiaGeorgiaGermanyGhanaGibraltarGreeceGreenlandGrenadaGuadeloupeGuamGuatemalaGuineaGuinea-BissauGuyanaHaitiHeard and Mc Donald IslandsHoly See (Vatican City State)HondurasHong KongHungaryIcelandIndiaIndonesiaIran (Islamic Republic of)IraqIrelandIsraelItalyJamaicaJapanJordanKazakhstanKenyaKiribatiKorea, Democratic People's Republic ofKorea, Republic ofKuwaitKyrgyzstanLao, People's Democratic RepublicLatviaLebanonLesothoLiberiaLibyan Arab JamahiriyaLiechtensteinLithuaniaLuxembourgMacauMacedonia, The Former Yugoslav Republic ofMadagascarMalawiMalaysiaMaldivesMaliMaltaMarshall IslandsMartiniqueMauritaniaMauritiusMayotteMexicoMicronesia, Federated States ofMoldova, Republic ofMonacoMongoliaMontserratMoroccoMozambiqueMyanmarNamibiaNauruNepalNetherlandsNetherlands AntillesNew CaledoniaNew ZealandNicaraguaNigerNigeriaNiueNorfolk IslandNorthern Mariana IslandsNorwayOmanPakistanPalauPanamaPapua New GuineaParaguayPeruPhilippinesPitcairnPolandPortugalPuerto RicoQatarReunionRomaniaRussian FederationRwandaSaint Kitts and NevisSaint LuciaSaint Vincent and the GrenadinesSamoaSan MarinoSao