Sorry I did not make this clear. I installed SQL Enterprise on the
cluster. There is only one instance.
In the Server 2003 Event log, there is only a indication that the MS
SQL Agent Service Stopped at so-and-so time. It's not a fatal warning,
or anything. It does not restart itself.
There is a message that it stopped. WHY did it stop? Was it a request to
stop, did it abort, etc. There is never just one message. It either shut
down due to a stop service request or it threw some kind of error and shut
down. There should also be indications in the SQL Server error log as well
as the SQL Agent error logs. Things don't just spontaneously shut down,
something causes it.

Signature
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
> Sorry I did not make this clear. I installed SQL Enterprise on the
> cluster. There is only one instance.
>
> In the Server 2003 Event log, there is only a indication that the MS
> SQL Agent Service Stopped at so-and-so time. It's not a fatal warning,
> or anything. It does not restart itself.
Anthony Thomas - 26 Jan 2006 03:01 GMT
Not to mention that by default, if the SQL Agent shuts down, it will cause
an instance failover. If it doesn't fail over, then it is not set up to
affect the group, or someone marked set it offline manually.
Try posting the SQL Agent log and SQL Server error log.
Sincerely,
Anthony Thomas
> There is a message that it stopped. WHY did it stop? Was it a request to
> stop, did it abort, etc. There is never just one message. It either shut
[quoted text clipped - 9 lines]
> > SQL Agent Service Stopped at so-and-so time. It's not a fatal warning,
> > or anything. It does not restart itself.