Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server Active Directory Helper Service Expand / Collapse
Author
Message
Posted Friday, December 28, 2007 4:15 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, July 21, 2014 9:10 AM
Points: 88, Visits: 178
I tried to start SQL Server Active Directory Helper on

- A Win 2003 Server that is a Primary Domain Controller (Virtual Machine)
- A Win XP SP2 (virtual) machine that is joined to the active directory.

An error was displayed referring to the following 'service-specific error code': -1073741724.

Any idea what this means?
Post #436979
Posted Wednesday, December 24, 2008 12:41 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, May 9, 2009 12:58 AM
Points: 1, Visits: 2
Even I am having the same problem.

Post #625214
Posted Thursday, January 8, 2009 5:02 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 8, 2009 11:58 PM
Points: 2, Visits: 3
i m also having a same problem

what is the solution
Post #632259
Posted Thursday, January 8, 2009 5:48 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, July 25, 2010 9:38 PM
Points: 107, Visits: 264
The Active Directory Helper won't start manually. By default the service is Disabled. The SQL Server Database Engine handles the use of this service.

It publishes SQL Server information in Active Directory. If you don't need to publish SQL Server information in your Active Directory domain, then set the service to Disabled. If you do, set it to Manual and let SQL Server manage it.

The SQL Server installation sets the user account to NT AUTHORITY\NETWORK SERVICE. This will pass the computer name as the credential to Active Directory. Another often used user account is NT AUTHORITY\LOCAL SYSTEM. Following the principal of least privilege, it is best to create a new service account dedicated to the Active Directory Helper service. Domain Users is the only group membership it needs. If you use Group Policy to configure the Log On As A Service privilege then you will need to add this service account to your GPO. If this doesn't apply, then simply setting the user in Services will grant the privilege on your behalf.



--
Andrew Hatfield
Post #632285
Posted Friday, January 9, 2009 7:20 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 7:32 PM
Points: 1,669, Visits: 2,211
Andrew,

Can you explain what reasons would be good reasons to choose to publish SQL Server info to AD? I'm relatively new to the administrative pieces of SQL Server, and would like some background on this topic ... It also would be useful for me to know how the answer to the above question applies in a home network scenario, and specifically where one has a website that has financial data on said SQL Server, where I'd be restricting access to specific authenticated users. Could such publication be more of a risk than a helpful thing?

Steve
(aka smunson)
:):):)


Steve
(aka sgmunson)

Internet ATM Machine
Post #633371
Posted Friday, January 9, 2009 8:28 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, July 21, 2014 9:10 AM
Points: 88, Visits: 178
smunson (1/9/2009)
Andrew,

Can you explain what reasons would be good reasons to choose to publish SQL Server info to AD? I'm relatively new to the administrative pieces of SQL Server, and would like some background on this topic ... It also would be useful for me to know how the answer to the above question applies in a home network scenario, and specifically where one has a website that has financial data on said SQL Server, where I'd be restricting access to specific authenticated users. Could such publication be more of a risk than a helpful thing?

Steve
(aka smunson)
:):):)


I see your point, perhaps a useful scenario (lacking background knowledge on SQL Server) would be that I might need to retrieve personal information of employees into the Active Directory Domain, using procedural scripts. Assuming this can be done it would be helpful in this case.
Post #633481
Posted Friday, January 9, 2009 5:09 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, July 25, 2010 9:38 PM
Points: 107, Visits: 264
Publishing SQL Server information to Active Directory is only of any use if you have client applications that query Active Directory for such information.

When you publish SQL Server to AD, it publishes the SQL Instance and databases. One way that I could see this being useful is that you wouldn't need to configure your application connection settings. It can query LDAP://RootDSE to get your local domain information and then ask AD to give it a list of SQL Instances and databases.

I haven't yet seen an application that takes advantage of this feature. I would imagine that SQL Server creates an Application Partition within your Active Directory schema similar to DNS.

There is some further information here
http://www.sqlmag.com/Article/ArticleID/41841/41841.html
http://msdn.microsoft.com/en-us/library/aa174517(SQL.80).aspx



--
Andrew Hatfield
Post #634009
Posted Friday, January 9, 2009 5:14 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, July 25, 2010 9:38 PM
Points: 107, Visits: 264
smunson (1/9/2009)

It also would be useful for me to know how the answer to the above question applies in a home network scenario, and specifically where one has a website that has financial data on said SQL Server, where I'd be restricting access to specific authenticated users. Could such publication be more of a risk than a helpful thing?

Steve
(aka smunson)
:):):)


I can't see that it would add any value in your situation. Horse for courses though



--
Andrew Hatfield
Post #634012
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse