Re: Custom membership provider problem

On Sat, 17 Dec 2005 03:04:17 -0000, "John" <John@xxxxxxxxxxxxxxxxxxxx>
wrote:

SQL server 2005 does not install with the TCP/IP protocol turned on.
You must turn it on to cure this problem.

>Hi
>
>I was working fine with create user wizard and the default membership
>provider. I have now customised the membership provider as per attached
>web.config. The create user wizard picks up the custom membership provider
>fine and removes the security question/answer fields as designated in the
>custom provider.
>
>The problem is that when I try to create a new user in the create user
>wizard by entering the info and pressing the 'create user' button, I get the
>below error.
>
>What am I doing wrong and how can I fix it? I created the aspnetdb db using
>the aspnet_regsql.exe tool.
>
>Thanks
>
>Regards
>
>
>Server Error in '/Events' 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: SQL Network Interfaces, error: 25 - Connection string is not
>valid)
>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: SQL
>Network Interfaces, error: 25 - Connection string is not valid)
>
>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: SQL Network Interfaces, error: 25 -
>Connection string is not valid)]
> System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
>exception, Boolean breakConnection) +734979
> System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
>stateObj) +188
> System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
>Boolean& failoverDemandDone, String host, String failoverPartner, String
>protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean
>encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection
>owningObject, Boolean aliasLookup) +820
> System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
>owningObject, SqlConnectionString connectionOptions, String newPassword,
>Boolean redirectedUserInstance) +628
> System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
>identity, SqlConnectionString connectionOptions, Object providerInfo, String
>newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
>+170
> System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
>options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
>owningConnection) +130
> System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
>owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
> System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
>owningObject) +424
> System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
>owningObject) +66
> System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
>owningObject) +496
> 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.DataAccess.SqlConnectionHolder.Open(HttpContext context,
>Boolean revertImpersonate) +84
> System.Web.DataAccess.SqlConnectionHelper.GetConnection(String
>connectionString, Boolean revertImpersonation) +197
> System.Web.Security.SqlMembershipProvider.CreateUser(String username,
>String password, String email, String passwordQuestion, String
>passwordAnswer, Boolean isApproved, Object providerUserKey,
>MembershipCreateStatus& status) +3612
> System.Web.UI.WebControls.CreateUserWizard.AttemptCreateUser() +305
> System.Web.UI.WebControls.CreateUserWizard.OnNextButtonClick(WizardNavigationEventArgs
>e) +105
> System.Web.UI.WebControls.Wizard.OnBubbleEvent(Object source, EventArgs
>e) +453
> System.Web.UI.WebControls.CreateUserWizard.OnBubbleEvent(Object source,
>EventArgs e) +149
> System.Web.UI.WebControls.WizardChildTable.OnBubbleEvent(Object source,
>EventArgs args) +17
> System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35
> System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115
> System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
>+163
> System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
>eventArgument) +7
> System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
>sourceControl, String eventArgument) +11
> System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
> System.Web.UI.Page.ProcessRequestMain(Boolean
>includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102
>
>
>
>
>
>--------------------------------------------------------------------------------
>
>Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET
>Version:2.0.50727.42
>
.