Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
MTWiley
Starting Member
3 Posts |
 Posted - 2011-11-10 : 12:42:53
|
| 3 Seperate Servers running Windows Server 2008 and SQL Server 2008There's a primary DB server and 2 other servers that it log ships to that are for disaster recovery. When we restart any of those machines the SQL services will not start back up and fail due to a log in error. We reenter the login credentials exactly the same as before and the services will start(god only knows how long it took someone to figure that one out). It's nice that we've found a way to get the services started again, but this doesn't really sit well with me since one of the admins has to log into the database server enter the credentials and manually restart the services everytime a machine goes down for anything including windows updates. Does anyone have any experience with this issue or know of a possible cause for this problem? I've tried searching a bit online, but haven't been able to isolate the issue. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-11-10 : 13:23:47
|
| whats the credential used for configuring the service? is it added as a admin account in machine where server is installed? is the machine under a different domain? are there any policies applied on it which is checking and removing this account as its not one belonging to same domain as machine?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2011-11-10 : 15:48:14
|
| This could be due to some network component, like the NIC card, not having finished startup by the time SQL Server tries to start, so that you get a login failure.CODO ERGO SUM |
|
|
|
MTWiley
Starting Member
3 Posts |
Posted - 2011-11-10 : 19:16:40
|
quote:
This could be due to some network component, like the NIC card, not having finished startup by the time SQL Server tries to start, so that you get a login failure.
If that was the case when we tried to start it manually after we're able to RDP into the SQL server and it fails wouldn't that eliminate that as a possibility?quote:
Originally posted by visakh16
whats the credential used for configuring the service?
I'm not quite sure what you mean, are you asking what credentials am I using to change the logon as credentials for the service or are you asking what credentials is the service using?quote:
is it added as a admin account in machine where server is installed?
It's not a member of the local admins group on our main DB server, Local DR does have it as a member of the local admins group(This server is also a backup domain controller), and remote DR doesn't have it as a local admin. It is however a member of the Administrators, Domain Admins, Domain Users, and 2 other groups, but I don't see any policies that would be causing the problem. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-11-11 : 03:17:00
|
| I'm not quite sure what you mean, are you asking what credentials am I using to change the logon as credentials for the service or are you asking what credentials is the service using?I was asking on the credentials the service was using to logon. go to services.msc open service to see what account it uses------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
MTWiley
Starting Member
3 Posts |
Posted - 2011-11-11 : 12:58:51
|
| It's using outsideIT@locadomain.local, this account was created several years ago when the outside IT setup our original SQL Server 2000 and 2005. We've since taken over the IT in house and because that account was setup as the DB owner/admin we just continued using those credentials since we have satellite offices all over the world and operate 24/7 so we have extremely limited opportunity for scheduled downtime. in the event it was to mess something up and any unscheduled disruption would cost us alot more than it paying an IT admin to be on call to start the services back up manually. |
|
|
|
|
|
|
|
|
SQL Services fail to start automatically on reboot