Services stop automatically

Question

Post reply

Services stop automatically

Narendra-587652

SSChasing Mays

Points: 646
More actions
July 8, 2010 at 2:03 am

#223625

We have cluster environment with SQL 2008 and window 2008.
Form few days we are facing problem with one instances
The instances is down . and not showing up in cluster.
When we start sql services manually instances got up ,but it d't show up in cluster.
But after some time sql service again get down automatically , and instances is unavailable.
In erro log it says
-------------------------------------
spid43s Service Broker manager has shut down.
spid7s SQL Server is terminating in response to a 'stop' request from Service Control Manager
-------------------------------
Please let us know if you have any suggestion on that
-Nar

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Dugi SSCoach Points: 17998 More actions · Answer 1

What is the version of the SQL Server 2008!?

Enterprise or Standard or Express ...

:exclamationmark:

============================================================
SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]

Dugi SSCoach Points: 17998 More actions · Answer 2

One more thing, do you have different users to start your services ?!

============================================================
SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]

Narendra-587652 SSChasing Mays Points: 646 More actions · Answer 3

It is Enterprise edition

we using same account for services

Other instances on this cluster is active and working fine

onely one instances geting failed.

Once we restart SQl services manually it get started and after few time it get stoped

jude.pieries Default port Points: 1438 More actions · Answer 4

This is just a idea; are all the services running on the same service account ? If yes, create a new windows account and assign it as the new service account. Do the same for the passive node(s) where the instance would fail. Bring the instance resource online (on the cluster manager) after starting the sql instance.

This may not make much meaning but it worked for me

chetanr.jain Hall of Fame Points: 3938 More actions · Answer 5

There should be seperate Service account ( startup account) for Each SQL server Instance.

Also, that started account should be having local admin accounts on all nodes.

Narendra-587652 SSChasing Mays Points: 646 More actions · Answer 6

the same account is use for all instance in same cluster and it working fine

but this is geting failed , we did the same but no good news

i tryied to run the instance as local system but it also geting stop after few minute .

First i want to up the instances local or admin. but it geting fail in few minute after manual start

David Sorauer SSCrazy Points: 2874 More actions · Answer 7

Are you running automated Windows patch management (such as WSUS)? Depending on your settings, if it can't patch SQL Server successfully- it stops services.