Re: Error 22039 trying to add SQL 2K to AD

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



1. Services run under security credentials. SQL Server runs
as a service. You assign a login for this service to run
under. You can view the account being used by SQL Server to
run under Services. Look at the LogOn tab when view the SQL
Server service and it will tell you what SQL Server runs
under.
2. That applied to one of your threads where you indicated
the service wasn't installing.
3. There are probably knowledge base articles on it. Search
the Knowledge base for SQL Server only and the exact phrase
domain controller. There are a lot of security issues as
well if you are installing SQL Server on a domain
controller.
4. Look for the books online topics:
Active Directory Integration
MSSQLServerADHelper Service

-Sue

On Wed, 5 Oct 2005 11:38:01 -0500, "Sydney Lotterby"
<sydney@xxxxxxxxxxxxxx> wrote:

>Sue,
>Thanks for your response.
>1) "permissions that matter but rather the permissions of the SQL Server
>service account. " - Not sure how to answer this b/c I use Windows domain
>login for connection. I use Administrator for this and have full access
>rights.
>
>2) "Sqlstp.log and Setup.log" - my programmer checked these and said all
>was OK.
>
>3) "There are issues with xpadsi.exe on domain controllers" - what kinds of
>issues? where can I read about them.
>
>4) What do I lose by not having SQL server registered with AD?
>
>"Sue Hoegemeier" <Sue_H@xxxxxxxxxxxxx> wrote in message
>news:hm51k112bk39ehbv0ih16bu3j9riufkgcv@xxxxxxxxxx
>> With your posts it's hard to tell if you have two different
>> issue or just one. If the service is not installing, that
>> would be one issue.
>> If the service is installed, on the permissions side it's
>> not your permissions that matter but rather the permissions
>> of the SQL Server service account.
>> Make sure xpadsi.exe is in the correct folder.
>> There are issues with xpadsi.exe on domain controllers.
>> If you uninstalled and reinstalled, did you check the setup
>> logs - Sqlstp.log and Setup.log
>>
>> -Sue
>>
>> On Sun, 2 Oct 2005 20:55:54 -0500, "Sydney Lotterby"
>> <sydney@xxxxxxxxxxxxxx> wrote:
>>
>>>I upgraded SQL 2000 to sp4, tried to add registration to Active Directory
>>>and get the following:
>>>
>>>SQL Server Enterprise Manager could not add server '....' to Active
>>>Directory.
>>>Error 22039: xpadsi.exe failed
>>>
>>>Any suggestions?
>>>
>>>btw I am logged in as Administrator on the srever itself and have Full
>>>Rights.
>>>
>>
>

.



Relevant Pages

  • Re: Execute Persmission denied on object sp_OACreate
    ... If so what access and permissions. ... The account is a windows account. ... One method to test permissions is to log in to your SQL Server box using the ... >>> SA account password and gaining access to the database. ...
    (microsoft.public.sqlserver.security)
  • Re: Specifying a logon account for SQL Server 2005 services
    ... As I mentioned using a Windows domain account with no permissions is the ... configured only for very specific server and memory configurations. ... account to use while installing SQL Server, will SQL Server give this account ...
    (microsoft.public.sqlserver.security)
  • Re: simple security question (need refresher)
    ... If IIS is configured for anonymous access and you connect to SQL Server ... using Windows authentication, the IIS anonymous account ... this account or roles that this account is a member of. ... Permissions are required only on objects directly accessed by the ...
    (microsoft.public.sqlserver.security)
  • Re: "Access denied" with xp_cmdshell (!)
    ... But problem is that I have tried to give for that account full control ... restart Sql Server for those permissions to take effect. ...
    (microsoft.public.sqlserver.security)
  • Re: MSDE Service permissions
    ... remove it from the users group and use it for the service ... LocalSystem account, created just for this purpose and never use an actual ... You can create this account before you begin installing SQL ... or you can change the account under which SQL Server runs at a later ...
    (microsoft.public.sqlserver.msde)