Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


  • All machines run Windows Server 2008 Enterprise
  • SQL Server 2012 Standard (Primary)
  • SQL Server 2012 Standard (Mirror)
  • SQL Server 2012 Express (Witness)

Root issue: Our ASP.NET application is not “failing over” correctly, while our classic ASP application is.

Mirroring is currently configured with a witness and I’m get all green check marks inside of SSMS.

What I have tested.

  • A manual failover works flawlessly. Both the classic asp and the ASP.NET application “fail over” to the mirror server without issues
  • In an automatic failover situation (pull network cord out of Primary SQL server) the classic asp applications fails over correctly, but the ASP.NET application does not. We get a time out. I noticed inside SSMS that the mirror server does correctly become the “primary” server.
  • There is nothing out of the ordinary in the SQL Error Logs when comparing manual & automatic failover.

Below is our connection strings for Classic ASP and for ASP.NET

  • Classic ASP (global.asa)

    Application("DSN_STRING") = "Provider=SQLNCLI;   ; Failover;
     Database=MOD; Uid=XXXXXXX; Pwd=YYYYYY;"
  • ASP.NET (web.config)

    add name="MOD" connectionString="Data;
      Failover;Initial Catalog=MOD;
      User ID=XXXXX;Password=YYYYYY;Connect Timeout=150;
      Min Pool Size=20;" providerName="System.Data.SqlClient"/
share|improve this question

closed as unclear what you're asking by Max Vernon, RolandoMySQLDBA, Mark Storey-Smith, bluefeet, Jon Seigel Oct 20 '13 at 21:45

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question.If this question can be reworded to fit the rules in the help center, please edit the question.

Are the ASP.NET and ASP applications on the same server? Timeout would indicate to me that one of them cannot properly resolve the FQDN in the connection string. – Aaron Bertrand May 20 '13 at 15:09
What happens if you remove the explicit 150-second timeout value from the .NET connection string? You want the connection to time out so it tries the mirror instead of the primary. – Jon Seigel May 20 '13 at 15:53