Answered by:
A network-related or instance-specific error occurred while establishing a connection to SQL Server

Question
-
Hi All,
I am facing following problem while publishing my application to azure.
I have check connection string it works fine with local application. Publish process was successful but when try to login it throws following error.
Please help me.
Server Error in '/' Application.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
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: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Source Error:An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:[SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +6400336 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() +477 System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover) +506 System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject, Boolean withFailover) +311 System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout) +6420310 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +6420345 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +436 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +506 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +49 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +6422230 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +78 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +2194 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +89 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +6425758 System.Data.SqlClient.SqlConnection.Open() +300 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +150 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +4790383 System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.GetConnectionHolder() +23 System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.LoadPersonalizationBlobs(WebPartManager webPartManager, String path, String userName, Byte[]& sharedDataBlob, Byte[]& userDataBlob) +2336614 System.Web.UI.WebControls.WebParts.PersonalizationProvider.LoadPersonalizationState(WebPartManager webPartManager, Boolean ignoreCurrentUser) +146 System.Web.UI.WebControls.WebParts.WebPartPersonalization.Load() +273 System.Web.UI.WebControls.WebParts.WebPartPersonalization.LoadInternal() +41 System.Web.UI.Control.InitRecursive(Control namingContainer) +133 System.Web.UI.Control.InitRecursive(Control namingContainer) +421 System.Web.UI.Control.InitRecursive(Control namingContainer) +421 System.Web.UI.Control.InitRecursive(Control namingContainer) +421 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1970
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.2042Monday, November 10, 2014 12:56 PM
Answers
-
Hi,
Please check if there is any other connection string in your web.config.
Please refer the following links. Someone has encountered this issue when included membership provider in the web application and the issue had been addressed when the membership methods are overridden.
ASP.NET Identity: Authorize attribute with roles doesn't work on Azure
Azure Website Connecting to Azure Database works fine on local but not deployed
- Edited by Ramesh Swaminathan Tuesday, November 11, 2014 2:40 PM
- Marked as answer by Will ShaoMicrosoft employee Monday, November 17, 2014 7:10 AM
Tuesday, November 11, 2014 2:39 PM
All replies
-
Hi,
Are you accessing the local database in your application when you test it in your local environment? If so, you cannot access the local database when you deploy your application in Azure. If you have an SQL Azure database, update the connection string before release to Azure.
If your local database can be accessible using static TCP port over internet, then please check if the per-requisites are met as described in the following link.
Connect to an on-premises SQL Server from an Azure website using Hybrid Connections
Microsoft MVP - ASP/ASP.NET
Monday, November 10, 2014 2:15 PM -
Hi,
Thanks for your response!
I am accessing azure database from local copy of application, it works fine but when publish to azure it throws above error.
I am using framework 4.0 and SQL server 2008/2012.
Thanks !!
Tuesday, November 11, 2014 12:38 PM -
Hi,
Please check if there is any other connection string in your web.config.
Please refer the following links. Someone has encountered this issue when included membership provider in the web application and the issue had been addressed when the membership methods are overridden.
ASP.NET Identity: Authorize attribute with roles doesn't work on Azure
Azure Website Connecting to Azure Database works fine on local but not deployed
- Edited by Ramesh Swaminathan Tuesday, November 11, 2014 2:40 PM
- Marked as answer by Will ShaoMicrosoft employee Monday, November 17, 2014 7:10 AM
Tuesday, November 11, 2014 2:39 PM