Server Error in asp.net application

anantgupta · June 25th, 2011, 02:54 AM

My ASP.NET application runs perfectly on the Development server but when I try to deploy it to the local IIS server or a free hosting provider server, it turns with an unhandled exception in both cases an the error in the latter case being:

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)

I've spent days trying to sort out this problem but every where it asks for checking the remote login connections.In spite of all that, the error turns out again and again. Please help.

Imar · June 25th, 2011, 06:26 AM

Hi there,

Can you provide the following information:

1. OS of the web server
2. Name of the instance of the SQL Server installation (e.g. the name your hosts tells you to use to connect to it)
3. Your connection string
4. The location and code that gives you this error (e.g. in all your pages, or in pages using services like Membership; a stack trace would help).

Cheers,

Imar

anantgupta · June 25th, 2011, 07:39 AM

1. I have SQL Web Server 2008 R2
2.my instance name is SQLEXPRESS1

3.The connection string name is BlogEntryConnectionString, BlogEntry being name of the blog database, and the connection string being: "Data Source=ANANT-PC\SQLEXPRESS1;Initial Catalog=BlogEntry;Integrated Security=True" providerName="System.Data.SqlClient"
ANANT-PC is the name of the machine.

4. The error doesn't arise when I run the code on development server but on the local server or the server of the hosting provider. It is related to permissions accessed by the database.
On the local server, the following exception arises:
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
and the stack trace:
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException exception, Boolean breakConnection) +308
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning() +412
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity) +456
System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject) +275
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout) +1076
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +309
System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +350
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +509
System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +49
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection owningObject) +984
System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection owningObject) +91
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection owningObject) +1908
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection owningConnection) +85
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +270
System.Data.SqlClient.SqlConnection.Open() +299

In case of http://www.aspspider.info/anant718:
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)
Stack trace:
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException exception, Boolean breakConnection) +5009598
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning() +234
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity) +341
System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject) +129
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout) +239
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +195
System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +232
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +185
System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +33
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection owningObject) +524
System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection owningObject) +479
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection owningConnection) +108
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +126
System.Data.SqlClient.SqlConnection.Open() +125

Please try to sort this out.It will be a great help to me.Thank you so much!

Imar · June 25th, 2011, 07:55 AM

Quote:

The error doesn't arise when I run the code on development server but on the local server or the server of the hosting provider.

and

Quote:

2.my instance name is SQLEXPRESS1

Does this mean you're trying to connect to ANANT-PC\SQLEXPRESS1 from your site running with your host? That's not going to work; first of all because ANANT-PC is a local name, and secondly because of firewall issues.

When you host your site with an hoster, they typically give you access to a SQL Server and provide details to connect to it.

Cheers,

Imar

anantgupta · June 28th, 2011, 01:01 AM

Hello Sir,
Now an another issue has arrived and this may be not that difficult to solve.I noticed it right now.When I run the app even on the development server and the localhost, the page which doesn't require a login opens perfectly with the data list but the page that should open after entering the correct credentials in the login page dosent open and shows the same error-40 stated in the previous post.
Earlier, the app worked fine in the development server and didnt work at all in the localhost. But now it works partially in both development and localhost servers. This may be due to the change in settings that I must have done in order to find a solution.