none
microsoft$dpm$acct - The service did not start due to a logon failure RRS feed

  • Question

  • DPM 2010 failed to start after a reboot. When I tried to start the various DPM services the MSDPM2010 would not start. The password has not been changed.

    The event log says to grant the Log on as service right, but when I go there it is grayed out.

    This DPM server is a member of an EBS domain so I suppose some group policy has gotten out of hand.

     I would be OK with running as LocalSystem on this server if it would solve the problem and not create any others.

    Kal

      From the System Event Log:

    Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.

     If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.

    Wednesday, September 22, 2010 7:06 AM

Answers

  • Mike,

    I did not have success with your link, but this one helped me: http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/059465f4-a35b-4172-820c-f0c1e0a44d08 (near the bottom of the thread is a nice summary).

    It is about changing permissions for passwords, but just selct the Log on as a service line to edit and everything else is pretty much the same. It turns out that DPM (or at least mine) has  gpmc.msc. So DPM is running again.

    I am still wondering about MS$DPM2007$ though? Any reason to leave it running?

    Group policies are no doubt very helpful when you have a lot of computers to manage, and/or enough time to learn each necessary detail. But for those of us with a day job and a life there is a whole lot to learn.

    Kal

     

    Thursday, September 23, 2010 3:14 AM

All replies

  • It won't work I'm afraid as a local service.  Also, it are not the DPM services that need to run as the dpm$acct account, but the SQL services.  So my advice would be to fix this in your group policy.

    You can use the steps as described here to do this: http://uksbsguy.com/blogs/ianwatkins/archive/2007/02/17/enabling-log-on-as-a-service-for-a-local-user.aspx

    Hope it helps,

    Cheers,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Wednesday, September 22, 2010 8:01 AM
    Moderator
  • Mike,

    I will try your link, painful though these things are.

    But it is not clear to me why the SQL part will not work as a local service. It worked fine in 2007 as that DB is still running right next to the one that will not start.

    But that brings up a question, any reason to leave that running? I did not see it before. As I recall, I uninstalled and started over with 2010.

    Kal

     

    Wednesday, September 22, 2010 2:52 PM
  • Mike,

    I did not have success with your link, but this one helped me: http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/059465f4-a35b-4172-820c-f0c1e0a44d08 (near the bottom of the thread is a nice summary).

    It is about changing permissions for passwords, but just selct the Log on as a service line to edit and everything else is pretty much the same. It turns out that DPM (or at least mine) has  gpmc.msc. So DPM is running again.

    I am still wondering about MS$DPM2007$ though? Any reason to leave it running?

    Group policies are no doubt very helpful when you have a lot of computers to manage, and/or enough time to learn each necessary detail. But for those of us with a day job and a life there is a whole lot to learn.

    Kal

     

    Thursday, September 23, 2010 3:14 AM