Is missing or corrupted for some reason then you can expect to see the following errors listed below. Once done make sure the DPM reg key is present.ĭPM Server Missing the Member Server Reg key Please reference the resource link below. This being done taking care to use the proper syntax and correct thumbprint. Once done, rerun the Set-DPMCredentials command to recreate that key. : In this case to where the registry key is missing for the DPM Server itself on the DPM Server, the following needs to be done.ġ.) Restore the key via registry backup, if no backup is available for this key and\or you do not feel comfortable with this measure then proceed to the next step.Ģ.) Verify that a valid certificate is in place on the DPM server. WARNING CCommandProcessor::SendOutboundCommandUsingCertificate failed for Server: Ĭ2797F36-E616-4D5C-AC68-D9DA2216CE2D WARNING , hrOriginal = 0x80990940, No further retry You may get one if not all of the alerts listed below. If the DPM registry key is missing then a consistency check and\or a recovery point on a protected datasource using certificate authentication will fail with the following errors. The crash log name itself will be such as: DPMCPWrapperServiceCurr.errlog._19-25-50 You would also see a crash log generated in the following directory: C:\Program Files\Microsoft System Center 2012\DPM\DPM\Temp directory (There is a list of the common causes for this error discussed in Part 3 of this series.) If this DPM registry key is missing then you may also see the DPM CPWrapper service in a “starting” state if not then a restart of this service may fail when attempting to bind the service with that missing registry key. In this case the related registry keys that bind to that service. Indicates an issue with the DPM CPWrapper Service. Remember this error was produced by removing the DPM certificate registry key. HKLM\Software\Microsoft\MicrosoftTDataProtectionManager\Agent\2.0\Certificates\Īlthough this error suggests to check the CPWrapper service on the member server, which is not a bad idea, the issue in this case is with the DPM server itself. Itself is missing or deleted for some reason then you can expect the following error in the DPM GUI: In this example we will look at the errors in the:Īfter the Set-DPMCredentail command is run, if the registry key The default location is HKLM\Software\Microsoft\MicrosoftTDataProtectionManager\Agent\2.0\Certificates\ or ĭPM Server Missing DPM cert reg key (its’ own reg key) Missing Member server cert reg key (it’s own key)Īfter running both the SetDPMserver command on the member server or the Attach-ProductionServerWithCertificate command on the DPM server, registry entries are placed on the servers to associate the certificate with the DPM server and the protected server. When troubleshooting DPM certificate based authentication:Ī.)Check the registry keys on both the DPM server and protected server. This is so important that it warrants repeating. In the scenarios below, after I would remove a reg key or cert, in order to get things back into a working state I would have to repeat those steps. This troubleshooting theme should be strictly adhered to during your certificate based authentication troubleshooting. : “Certs check, registry check, DPMCPWrapperService restart check. In this next section we will go over what errors you can expect to see when either the certificates or the registry keys are missing. When you have everything setup and working, the certs are in the right store and the proper command syntax has been used, there are specific registry entries placed on both the DPM server and the member server being protected. We are going to jump right in and look at a few failed scenarios when your DPM certificate related registry keys are missing or corrupt. This article picks up from whereĭPM Certificate Troubleshooting–Part 1: General Troubleshooting
First published on TECHNET on Jul 24, 2012
0 kommentar(er)
