Error 0x80070534 when changing service account

[Alex Luna]

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
Alex

[Sue Hoegemeier]

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
Domain\ServiceAcctName)

-Sue

[Alex Luna]

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?

Alex

[Sue Hoegemeier]

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.

-Sue

On Wed, 14 Feb 2007 06:19:03 -0800, Alex Luna

[Alex Luna]

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.

-Alex

[Sue Hoegemeier]

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
incorrect.

-Sue

On Thu, 22 Feb 2007 13:02:47 -0800, Alex Luna

[Alex Luna]

Sue

If I use the prefix, I got error 0x80070534, if I don't use the prefix I got
the error 0x80070056, incorrect network password, but I'm sure the password
is correct. Something similar happens when I use RUN AS command (or screen)
on the DC, if I type the user with domain prefix, it starts the app as that
user (the same I want SQL services start with), but if I don't use the prefix
at RUN AS window or command, the password error appears. Maybe, I have a
misconfiguration at domain level...???

Thank you for your help
-Alex

[Sue Hoegemeier]

Hi Alex,
Managing this on a domain controller can be a pain. The
permissions don't always get set correctly due to security
issues - it's a different risk when you install SQL Server
on a domain controller.
You'll need to start by walking through all the permissions
for the service account. The following link is probably the
best resource on this:
http://support.microsoft.com/?id=283811

-Sue

On Mon, 26 Feb 2007 08:11:08 -0800, Alex Luna

[Mohammad Aziz]

The only solution that I have been able to find for this error is to RDP into the SQL Server using the new Service account you want the SQL server to run under.
Then go into the sql server configuration manager and change the SQl server service account and restart the service.
Also you might want to make this service account a local admin on the server

>> On Tuesday, February 13, 2007 11:45 PM 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
>> Domain\ServiceAcctName)
>>
>> -Sue
>>

>> On Tue, 13 Feb 2007 15:35:01 -0800, Alex Luna
>> <Alex...@discussions.microsoft.com> wrote:

>>> On Wednesday, February 14, 2007 9:19 AM AlexLun 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?
>>>
>>> Alex
>>>
>>> "Sue Hoegemeier" wrote:

>>>> On Thursday, February 15, 2007 10:47 PM 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.
>>>>
>>>> -Sue
>>>>

>>>> On Wed, 14 Feb 2007 06:19:03 -0800, Alex Luna
>>>> <Alex...@discussions.microsoft.com> wrote:

>>>>> On Thursday, February 22, 2007 4:02 PM AlexLun 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.
>>>>>
>>>>> -Alex
>>>>>
>>>>> "Sue Hoegemeier" wrote:

>>>>>> On Sunday, February 25, 2007 4:49 PM Sue Hoegemeier wrote:

>>>>>> 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
>>>>>> incorrect.
>>>>>>
>>>>>> -Sue
>>>>>>
>>>>>> On Thu, 22 Feb 2007 13:02:47 -0800, Alex Luna
>>>>>> <Alex...@discussions.microsoft.com> wrote:

>>>>>>> On Monday, February 26, 2007 11:11 AM AlexLun wrote:

>>>>>>> Sue
>>>>>>>
>>>>>>> If I use the prefix, I got error 0x80070534, if I don't use the prefix I got
>>>>>>> the error 0x80070056, incorrect network password, but I'm sure the password
>>>>>>> is correct. Something similar happens when I use RUN AS command (or screen)
>>>>>>> on the DC, if I type the user with domain prefix, it starts the app as that
>>>>>>> user (the same I want SQL services start with), but if I don't use the prefix
>>>>>>> at RUN AS window or command, the password error appears. Maybe, I have a
>>>>>>> misconfiguration at domain level...???
>>>>>>>
>>>>>>> Thank you for your help
>>>>>>> -Alex
>>>>>>>
>>>>>>> "Sue Hoegemeier" wrote:

[rpal...@gmail.com]

среда, 14 февраля 2007 г., 1:35:01 UTC+2 пользователь Alex Luna написал:

I had the same issue. The problem was with domain account. It was configure only for list of computers to log on.I add my SQL-computer to list and it's resolve the problem.