Sql server

Question

Server Error in '/' Application.
The network path was not found
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.ComponentModel.Win32Exception: The network path was not found

Source Error:

Line 28: string strConnection = System.Web.Configuration.WebConfigurationManager.ConnectionStrings["ConnectionString"].ToString();
Line 29: SqlConnection sqlcon = new SqlConnection(objEncry.Decrypt(strConnection));
Line 30: sqlcon.Open();
Line 31: SqlCommand sqlcmd = new SqlCommand("ExceptionInsert", sqlcon);
Line 32: sqlcmd.CommandType = CommandType.StoredProcedure;

Source File: c:\inetpub\site\file\App_Code\utilities.cs Line: 30

Stack Trace:

[Win32Exception (0x80004005): The network path was not found]

[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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)]
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +642
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +116 System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) +1079
System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions) +6600667 System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource1 retry) +233
System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +278
System.Data.SqlClient.SqlConnection.Open() +239
utilities.ExceptionDetails(String ExMessage, String Url, String Functionname) in c:\inetpub\site\oriensnepal\App_Code\utilities.cs:30
_Default.BindNews() in c:\inetpub\site\oriensnepal\Default.aspx.cs:31
_Default.Page_Load(Object sender, EventArgs e) in c:\inetpub\site\oriensnepal\Default.aspx.cs:17
System.Web.UI.Control.LoadRecursive() +71
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3178

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.33440

Answer 1

Hi @Ashok Kumar P ,

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.

It seems that the remote connections are not allowed, please refer to the solution from this blog. And here has a similar thread.

Best regards,
Carrin

---

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

The error message means that you were able to reach SQL Server.

Things to check:

1. Is the connection string specifying the correct server\instance?
2. Is the SQL Server instance running?
3. If it is a named instance, is the Browser running?
4. If it is a remote instance, does SQL Server accept remote connections?
5. Is there any firewall in the way?

Here is a link to a troubleshooter: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine?view=sql-server-2017