Add persitent state management with ASP.NET 2.0 and SQL Server Express

So I had to dig a bit to figure out how to add persistant SQLServer state management to ASP.net 2.0.

I'm using Web Developer Express (and the rest of the express studio suite) and I'm also using Sql Server 2005 express.

Ultimately, I found the tool located in:

C:\windows\Microsoft.NET\Framework\v2.0.50727

and I had to run:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regsql.exe -ssadd -sstype p -E -S .\sqlexpress

which gave me the results I wanted.

Here's the error message I was getting before I got things cleared up:

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) +575
   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +160
   System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +122
   System.Data.SqlClient.SqlConnection.Open() +229
   System.Web.SessionState.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo) +149

[HttpException (0x80004005): Unable to connect to SQL Server session database.]
   System.Web.SessionState.SqlSessionStateStore.ThrowSqlConnectionException(SqlConnection conn, Exception e) +276
   System.Web.SessionState.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo) +491
   System.Web.SessionState.SqlSessionStateStore.GetConnection(String id, Boolean& usePooling) +248
   System.Web.SessionState.SqlSessionStateStore.SetAndReleaseItemExclusive(HttpContext context, String id, SessionStateStoreData item, Object lockId, Boolean newItem) +213
   System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs) +713
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +167
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +117