sql server clustering: Hi All

I am having problems with the SQL server Agent what the cluster fails over.
The Event log is logging an event 103 "SQLServerAgent could not be started
(reason: Unable to connect to server '(local)'; SQLServerAgent Cannot
start).

The SQLAGENT.OUT log file reads as follows:

2004-03-09 19:20:37 - ? [393] Waiting for SQL Server to recover databases...
2004-03-09 19:20:38 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
unicode retail build) : Process ID
2004-03-09 19:20:38 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
unicode retail build) : Process ID 3224
2004-03-09 19:20:38 - ? [101] SQL Server PIPESQL1 version 8.00.760 (0
connection limit)
2004-03-09 19:20:38 - ? [102] SQL Server ODBC driver version 3.81.9042
2004-03-09 19:20:38 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
Local host server is
2004-03-09 19:20:38 - ? [310] 2 processor(s) and 1152 MB RAM detected
2004-03-09 19:20:38 - ? [339] Local computer is PIPESQL1 running Windows NT
5.0 (2195) Service Pack 4
2004-03-09 19:20:38 - ? [129] SQLSERVERAGENT starting under Windows NT
service control
2004-03-09 19:20:38 - + [260] Unable to start mail session (reason: No mail
profile defined)
2004-03-09 19:20:38 - + [408] SQL Server MSSQLSERVER is clustered -
AutoRestart has been disabled
2004-03-09 19:20:38 - + [396] An idle CPU condition has not been defined -
OnIdle job schedules will have no effect

Any help would be appreciated

Thank You

Marc

Try creating an alias on this node that points to the virtual SQL Server
name and uses TCP/IP as the network library. See if that allows it to
start. For some reason it is trying to use shared memory to connect and on
a cluster I do not believe this is the correct network lirary to use.

Rand
This posting is provided "as is" with no warranties and confers no rights.

Hi Rand

By Alias do you mean install anther instance of SQL on the node?

Marc

[quoted text, click to view]

You can create an alias by using cliconfig.exe. Got to Start - Run on this
node and enter cliconft. This will launch the SQL Server Client Network
Utility.

Select the Alias tab, click Add and enter the following information:

Server Alias: Virtual SQL Server name
Network Library: TCP/IP
Server name: Virtual SQL Server IP address

Uncheck the Dynamically Determine Port and enter the port number the
Virtual SQL Serfer is listening on.

Click OK twice and see if SQL Server Agent will come on line.

Rand


This posting is provided "as is" with no warranties and confers no rights.

Hi Rand

It does the same thing. comes on line for a few seconds then off line again.
Same error.

Marc

[quoted text, click to view]