Connection pooling not working in Clustered Env.

Hi,
We had deployed a .NET application in a non clustered environment with conection pooling and was working fine. Now we had moved to a clustered env and connection pooling stopped working. Is there any cluster aware setting that we need to look at. Please let me know your thoughts.
Thanks in advanceCan you be more specific on what went wrong? Any error code, exception stack will be helpful.sqlsql

Connection For Clustered Server

We have having a problem connecting to our 4 node cluster using an ado.net connection.
Here is what we have:

Connection String:

 <appSettings>
 <add key="ConnectionString" value="workstation id=AH501780;packet size=4096;integrated security=SSPI;data source=XXXXXX\XXXXXX;persist security info=False;initial catalog=xxxx" />
 </appSettings>

We added in the Web.config file:

 <identity impersonate="true"/>
 <authentication mode="Windows" />

In IIS 6 we have windows authentication checked.

We get the following error when we try to run the program:

SQL Server does not exist or access denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

We have the SQL Profiler running and we don't see any connection being made. Any help would be appreciated!

Thanks,
TreyTry this for general error message troubleshooting:

http://support.microsoft.com/default.aspx?kbid=328306

It could also be caused due to an incorrect renaming of the cluster:

http://support.microsoft.com/default.aspx?kbid=307336

Are you going through a firewall? Try this:

http://support.microsoft.com/default.aspx?kbid=318432

Also, is the SQL Server updated with SP3?|||We got a little further with our problem. We have a VB.net windows application that will connect using that connection string. But the asp.net app will not. We also now added a port number to the connection string and we get the following error:

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

So once again I hit another wall.

Trey|||In IIS, check under Authentication to see if "Anonymous" authentication is still enabled. Or you could add the following to your web.config (if it is already there, replace it with this):

<authorization>
<deny users="?" />
</authorization>|||Just wondering...dose my server need to use Active Directory?|||Is the SQL Server on the same server as the web server? If so, no. Otherwise, you need to configure the setup differently if you are not using AD.|||the web server and the SQL culter are on different boxes. where do i need to look now?|||Try creating a domain account on the network, then give that account permission to log into the SQL Server cluster. Then have your web app impersonate that account and see what happens.

connecting to sql server using Kerberos

Hi ALL,
I have an issue with connecting to a clustered sql 2005 instance from an XP
box using Kerberos: wondering if some one can help me to get to the bottom of
the issue; this is what happens;
Say if I log on to the domain; at 8 am yesterday, I get Kerberos tickets
with start time = 2007-05-23 0800 and End time =2007-05-23 1800 (10 hours) ,
also it has a renewal until = 2007-05-30 0800 (i.e. 7 days)
after the end time my existing management studio won’t use Kerberos for new
connections (although existing connections made prior will be using the
original authentication ) but any new management studio instance will use
Kerberos; as expected.
This is the same with the query analyser as well, which means can rule out
it been application specific.
Also I'am using tcp:instance so it always uses tcp.
All the requirments as mentioned in the following KB article are met as well
http://support.microsoft.com/kb/909801/
Any ideas to trouble shoot would be great guys!!
CTS DBA
I just forgot to add few vital informations,
we have a win 2000 active directory, sql server 2005 sp2 is 64 bit and
resides on a win 2003 64 bit cluster
client machines uses xp sp2 with latest patches etc.
CTS DBA
"CTS_DBA" wrote:

> Hi ALL,
> I have an issue with connecting to a clustered sql 2005 instance from an XP
> box using Kerberos: wondering if some one can help me to get to the bottom of
> the issue; this is what happens;
> Say if I log on to the domain; at 8 am yesterday, I get Kerberos tickets
> with start time = 2007-05-23 0800 and End time =2007-05-23 1800 (10 hours) ,
> also it has a renewal until = 2007-05-30 0800 (i.e. 7 days)
> after the end time my existing management studio won’t use Kerberos for new
> connections (although existing connections made prior will be using the
> original authentication ) but any new management studio instance will use
> Kerberos; as expected.
> This is the same with the query analyser as well, which means can rule out
> it been application specific.
> Also I'am using tcp:instance so it always uses tcp.
> All the requirments as mentioned in the following KB article are met as well
> http://support.microsoft.com/kb/909801/
> Any ideas to trouble shoot would be great guys!!
> --
> CTS DBA

connecting to sql server using Kerberos

Hi ALL,
I have an issue with connecting to a clustered sql 2005 instance from an XP
box using Kerberos: wondering if some one can help me to get to the bottom o
f
the issue; this is what happens;
Say if I log on to the domain; at 8 am yesterday, I get Kerberos tickets
with start time = 2007-05-23 0800 and End time =2007-05-23 1800 (10 hours) ,
also it has a renewal until = 2007-05-30 0800 (i.e. 7 days)
after the end time my existing management studio won’t use Kerberos for ne
w
connections (although existing connections made prior will be using the
original authentication ) but any new management studio instance will use
Kerberos; as expected.
This is the same with the query analyser as well, which means can rule out
it been application specific.
Also I'am using tcp:instance so it always uses tcp.
All the requirments as mentioned in the following KB article are met as well
http://support.microsoft.com/kb/909801/
Any ideas to trouble shoot would be great guys!!
CTS DBAI just forgot to add few vital informations,
we have a win 2000 active directory, sql server 2005 sp2 is 64 bit and
resides on a win 2003 64 bit cluster
client machines uses xp sp2 with latest patches etc.
CTS DBA
"CTS_DBA" wrote:

> Hi ALL,
> I have an issue with connecting to a clustered sql 2005 instance from an X
P
> box using Kerberos: wondering if some one can help me to get to the bottom
of
> the issue; this is what happens;
> Say if I log on to the domain; at 8 am yesterday, I get Kerberos tickets
> with start time = 2007-05-23 0800 and End time =2007-05-23 1800 (10 hours)
,
> also it has a renewal until = 2007-05-30 0800 (i.e. 7 days)
> after the end time my existing management studio won’t use Kerberos for
new
> connections (although existing connections made prior will be using the
> original authentication ) but any new management studio instance will use
> Kerberos; as expected.
> This is the same with the query analyser as well, which means can rule out
> it been application specific.
> Also I'am using tcp:instance so it always uses tcp.
> All the requirments as mentioned in the following KB article are met as we
ll
> http://support.microsoft.com/kb/909801/
> Any ideas to trouble shoot would be great guys!!
> --
> CTS DBA