I hope this is not a FAQ. I have a 2-node Windows Server 2003 cluster, with
SQL Server 2000 SP3a. This is a development system, and is actually
implemented using VMware (though I don't think that is relevant).
Occasionally when moving the SQL Server group, I get random failures of SQL
Server, Agent, or Fulltext. Going through cluster.log, I find entries like
the following:
000002d4.0000020c::2005/03/10-05:56:37.490 ERR SQL Server <SQL Server>:
[sqsrvres] StartResourceService: Failed to start MSSQLSERVER service.
CurrentState: 1
000002d4.0000020c::2005/03/10-05:56:37.490 ERR SQL Server <SQL Server>:
[sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 435)
000002d4.0000020c::2005/03/10-05:56:37.505 ERR SQL Server <SQL Server>:
[sqsrvres] OnlineThread: Error 435 bringing resource online.
and
000002d4.00000cf0::2005/03/10-06:09:52.281 ERR <Unknown Resource>:
[sqsrvres] StartResourceService: Failed to start SQLSERVERAGENT service.
CurrentState: 1
000002d4.00000cf0::2005/03/10-06:09:52.281 ERR SQL Server Agent <SQL Server
Agent>: [sqagtres] OnlineThread: ResUtilsStartResourceService failed (status
435)
000002d4.00000cf0::2005/03/10-06:09:52.281 ERR SQL Server Agent <SQL Server
Agent>: [sqagtres] OnlineThread: Error 435 bringing resource online.
Any ideas as to what is going wrong? Could this be network-related?
Many thanks,
John.
John wrote:
> Hi All,
> I hope this is not a FAQ. I have a 2-node Windows Server 2003 cluster, with
> SQL Server 2000 SP3a. This is a development system, and is actually
> implemented using VMware (though I don't think that is relevant).
It could be relevant. Workstation 4.x does too much disk caching so disk
corruption will occur, on the quorum disk for example. VMWare GSX 3 is
fine a long as you add disk.locking="FALSE" and scsi0.sharedBus="virtual"
Hans
|||Thanks for the response. Yes, I am using VMware Workstation 4.5 - that may
be an issue.
Is there a way of finding out exactly what error 435 means? It does not
seem to be a standard error code; "net helpmsg" does not help.
Thanks,
John.
"Hans de Bruin" wrote:
> John wrote:
> It could be relevant. Workstation 4.x does too much disk caching so disk
> corruption will occur, on the quorum disk for example. VMWare GSX 3 is
> fine a long as you add disk.locking="FALSE" and scsi0.sharedBus="virtual"
> --
> Hans
>
|||John wrote:
> Thanks for the response. Yes, I am using VMware Workstation 4.5 - that may
> be an issue.
> Is there a way of finding out exactly what error 435 means? It does not
> seem to be a standard error code; "net helpmsg" does not help.
>
Cluster service can't bring the resources online. Check the windows event
log and the sql log files to find out why. When that does not help, run a
dos box as the sql service account an start sql from the command line (not
net start but the sqlserver.exe).
If you really want to cluster with vmware either use a single node cluster
or use iscsi drives. I have got an out of date site which describes this:
http://eratosthenes.xs4all.nl/wmwarecluster/ .
Hans
|||What was the fix for this? I am having the same exact issue.
Quote:
John wrote:
> Thanks for the response. Yes, I am using VMware Workstation 4.5 - that may
> be an issue.
> Is there a way of finding out exactly what error 435 means? It does not
> seem to be a standard error code; "net helpmsg" does not help.
>
Cluster service can't bring the resources online. Check the windows event
log and the sql log files to find out why. When that does not help, run a
dos box as the sql service account an start sql from the command line (not
net start but the sqlserver.exe).
If you really want to cluster with vmware either use a single node cluster
or use iscsi drives. I have got an out of date site which describes this:
http://eratosthenes.xs4all.nl/wmwarecluster/ .
Hans
No comments:
Post a Comment