I am trying to run the Personal Website starter kit from Jeremy Wadsworth (but the same thing happens with the Starter Kit here).  When I run it through the Visual Web Developer debug tool everything on the website works fantastic.  When I try to access it though the web I get; (Happens going through IE on Windows Home Server where the site is as well as going through IE and Firefox on my PC.)

Runtime Error

Any help tracking the problem down would be greatly appreciated.

Terry 

My guess is that IIS is not configured correctly.  Open IIS and go to the Web Service Extensions folder.  You need make sure that ASP.NET is allowed.

 Careed,

Thanks for the reply but ASP.NET is allowed in IIS.  Both v1.1.4322 and v2.0.50727.   Any other thoughts?

Terry 

Can you turn on dubugging. We need to see the details of the error.

 Here is the error in the event log

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7/13/2008 10:08:06 AM
Event time (UTC): 7/13/2008 3:08:06 PM
Event ID: 81b4f89598564c948e534cb6d4579f18
Event sequence: 2
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: /LM/W3svc/1/Root/Family-2-128604352866406250
    Trust level: Full
    Application Virtual Path: /Family
    Application Path: D:\shares\Website\Family\
    Machine name: WARNKESERVER
 
Process information:
    Process ID: 4240
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE
 
Exception information:
    Exception type: SqlException
    Exception message: A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)
 
Request information:
    Request URL: http://warnke.homeserver.com/family/default.aspx
    Request path: /family/default.aspx
    User host address: 75.128.248.94
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: NT AUTHORITY\NETWORK SERVICE
 
Thread information:
    Thread ID: 8
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
   at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
   at System.Data.SqlClient.TdsParserStateObject.ReadByte()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate)
   at System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation)
   at System.Web.Security.SqlRoleProvider.RoleExists(String roleName)
   at System.Web.Security.Roles.RoleExists(String roleName)
   at ASP.global_asax.Application_Start(Object sender, EventArgs e) in D:\shares\Website\Family\global.asax:line 7
 
 
Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Check you SQL Server configuration and make sure that you have TCP/IP capabilities.  It sounds like only Named Pipes is currently the only protocol functional.

Careed, 

SQL has both local and remote connections active and using both TCP/IP and pipes already configured.    

Terry 

How are you connecting to the SQL Server through the application?  The error log message seems to indicate that the connection cannot be made.  This might be due to your authorization to connect through the ASP.NET worker process.

 Being a nob of a noob you got me on that one.  No idea what you are talking about.  I pretty much copied the starter kit stuff and went from there.

You need to make sure that the connectionstring in your web.config is configured to the database you are using and allows access to your database.

Open up the web.config and look for the section <connectionStrings>

And check the deatils there match you sql setup.

Hope it helps

Also a great write up for the membership and databases is at http://aspnet.4guysfromrolla.com/articles/120705-1.aspx

 O.K.  I think it has something to do with the connectionstrings.

Here is what is there;

<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
    <configSections>
        <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
            <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
                <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
                <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
                    <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>
                    <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
                    <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
                    <section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/></sectionGroup></sectionGroup></sectionGroup></configSections><connectionStrings>
    

        <!-- Connection for SQL 2005 Express -->
        <remove name="Personal"/>
        <add name="Personal" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|personal.mdf" providerName="System.Data.SqlClient"/>
        <!-- Connection for SQL Server 2005 -->
        <!--<add name="Personal" connectionString="Server=(Local);Integrated Security=True;database=Personal" providerName="System.Data.SqlClient"/>-->
        <remove name="LocalSqlServer"/>
        <!-- Connection for SQL 2005 Express -->
        <add name="LocalSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|personal.mdf" providerName="System.Data.SqlClient"/>
        <!-- Connection for SQL Server 2005 -->
        <!--<add name="LocalSqlServer" connectionString="Server=(Local);Integrated Security=True;database=Personal" providerName="System.Data.SqlClient"/>-->
    </connectionStrings>

Am I correct in assuming that I need to uncomment the lines in bold above?   Do I need to delete/comment out the other lines?  Do I need the AttachDBFilename=.................. then?

Hey what do you expect I worked on mainframes not servers!!!!!

Thanx

Terry

P.S. 

Do I need to regenerate the publickeytoken? 

Yes true it like this

<!-- Connection for SQL 2005 Express -->
        <remove name="Personal"/>
        <!--<add name="Personal" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|personal.mdf" providerName="System.Data.SqlClient"/>-->
        <!-- Connection for SQL Server 2005 -->
        <add name="Personal" connectionString="Server=(Local);Integrated Security=True;database=Personal" providerName="System.Data.SqlClient"/>
        <remove name="LocalSqlServer"/>
        <!-- Connection for SQL 2005 Express -->
        <!--<add name="LocalSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|personal.mdf" providerName="System.Data.SqlClient"/>-->
        <!-- Connection for SQL Server 2005 -->
        <add name="LocalSqlServer" connectionString="Server=(Local);Integrated Security=True;database=Personal" providerName="System.Data.SqlClient"/>
    </connectionStrings> 

 No to the ps question will be fine.

Let me know how you get on.

Refering to your first post, did you do this:

This <customErrors> tag should then have its "mode" attribute set to "Off".