SQL Membership Provider Problem

[GaryDean]

My ASP.Net application, that uses the SQL Membership Provider, runs fine on
my development box (server2003) as long as I use the standard provider.
But, in anticipation of deployment to other servers I am attempting to
register another provider instance.

I'm not sure this is the right deployment choice but I haven't found any
guidelines on how to best deploy apps using the SQL Membership provider.

I first attached C:\Inetpub\wwwroot\PTPEmployment\App_Data\ASPNETDB .MDF to
my local SQL Server instance and renamed the data base to PTPSecurity
(because that's a shorter name).

I then added the following to my web.config....

a connection string in the connection strings section.....
<add name="AUTHConnectionString" connectionString="Data
Source=DEVSERVER2003;Initial Catalog=PTPSecurity;Integrated Security=True"
providerName="System.Data.SqlClient"/>

and.....
<membership defaultProvider="SqlProvider">
<providers>
<clear />
<add connectionStringName="AUTHConnectionString" applicationName="/"
name="SqlProvider" type="System.Web.Security.SqlMembershipProvider" />
</providers>
</membership>

Now, the applications runs for some things and the asp.net website
configuration utility will run for some things. But both also get the
following error with some things withing the provider database are accessed.
For instance if I try to access roles in either the application or the
utility I get the error pasted below.

#1 can anyone tell my why this is happening and #2 how are we supposed to
deploy apps with the ASPNETDB.MDF database?

The following message may help in diagnosing the problem: Cannot open user
default database. Login failed. Login failed for user
'DEVSERVER2003\Administrator'. at
System.Web.Administration.WebAdminPage.CallWebAdmi nHelperMethod(Boolean
isMembership, String methodName, Object[] parameters, Type[] paramTypes) at
ASP.security_roles_manageallroles_aspx.BindGrid() at
ASP.security_roles_manageallroles_aspx.Page_Load() at
System.Web.Util.CalliHelper.ArglessFunctionCaller( IntPtr fp, Object o) at
System.Web.Util.CalliEventHandlerDelegateProxy.Cal lback(Object sender,
EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)

thanks,
Gary

[sloan]

http://weblogs.asp.net/scottgu/archi...25/423703.aspx
<configuration>

<connectionStrings>

<remove name="LocalSqlServer"/>

<add name="LocalSqlServer" connectionString="Data
Source=localhost;Initial Catalog=appservicesdb;Integrated Security=True"
providerName="System.Data.SqlClient"/>

</connectionStrings>

</configuration>



"GaryDean" <Ga******@newsgroups.nospamwrote in message
news:ud**************@TK2MSFTNGP02.phx.gbl...

My ASP.Net application, that uses the SQL Membership Provider, runs fine
on my development box (server2003) as long as I use the standard provider.
But, in anticipation of deployment to other servers I am attempting to
register another provider instance.

I'm not sure this is the right deployment choice but I haven't found any
guidelines on how to best deploy apps using the SQL Membership provider.

I first attached C:\Inetpub\wwwroot\PTPEmployment\App_Data\ASPNETDB .MDF to
my local SQL Server instance and renamed the data base to PTPSecurity
(because that's a shorter name).

I then added the following to my web.config....

a connection string in the connection strings section.....
<add name="AUTHConnectionString" connectionString="Data
Source=DEVSERVER2003;Initial Catalog=PTPSecurity;Integrated Security=True"
providerName="System.Data.SqlClient"/>

and.....
<membership defaultProvider="SqlProvider">
<providers>
<clear />
<add connectionStringName="AUTHConnectionString" applicationName="/"
name="SqlProvider" type="System.Web.Security.SqlMembershipProvider" />
</providers>
</membership>

Now, the applications runs for some things and the asp.net website
configuration utility will run for some things. But both also get the
following error with some things withing the provider database are
accessed. For instance if I try to access roles in either the application
or the utility I get the error pasted below.

#1 can anyone tell my why this is happening and #2 how are we supposed to
deploy apps with the ASPNETDB.MDF database?

The following message may help in diagnosing the problem: Cannot open user
default database. Login failed. Login failed for user
'DEVSERVER2003\Administrator'. at
System.Web.Administration.WebAdminPage.CallWebAdmi nHelperMethod(Boolean
isMembership, String methodName, Object[] parameters, Type[] paramTypes)
at ASP.security_roles_manageallroles_aspx.BindGrid() at
ASP.security_roles_manageallroles_aspx.Page_Load() at
System.Web.Util.CalliHelper.ArglessFunctionCaller( IntPtr fp, Object o) at
System.Web.Util.CalliEventHandlerDelegateProxy.Cal lback(Object sender,
EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

thanks,
Gary

[Steven Cheng[MSFT]]

That sounds good.

Thanks for coming back and letting us know the result.

Have a good day!

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.