Article ID: 315159 - View products that this article applies to.
This article was previously published under Q315159
You may receive an error message if all the following conditions are true:
OleDbException (0x80004005): [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.]
SqlException (0x80004005): [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.]
System.Data.SqlClient.SqlException: SQL Server does not exist or access denied
System.Data.OleDbClient.OleDbException: SQL Server does not exist or access denied
When the ASP.NET worker process runs under the ASPNET account, if you do not enable impersonation for an application, all the threads that run the requests for that application run under the process account. The ASPNET account cannot establish a named pipes connection to the database server.
To work around this problem, use one of the following methods:
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
For additional information about ASP.NET security, click the following article number to view the article in the Microsoft Knowledge Base:
306590For more information about the <processModel> section, refer to the following MSDN documentation:
(https://support.microsoft.com/kb/306590/ )ASP.NET security overview
Article ID: 315159 - Last Review: May 13, 2007 - Revision: 2.6