HTTP/1.1 500 Internal Server Error Connection: close Date: Tue, 12 Aug 2008 20:03:28 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 6997 An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Server Error in '/' Application.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

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: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

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): An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)]

   System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)  435

   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)  82

   System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)  105

   System.Data.SqlClient.SqlConnection.Open()  111

   System.Web.SessionState.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo)  79



[HttpException (0x80004005): Unable to connect to SQL Server session database.]

   System.Web.SessionState.SqlSessionStateStore.ThrowSqlConnectionException(SqlConnection conn, Exception e)  227

   System.Web.SessionState.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo)  349

   System.Web.SessionState.SqlSessionStateStore.GetConnection(String id, Boolean& usePooling)  285

   System.Web.SessionState.SqlSessionStateStore.SetAndReleaseItemExclusive(HttpContext context, String id, SessionStateStoreData item, Object lockId, Boolean newItem)  178

   System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs)  476

   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()  92

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)  64

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433