Solved

SQL connection failing after changing windows built in domain administrators account

Posted on 2011-02-14
7
507 Views
Last Modified: 2012-05-11
I disabled the built in domain administrator account in Active directory and now users cannot connect to a very important the SQL server application.  The application tries to establish a server connection on port 38113 and fails.  When I run the application locally on the server it fails with the error:
"socket connection failed (error code 10061)"
If I re-enable the ID and reboot the server, it works again...If I then disable the ID after that reboot, it continues to work untill the server is rebooted again, then it stops working.  I suspect a connection string needs to be modified somewhere but I don't know where and how to change it.
0
Comment
Question by:lanreo
  • 4
  • 3
7 Comments
 
LVL 7

Expert Comment

by:lundnak
ID: 34892145
What userid are your SQL Server services configured to run under?
0
 

Author Comment

by:lanreo
ID: 34893397
MSSQLSERVER, MSSQLServerADHelper and SQLSERVERAGENT are all running under the Local System Account
0
 
LVL 7

Accepted Solution

by:
lundnak earned 500 total points
ID: 34896737
Local system gets its privileges from BuiltIn\Administrators.  I would recommend creating domain user to run the services as.

Following the steps in this blog.

http://www.sqldbadiaries.com/2011/02/02/restirct-access-to-local-system-administrators-on-sql-server/
0
Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 

Author Comment

by:lanreo
ID: 34898195
I've done all the steps in the blog above except removing the "Builtin\Administrators" group from Systems admin role in SQL, I even rebooted the server and I still have the same problem, the client application still does not connect.  I have a feeling there's a file somewhere on the server where it's hardcoded to use a certain "domain\userid" to connect.....please help !!!
0
 

Author Comment

by:lanreo
ID: 34898586
I figured out the problem; the SQL client application was running under a service account that was using the disabled ID....I changed that ID and all worked fine, thanks for your help all the same ..
0
 
LVL 7

Expert Comment

by:lundnak
ID: 34899587
Good deal.  I didn't think about checking the client settings.
0
 

Author Closing Comment

by:lanreo
ID: 34925273
The hints you gave me led to my finding the solution for my issue
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes some very basic things about SQL Server filegroups.
This article explains all about SQL Server Piecemeal Restore with examples in step by step manner.
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

867 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now