Re: Error 0x80070534 when changing service account

Which same error? One error you are getting due to running
SQL Server on a domain controller is using the domain
prefix. When you removed the prefix, the error was:
"The specified network password is not correct."
Which means the password you used for the account was


On Thu, 22 Feb 2007 13:02:47 -0800, Alex Luna
<AlexLuna@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Thank you Sue, but still got the same error at Configuration Manager.

The account has granted Logon as Service right in the domain and in Domain
Controllers. I had set the same permissions for that account in both SQL
Server. The only difference I see is that the SQL Server where the account is
able to start the service is not a domain controller, and the other SQL
Server it is.


"Sue Hoegemeier" wrote:

When you create a new account, make sure to set the correct
settings for the service account. Then add the account to
the sysadmins server role in SQL Server. Then change the
service account using the Configuration Manager.


On Wed, 14 Feb 2007 06:19:03 -0800, Alex Luna
<AlexLuna@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hello Sue,

Thank you or your help. If I try using the account name without domain name
prefix, an error 0x80070056 "The specified network password is not correct."
shows up.

I also tried to use another domain account as service account and error
0x80070534 appears. I added the desired service account to domain admin group
and still got the same error. So, only with admin user account I'm able to
start SQL Server.

Any suggestions?


"Sue Hoegemeier" wrote:

You can get the error when the account can't be mapped to
the correct SID - did you try another account? With the DC
issue, you may also want to try without the domain prefix -
along the lines of ServiceAcctName (instead of


On Tue, 13 Feb 2007 15:35:01 -0800, Alex Luna
<AlexLuna@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi people
I'm trying to change the SQL Server service account to a domain account and
got error 0x80070534. I explain a little...
I have three servers, a DC, another DC with SQL Server installed and a
member server with SQL Server installed.
In the member server I wasable to successfully change the SQL Server service
account (and for other SQL services also), so the doman user has needed
privileges in domain and in member server files.
In the second DC, I installed SQ Server prior to promote it to DC. In this
server, if I use domain administrator account to start SQL Server, it starts
without problem. But I want to make it start with same domain account the
other SQL Server starts. So I try to assign the service account using SQL
Configuration Manager and error 0x80070534 "No mapping between account names
and security IDs was done" appears.
Any help will be geatly appreaciated.
Thank you


Relevant Pages

  • Re: 2005 Enterprise sp 2 install fails - 11009
    ... Q...Was your SQL Server service account a domain administrator account? ...
  • Re: Error 0x80070534 when changing service account
    ... Managing this on a domain controller can be a pain. ... issues - it's a different risk when you install SQL Server ... If I use the prefix, I got error 0x80070534, if I don't use the prefix I got ... Which means the password you used for the account was ...
  • Re: SQL windows account
    ... > Can the account to run SQL server belong to USER group or ... >>SQL Service account absoloutely does NOT have ... >>Jasper Smith (SQL Server MVP) ... >>> I happened to be a box and DB admin and i have a local ...
  • Re: Error 15401 using sp_grantlogin (not addressed by current KB articles)
    ... Restarting Windows 2000 resolved the problem for this particular account, ... confused when it sees a duplicate SID. ... > One way to get SQL Server to agree with the renamed NT ... > Preview (to ensure the script was created), ...
  • Re: SharePoint V3 Install Error
    ... But it our case it had to do with Group Policies that forbid the account of ... WSS ... Event Source: WindowsSharePointServices3Search ... whatever you are installing WSS as sufficient rights to the SQL Server ...