DPM 2012 : Troubleshooting error 999 in event viewer

November 15, 2012 at 11:37 am in Data Protection Manager, dpm, DPM 2012 by Kenny Buntinx [MVP]

 

Hi All,

Our DPM2012 CU3  has been working pretty well for us , but this morning I came in the office and tried to open the DPM2012 console but received this error:

—————————————

The description for Event ID 999 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unexpected error caused a failure for process ‘DPMAMService’.  Restart the DPM process ‘DPMAMService’.

—————————————-

Step 1 :  Verify that the following related DPM services are running :

  • SQL Server –> Make sure they run with .\MICROSOFT$DPM$Acct
  • SQL Server Agent –> Make sure they run with .\MICROSOFT$DPM$Acct
  • SQL server Browser
  • DPMAMService –> DPM AccessManager Service
  • DpmWriter –> DPM Writer Service

The DPM service was dependent on the SQL Server and SQL Server Agent services. I have gone to the Services and all services are running except one called “DPMAMService” .

I get this error message when trying to run it :

——————————

The DPM AccessManager Service service terminated unexpectedly.  It has done this 2 time(s).  The following corrective action will be taken in 100 milliseconds: Restart the service.

——————————

Step 2 :  Verify that the related DPM services have enough time to start:

When a service starts, the service communicates to the Service Control Manager how long the service must have to start (the time-out period for the service). If the Service Control Manager does not receive a "service started" notice from the service within this time-out period, the Service Control Manager terminates the process that hosts the service. This time-out period is typically less than 30 seconds (30000 miliseconds). If you do not adjust this time-out period, the Service Control Manager ends the process.Adjust this time-out period, follow these steps:

a.  In Registry Editor, locate, and then right-click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control 

b.  Point to New , and then click DWORD Value.
c.  Enter:  ServicesPipeTimeout  and then press ENTER. 
d.  Right-click the ServicesPipeTimeout registry entry that you created in step c, and then click Modify . The Edit DWORD Value dialog box appears. 
e.  In the Value data text box, type TimeoutPeriod , and then click OK

Note TimeoutPeriod is a placeholder for the value of the time-out period (in milliseconds) that you want to set for the service. For example, if you want to set the time-out period to be 5 minutes (300000 milliseconds), type 300000. 
f.  Restart the computer. You must restart the computer for Service Control Manager to apply this change. 

Step 3 :  Verify that the related “.\MICROSOFT$DPM$Acct” has the “Log on as a service right“:

After checking it on the local security policy , I noticed that the related “.\MICROSOFT$DPM$Acct” was not part of the “Log on as a service right“. You should grant the Log on as a service right to this account and it will be OK again. But do not ask me why did this right disappeared. ( I am investigating if a GPO would do the hostile take-over Smile  ) . I rebooted the server , just in case !

Step 4 : On the DPM server , open the DPM Management shell  and run dpmsync:

I had also to open the DPM management shell and use command “dpmsync –sync” and after that  the DPM console started well.

Conclusion:

I know all of the above steps are maybe not necessary . However as I cannot find a lot of information on the internet , I posted these steps for verification and it might help you to solve your problem .The Product team should really do something about the “How to Troubleshoot DPM issues” .

Hope it Helps ,

Kenny Buntinx

Tweet about this on TwitterShare on FacebookShare on Google+Share on LinkedInPin on Pinterest