Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SQL Service Autostart not working (2000)
- Thread starter cmwright
- Start date
What about this. Do the service accounts have "Log on as a Service" rights?
You're not using the Network Service account for the services, are you? (MS doesn't recommend it).
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
You're not using the Network Service account for the services, are you? (MS doesn't recommend it).
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
- Thread starter
- #22
Yes. It has "Log on as a Service" rights. It's a custom domain account created specifically for the SQL services. Hmmmmmmmm.....
I can't help but wonder if we're looking at this incorrectly. The rights have to be fine unless they are local or the other servers would exhibit the same behavior. Locally, they have to be correct because everything works once manually started.
Does that makes sense? I just can't see why the services won't start with the OS.
-Chris
I can't help but wonder if we're looking at this incorrectly. The rights have to be fine unless they are local or the other servers would exhibit the same behavior. Locally, they have to be correct because everything works once manually started.
Does that makes sense? I just can't see why the services won't start with the OS.
-Chris
ptheriault
IS-IT--Management
I don't know if this will help but here is a link for Windows services.
- Paul
- If at first you don't succeed, find out if the loser gets anything.
- Paul
- If at first you don't succeed, find out if the loser gets anything.
A local group policy on your two servers would override any domain / global group policies, especially if there is a DENY in there somewhere. So, verify the local security settings in the OS to make sure something isn't over-riding the Autostart.
I googled "Service will not Autostart" and got a whole bunch of Microsoft links, but didn't find your specific error. You might want to try it to see if any of these things jog your memory on something.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
I googled "Service will not Autostart" and got a whole bunch of Microsoft links, but didn't find your specific error. You might want to try it to see if any of these things jog your memory on something.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
Oh, I forgot to ask. These servers, how long have they been around and have they ever Autostarted before? Or are these recent installs? Are the servers part of the same domain as the domain user login? Are they using 2-way trust in the domain or have you (or anyone) undone the Trusts between these servers and the rest of the domain?
If the servers don't have 2-way trust in the domain, it could be that they are not trusting the domain SQL account and therefore won't let it start the services until manually prompted.
And lastly, have you tried changing the services to manual. Stopping & restarting. Then stopping them again, changing them back to Auto, then restarting... Just for kicks to see if something is stuck.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
If the servers don't have 2-way trust in the domain, it could be that they are not trusting the domain SQL account and therefore won't let it start the services until manually prompted.
And lastly, have you tried changing the services to manual. Stopping & restarting. Then stopping them again, changing them back to Auto, then restarting... Just for kicks to see if something is stuck.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
- Thread starter
- #26
Great suggestions. The servers were fresh installs of the OS, and this behavior was exhibited from the very start. SQL never autostarted.
The servers are part of the same domain as the user account.
There are no DENY policies in place. I double-checked that again.
I need to ask the admins about the trust issue.
I have not tried the switch to manual, etc. I'll give that a shot at night.
I'll also switch to a local account and back again to see if that helps.
Stay tuned.
-Chris
The servers are part of the same domain as the user account.
There are no DENY policies in place. I double-checked that again.
I need to ask the admins about the trust issue.
I have not tried the switch to manual, etc. I'll give that a shot at night.
I'll also switch to a local account and back again to see if that helps.
Stay tuned.
-Chris
mrdenny
Programmer
- May 27, 2002
- 11,595
FYI: Local Policy's are overwridden by Domain Policies, not the other way around.
Security policies are applied in this order.
Local
Site
Domain
OUs.
If local policys are changed and overwrite a domain policy, the next time that the machine updates it's GPOs the policy will be set back to the domain policy.
Are there any other services which aren't auto starting?
Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)
--Anything is possible. All it takes is a little research. (Me)
![[noevil]](/data/assets/smilies/noevil.gif "[noevil] [noevil]")
Security policies are applied in this order.
Local
Site
Domain
OUs.
If local policys are changed and overwrite a domain policy, the next time that the machine updates it's GPOs the policy will be set back to the domain policy.
Are there any other services which aren't auto starting?
Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)
--Anything is possible. All it takes is a little research. (Me)
mrdenny
Programmer
- May 27, 2002
- 11,595
Nope. Domain policys can overwrite local policys.
If you have a local policy which denies the Domain Administrators network access to your workstation, a domain policy can overwrite that. GPOs can either overwrite or be combined. Typically the policy which would set something like this would be set to overwrite.
Now if you had a local policy which added a user to the DENY Network Access, and a GPO which set the GRANT Network Access to the same user, and the GPO does not reset the DENY Network Access to no one, then the DENY will win, because the DENY was never overwritten.
Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)
--Anything is possible. All it takes is a little research. (Me)
If you have a local policy which denies the Domain Administrators network access to your workstation, a domain policy can overwrite that. GPOs can either overwrite or be combined. Typically the policy which would set something like this would be set to overwrite.
Now if you had a local policy which added a user to the DENY Network Access, and a GPO which set the GRANT Network Access to the same user, and the GPO does not reset the DENY Network Access to no one, then the DENY will win, because the DENY was never overwritten.
Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)
--Anything is possible. All it takes is a little research. (Me)
ptheriault
IS-IT--Management
Chris,
Have you tried putting a delay on the SQL service. There could be something prevent SQL from starting but if you delay the service even by a second it might start.
- Paul
- If at first you don't succeed, find out if the loser gets anything.
Have you tried putting a delay on the SQL service. There could be something prevent SQL from starting but if you delay the service even by a second it might start.
- Paul
- If at first you don't succeed, find out if the loser gets anything.
- Thread starter
- #31
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
