SQL serrer 2005 failover clustering issues

#1

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before

#2

The failover partner parameter is used for mirroring, not clustering.

You should be connecting to the Virtual Network Name in the SQL Resource
group, not to any physical server name. In clustering, the network name is
part of the group and is the same no matter which physical host is running
the SQL instance. You leave the Failover Partner parameter blank.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"anith" <anith (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our
application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our
connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before

#3

The failover partner parameter is used for mirroring, not clustering.

You should be connecting to the Virtual Network Name in the SQL Resource
group, not to any physical server name. In clustering, the network name is
part of the group and is the same no matter which physical host is running
the SQL instance. You leave the Failover Partner parameter blank.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"anith" <anith (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our
application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our
connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before

#4

The failover partner parameter is used for mirroring, not clustering.

You should be connecting to the Virtual Network Name in the SQL Resource
group, not to any physical server name. In clustering, the network name is
part of the group and is the same no matter which physical host is running
the SQL instance. You leave the Failover Partner parameter blank.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"anith" <anith (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our
application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our
connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before

#5

The failover partner parameter is used for mirroring, not clustering.

You should be connecting to the Virtual Network Name in the SQL Resource
group, not to any physical server name. In clustering, the network name is
part of the group and is the same no matter which physical host is running
the SQL instance. You leave the Failover Partner parameter blank.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"anith" <anith (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our
application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our
connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before

#6

The failover partner parameter is used for mirroring, not clustering.

You should be connecting to the Virtual Network Name in the SQL Resource
group, not to any physical server name. In clustering, the network name is
part of the group and is the same no matter which physical host is running
the SQL instance. You leave the Failover Partner parameter blank.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"anith" <anith (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our
application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our
connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before

#7

The failover partner parameter is used for mirroring, not clustering.

You should be connecting to the Virtual Network Name in the SQL Resource
group, not to any physical server name. In clustering, the network name is
part of the group and is the same no matter which physical host is running
the SQL instance. You leave the Failover Partner parameter blank.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"anith" <anith (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our
application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our
connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before

#8

The failover partner parameter is used for mirroring, not clustering.

You should be connecting to the Virtual Network Name in the SQL Resource
group, not to any physical server name. In clustering, the network name is
part of the group and is the same no matter which physical host is running
the SQL instance. You leave the Failover Partner parameter blank.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"anith" <anith (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our
application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our
connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before

#9

The failover partner parameter is used for mirroring, not clustering.

You should be connecting to the Virtual Network Name in the SQL Resource
group, not to any physical server name. In clustering, the network name is
part of the group and is the same no matter which physical host is running
the SQL instance. You leave the Failover Partner parameter blank.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"anith" <anith (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our
application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our
connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before

#10

The failover partner parameter is used for mirroring, not clustering.

You should be connecting to the Virtual Network Name in the SQL Resource
group, not to any physical server name. In clustering, the network name is
part of the group and is the same no matter which physical host is running
the SQL instance. You leave the Failover Partner parameter blank.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"anith" <anith (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi.

We have set up failover clustering for our production servers. but we are
facing a strange issue when the web application servers try to connect to
slqserver when its failed over.
We are experiencing connection time out. but once we restart our
application
servers the clients are able to connect to the failed over servers. we are
using ODBC over SQL native client to connect to SQL servers. our
connection
string would look like this "Driver={SQL Native
Client};server=SQLserver1;Failover_
Partner=sqlserver2;uid=User;pwd=password;Database= mydb;Network=dbmssocn"

Could any one of you faced such issues before