OS= Windows 2003 64Bit Ent. R2 SP2 (latest updates)
SQL Server= MS SQL 64Bit Ent. with SP2
Below events gets generated on Cluster Node :-

1]The Cluster Service failed to bring the Resource Group "ABCD" completely
online or offline.
2]Cluster resource 'SQL Server' in Resource Group 'IABCD' failed. (Event id
-1069)
3]The SQL Server Agent (MSSQLSERVER) service terminated unexpectedly. It
has done this 1 time(s). --Event ID -- 7039

Event ID - 19019
[sqsrvres] CheckServiceAlive: Service is dead
[sqsrvres] OnlineThread: Error 1 bringing resource online.
[sqsrvres] OnlineThread: service stopped while waiting for QP.
[sqsrvres] CheckServiceAlive: Service is dead
[sqsrvres] OnlineThread: Error connecting to SQL Server.
[sqsrvres] ConnectToSQL: service stopped while trying to connect to server.
[sqsrvres] CheckServiceAlive: Service is dead

When we try to bring onlibe the failed resources or move group then server
goes to hung state.

Please help in this .

Thanks in Advance.

Regards
Dinesh Bhandare

Dinesh,

I have what sounds like a very similar problem. Trying to figure it out now.
We are getting similar messages in the log, but in addition, I am getting
EventID = 102 and 103. The 103 error indicates that the SQL Agent is
attempting to connect to an invalid instance. I am trying to figure out
where the SQL Agent is getting the incorrect instance to connect to.

My SQL Server (INST1) simply will not come online and I don't know why.
Note that this only occurs on my NODE-A server. If I move the groups to the
NODE-B server, everything is fine.

I also am getting EventID 19019 which is indicating, "The user is not
associated with a SQL Server connection.". I don't know what this is
referring to. SQL and SQL Agent run under the same domain/service account
and credentials are verified. The only other account called for is a local
Admin account to install the SQL instances. I am using my account, which is
a member of the local Admins group on both SQL Servers.


If you figure this out, please post the root cause and solution, and I will
do the same.

Regards,
DetRich

"Dinesh Bhandare" wrote:

The application log should show why the SQL instance failed.

It looks like the SQL instance is not responding to the cluster resource
"looksAlive" and "IsAlive" checks. Might be a dependency error. Try and
bring the disk resources online, then the IP , then the network name
resources online. Then try and bring the SQL Server resource online and see
if you get better results or at least better error messages.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP



"Dinesh Bhandare" <Dinesh Bhandare (AT) discussions (DOT) microsoft.com> wrote in
message news:AF06E59C-99C3-4F17-987A-D666FEB9EC08 (AT) microsoft (DOT) com...

Hi Geoff,

Thanks for reply.

Only SQL Server service and Agent gets failed and never comes online until
reboot of the server, other resources status is Online.


Dinesh
"Geoff N. Hiten" wrote:

Dear All,

The problem has been resolved by microsoft after analysing the dump provided
from the problem server. As per analysis the problem was with replistore
service.
Found request's more than 49,000 queue in memory which was causing SQL
server stop the in abnormal status. The replistore service stopped mode but
still the driver was getting loaded in to memory.

Changed the startup parameter to 4 in service startup mode in the registry
to resolve the problem.

Regards,

Dinesh Bhandare

"Dinesh Bhandare" wrote:

Dinesh Bhandare wrote on 11/30/2009 05:59 ET :
parameter to 4 in service startup mode in the registry to resolve the
problem.&quot;

thanks in advance