can not connect to SQL after fail-over

Hello,
I really hope someone knows what maybe the cause for this issue:
I recently added a new win2k3 node to a SQL cluster. I have installed SQL
2000 and SQL 2000 sp4 on the new node. All the groups including the SQL
group fails over without any problems to the new node. However, once it
moves over to the new node, I have the following issues:
1. The SQL Server Service Manager on the taskbar is stopped and in the
"Services" drop down, nothing is listed.
2. I can no longer telnet to port 1433 on the SQL virtual server.
The sql resources are are online and the services are running on the new nod
e.
Any help would be greatly appreciated!!
WGFind what port the SQL service is actually listening on, and try to connect
to that port explicitly using the virtual server IP addres followed by the
port number wiht a comma in between. For instance:
osql -S36.7.9.101,1433 -Usa -Ppassword
Linchi
"Walid" wrote:

> Hello,
> I really hope someone knows what maybe the cause for this issue:
> I recently added a new win2k3 node to a SQL cluster. I have installed SQL
> 2000 and SQL 2000 sp4 on the new node. All the groups including the SQL
> group fails over without any problems to the new node. However, once it
> moves over to the new node, I have the following issues:
> 1. The SQL Server Service Manager on the taskbar is stopped and in the
> "Services" drop down, nothing is listed.
> 2. I can no longer telnet to port 1433 on the SQL virtual server.
> The sql resources are are online and the services are running on the new n
ode.
> Any help would be greatly appreciated!!
> WG

can not connect to SQL after fail-over

Hello,
I really hope someone knows what maybe the cause for this issue:
I recently added a new win2k3 node to a SQL cluster. I have installed SQL
2000 and SQL 2000 sp4 on the new node. All the groups including the SQL
group fails over without any problems to the new node. However, once it
moves over to the new node, I have the following issues:
1. The SQL Server Service Manager on the taskbar is stopped and in the
"Services" drop down, nothing is listed.
2. I can no longer telnet to port 1433 on the SQL virtual server.
The sql resources are are online and the services are running on the new node.
Any help would be greatly appreciated!!
WGFind what port the SQL service is actually listening on, and try to connect
to that port explicitly using the virtual server IP addres followed by the
port number wiht a comma in between. For instance:
osql -S36.7.9.101,1433 -Usa -Ppassword
Linchi
"Walid" wrote:
> Hello,
> I really hope someone knows what maybe the cause for this issue:
> I recently added a new win2k3 node to a SQL cluster. I have installed SQL
> 2000 and SQL 2000 sp4 on the new node. All the groups including the SQL
> group fails over without any problems to the new node. However, once it
> moves over to the new node, I have the following issues:
> 1. The SQL Server Service Manager on the taskbar is stopped and in the
> "Services" drop down, nothing is listed.
> 2. I can no longer telnet to port 1433 on the SQL virtual server.
> The sql resources are are online and the services are running on the new node.
> Any help would be greatly appreciated!!
> WG

can not connect to SQL after fail-over

Hello,
I really hope someone knows what maybe the cause for this issue:
I recently added a new win2k3 node to a SQL cluster. I have installed SQL
2000 and SQL 2000 sp4 on the new node. All the groups including the SQL
group fails over without any problems to the new node. However, once it
moves over to the new node, I have the following issues:
1. The SQL Server Service Manager on the taskbar is stopped and in the
"Services" drop down, nothing is listed.
2. I can no longer telnet to port 1433 on the SQL virtual server.
The sql resources are are online and the services are running on the new node.
Any help would be greatly appreciated!!
WG
Find what port the SQL service is actually listening on, and try to connect
to that port explicitly using the virtual server IP addres followed by the
port number wiht a comma in between. For instance:
osql -S36.7.9.101,1433 -Usa -Ppassword
Linchi
"Walid" wrote:

> Hello,
> I really hope someone knows what maybe the cause for this issue:
> I recently added a new win2k3 node to a SQL cluster. I have installed SQL
> 2000 and SQL 2000 sp4 on the new node. All the groups including the SQL
> group fails over without any problems to the new node. However, once it
> moves over to the new node, I have the following issues:
> 1. The SQL Server Service Manager on the taskbar is stopped and in the
> "Services" drop down, nothing is listed.
> 2. I can no longer telnet to port 1433 on the SQL virtual server.
> The sql resources are are online and the services are running on the new node.
> Any help would be greatly appreciated!!
> WG
sql

Can I run both a SQL 2000 instance and SQL 2005 Instance on same two node cluster?

I'd like to run a SQL 2000 instance and a SQL2005 instance on the same
two node windows cluster.
Each would have it's own disk groups.
Basically mixed versions of instances on a cluster.
Does anyone know where I can get Microsoft's official statement on
this?
Has anyone done this before?
Yes. This is allowed and supported under most scenarios, but there are some
limitations.
The Microsoft SQL Server support policy for Microsoft Clustering
http://support.microsoft.com/kb/327518
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sanctus" <mchi55@.hotmail.com> wrote in message
news:1174503282.467053.80730@.l77g2000hsb.googlegro ups.com...
> I'd like to run a SQL 2000 instance and a SQL2005 instance on the same
> two node windows cluster.
> Each would have it's own disk groups.
> Basically mixed versions of instances on a cluster.
> Does anyone know where I can get Microsoft's official statement on
> this?
> Has anyone done this before?
>