Before I explain the issue I am facing, I would like to say that I did read the post at
but in my case the problem is transient (lasts for approximately two minutes after a failover) so items 1-3 in the list of troubleshooting steps do not seem to make sense.
As to 4 and 5, the named instances use non-default ports (2433 and 3433 respectively), so I do not know how to tailor the PortQry command for that.
portqry.exe -n ServerA,2433-p UDP -e 1434
portqry.exe -n ServerA,2433 -p UDP -e 2434
and it failed both times with a "Failed to resolve name to IP address" while the server was up and serving database requests
The same thing happened when I tried it with the failover server as well.
***The issue I am facing***
I am using Enterprise Library 4.1 to connect to a SQL Server 2008 R2 database with a mirror.
My connection string itself is as below (with dummy values for all fields):
"Data Source=ServerA;Failover Partner=ServerB;Initial Catalog=DBName;User ID=uid;Password=pwd;Connect Timeout=5"
Sample .NET code is as below (with modifications to instantiate all variables locally to provide context):
SqlDatabase db = new SqlDatabase(ConnectionString);
SqlConnection cn = (SqlConnection)db
View Complete Post