Hi there,

I have a two node cluster Win 2k with SP4 and SQL 2k with SP3. There are
two instances of SQL. The primary instance comes up just fine. The
secondary does not come up all of the disk, IP, and name resources load, but
the SQL Server resource will not. I have been able to get it to load by
opening the SQL Server Client Network Utility and putting in a Named Pipes
Alias for the instance. When I do this the clusetered instance comes online,
but I cannot access it from any clients.

Does anyone have any idea what might be going on?

Hi

Run "svrnetcn.exe" on the secondary instance and make sure that both TCP/IP
and Named Pipes are enabled.

On the Secondary, whan she starts, are there any errors in the SQL Log?

Regards
Mike

"Squerb" wrote: