Change service logon account

  • I am trying to change SQL server agent account in my developer machine from local system to my own user name. (this is for a test)

    I tried to change it in SQL server configuration manager as in the image.

    I used the browse button and search my username in our domain instead of typing it.

    But it gives the error: The specified network password is not correct

    Why is that?

    Thanks

    P.S and I followed the correct way of doing this in article:

    http://www.sqldbadiaries.com/2010/12/13/change-service-account-password-the-specified-network-password-is-not-correct/

    But I still got the error.

  • Are you positive you are a member of the local administrators group on your machine?

    ______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

  • Yes, I am the administrator of the box.

    This is a windows 7 developer box

  • Hi,

    I read the article you referred to at http://www.sqldbadiaries.com/2010/12/13/change-service-account-password-the-specified-network-password-is-not-correct/.

    Can you confirm you selected "Entire Directory" for the location field as mentioned at the bottom of the article.

    The From this location field in the above screenshot was populated with the local server name. Then clicked on Locations button and selected Entire Directory in the next screen, so that it looks for the Login Name in the Active Directory.

    Then he entered the Login Name in the Enter the object name… field and clicked Ok. As earlier, the Account Name was populated with Domain\LoginName, the only difference was that the Service Control Manager will look it up in Entire Directory. Now the DBA entered the password and clicked Ok. No error message and the service started successfully.

    The SQL Guy @ blogspot[/url]

    @SeanPearceSQL

    About Me[/url]

  • Thanks,

    The link is the link I referred to on my first post.

    I did exactly the same thing, in fact, I just tried on another testing server the same process, I don't have that error.

    The difference is that is a server with standard edition sql server on a windows 2008 r2, on my own developer box, it is a developer edition with windows 7.

    I am not sure where it is wrong.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply