User membership problems

Sorry to post another question about user/membership database problems. I tried for the past 5 days to sort the problem out by searching the archives and ploughing through ASP.NET 2.0 Unleashed, but know I have hit a brick wall. Any help would be most appreciated.

I have a simple website that uses the user and role features of ASP.NET 2.0. I am developing my website using VS2008. In my web.config file I have the following entries:

<authentication mode='Forms' />
<roleManager enabled='true' />
<membership defaultProvider='AspNetSqlRoleProvider'>
<providers>
<clear />
<add
name='AspNetSqlRoleProvider'
type='System.Web.Security.SqlMembershipProvider'
minRequiredNonalphanumericCharacters='0'
maxInvalidPasswordAttempts='3'
passwordAttemptWindow='60'
passwordFormat='Clear'
connectionStringName='LocalSqlServer' />
</providers>
</membership>

and my connection strings are:

<connectionStrings>

<!--
Live Connection Strings
-->

<remove name='LocalSqlServer'/>
<add name='ConnectionStringPublications' connectionString='Data Source=tcp:sql2k510.discountasp.net;Initial Catalog=SQL2005_427773_publications;User ID=SQL2005_427773_publications_user;Password=XXXXX;'
providerName='System.Data.SqlClient' />
<add name='LocalSqlServer' connectionString='Data Source=tcp:sql2k510.discountasp.net;Initial Catalog=SQL2005_427773_aspnetdb;User ID=SQL2005_427773_aspnetdb_user;Password=XXXXX;'
providerName='System.Data.SqlClient' />


</connectionStrings>

The aspnetdb database was created locally and set-up using the aspnet_regsql tool. It has been uploaded to my DASP site and attached using the SQL Toolkit.

Before uploading the db I created two users (bertie and family) and three roles (administrator, family and member). Bertie is an administrator role and family is a family role - idea being that I can administer all areas of my site, family can view the family area and registered members can view my academic areas.

Anyway, logging-on as 'bertie' or 'family' fails.

Another 'feature' that doesn't happen when the website is run locally is that when a user tries to register as a new user by visiting createNewUser.aspx a pop-up appears asking them to confirm a password change (along with a list of user names). The code in the createNewUser.aspx page is:

<%@ Page Language='VB' MasterPageFile='~/MasterPage.master' Title='Become a member of KurtRichardson.com' %>

<script runat='server'>

Sub CreateUserWizard1_SendingMail(ByVal sender As Object, ByVal e As MailMessageEventArgs)
Dim user As MembershipUser = Membership.GetUser(CreateUserWizard1.UserName)
Dim code As String = user.ProviderUserKey.ToString
e.Message.Body = e.Message.Body.Replace('<%ConfirmationCode%>', code)
End Sub

</script>

<asp:Content ID='Content1' ContentPlaceHolderID='head' runat='Server'>
</asp:Content>
<asp:Content ID='Content2' ContentPlaceHolderID='ContentPlaceHolder1' runat='Server'>
<asp:SiteMapPath ID='SiteMapPath1' runat='server' />


<div id='divDataDisplay' class='tabBody'>
<h1>
Create a New User</h1>
<asp:CreateUserWizard ID='CreateUserWizard1' runat='server' BackColor='#FFFBD6' BorderColor='#FFDFAD'
BorderStyle='Solid' BorderWidth='1px' Font-Names='Verdana' Font-Size='0.8em'
CompleteSuccessText='A confirmation email containing your new password has been sent to your email address. Click 'continue' to go to the membership confirmation page.'
DisableCreatedUser='true' ContinueDestinationPageUrl='~\confirmCode.aspx' OnSendingMail='CreateUserWizard1_SendingMail'>
<SideBarStyle BackColor='#990000' Font-Size='0.9em' VerticalAlign='Top' />
<SideBarButtonStyle ForeColor='White' />
<ContinueButtonStyle BackColor='White' BorderColor='#CC9966' BorderStyle='Solid'
BorderWidth='1px' Font-Names='Verdana' ForeColor='#990000' />
<NavigationButtonStyle BackColor='White' BorderColor='#CC9966' BorderStyle='Solid'
BorderWidth='1px' Font-Names='Verdana' ForeColor='#990000' />
<HeaderStyle BackColor='#FFCC66' BorderColor='#FFFBD6' BorderStyle='Solid' BorderWidth='2px'
Font-Bold='True' Font-Size='0.9em' ForeColor='#333333' HorizontalAlign='Center' />
<CreateUserButtonStyle BackColor='White' BorderColor='#CC9966' BorderStyle='Solid'
BorderWidth='1px' Font-Names='Verdana' ForeColor='#990000' />
<TitleTextStyle BackColor='#990000' Font-Bold='True' ForeColor='White' />
<MailDefinition From='[email protected]' BodyFileName='codeConfirmation.htm'
IsBodyHtml='true' Subject='Registration Confirmation for KurtRichardson.com' />
</asp:CreateUserWizard>
</div>
</asp:Content>

Needless to say, all this works fine when run locally, but does not work when uploaded to DASP.

One last question - can I view db data via the DASP control panel, or do I need to install some other software to do this.

Many thanks indeed for any assistance you can provide.

Kurt

 

I turned my brain on and looked that over several times and still can't think of anything right off hand.
The only thing I seem to keep speculating on is that there must be something else in the web.config causing the remote problem.

I get a kick out of your username by the way.
Salute,
Mark Wisecarver

 

Hi Mark

I'm glad to hear the solution to my problem is not too obvious - I would feel a bit of a wally if it was /emoticons/wink.gif

Here is the entire web.config file if that helps. As I'm running VS2008, maybe more is thrown in here by default than is really needed.



<configuration>

<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>


<appSettings/>
<connectionStrings>

<!--
Live Connection Strings
-->


<remove name='LocalSqlServer'/>
<add name='ConnectionStringPublications' connectionString='Data Source=tcp:sql2k510.discountasp.net;Initial Catalog=SQL2005_427773_publications;User ID=SQL2005_427773_publications_user;Password=XXXXXXX;'
providerName='System.Data.SqlClient' />
<add name='LocalSqlServer' connectionString='Data Source=tcp:sql2k510.discountasp.net;Initial Catalog=SQL2005_427773_aspnetdb;User ID=SQL2005_427773_aspnetdb_user;Password=XXXXXXX;'
providerName='System.Data.SqlClient' />


<!--
Development Connection Strings
-->

<!--
<remove name='LocalSqlServer'/>
<add name='ConnectionStringPublications' connectionString='Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\publications.mdf;Integrated Security=True;User Instance=True'
providerName='System.Data.SqlClient' />
<add name='LocalSqlServer' connectionString='data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true'
providerName='System.Data.SqlClient'/>
-->

</connectionStrings>

<system.web>

<compilation debug='false' strict='false' explicit='true'>

<assemblies>
<add assembly='System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089'/>
<add assembly='System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>
<add assembly='System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089'/>
<add assembly='System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089'/>
</assemblies>

</compilation>
<pages theme='Berties_Default'>
<namespaces>
<clear />
<add namespace='System' />
<add namespace='System.Collections' />
<add namespace='System.Collections.Generic' />
<add namespace='System.Collections.Specialized' />
<add namespace='System.Configuration' />
<add namespace='System.Text' />
<add namespace='System.Text.RegularExpressions' />
<add namespace='System.Linq' />
<add namespace='System.Xml.Linq' />
<add namespace='System.Web' />
<add namespace='System.Web.Caching' />
<add namespace='System.Web.SessionState' />
<add namespace='System.Web.Security' />
<add namespace='System.Web.Profile' />
<add namespace='System.Web.UI' />
<add namespace='System.Web.UI.WebControls' />
<add namespace='System.Web.UI.WebControls.WebParts' />
<add namespace='System.Web.UI.HtmlControls' />
</namespaces>

<controls>
<add tagPrefix='asp' namespace='System.Web.UI' assembly='System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>
<add tagPrefix='asp' namespace='System.Web.UI.WebControls' assembly='System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>
</controls>

</pages>


<authentication mode='Forms' />
<roleManager enabled='true' />
<membership defaultProvider='AspNetSqlRoleProvider'>
<providers>
<clear />
<add
name='AspNetSqlRoleProvider'
type='System.Web.Security.SqlMembershipProvider'
minRequiredNonalphanumericCharacters='0'
maxInvalidPasswordAttempts='3'
passwordAttemptWindow='60'
passwordFormat='Clear'
connectionStringName='LocalSqlServer' />
</providers>
</membership>

<httpHandlers>
<remove verb='*' path='*.asmx'/>
<add verb='*' path='*.asmx' validate='false' type='System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>
<add verb='*' path='*_AppService.axd' validate='false' type='System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>
<add verb='GET,HEAD' path='ScriptResource.axd' type='System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35' validate='false'/>
</httpHandlers>
<httpModules>
<add name='ScriptModule' type='System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>
</httpModules>


</system.web>

<system.codedom>
<compilers>
<compiler language='c#;cs;csharp' extension='.cs' warningLevel='4'
type='Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'>
<providerOption name='CompilerVersion' value='v3.5'/>
<providerOption name='WarnAsError' value='false'/>
</compiler>
<compiler language='vb;vbs;visualbasic;vbscript' extension='.vb' warningLevel='4'
type='Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'>
<providerOption name='CompilerVersion' value='v3.5'/>
<providerOption name='OptionInfer' value='true'/>
<providerOption name='WarnAsError' value='false'/>
</compiler>
</compilers>
</system.codedom>

<!--
The system.webServer section is required for running ASP.NET AJAX under Internet
Information Services 7.0. It is not necessary for previous version of IIS.
-->
<system.webServer>
<validation validateIntegratedModeConfiguration='false'/>
<modules>
<remove name='ScriptModule' />
<add name='ScriptModule' preCondition='managedHandler' type='System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>
</modules>
<handlers>
<remove name='WebServiceHandlerFactory-Integrated'/>
<remove name='ScriptHandlerFactory' />
<remove name='ScriptHandlerFactoryAppServices' />
<remove name='ScriptResource' />
<add name='ScriptHandlerFactory' verb='*' path='*.asmx' preCondition='integratedMode'
type='System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>
<add name='ScriptHandlerFactoryAppServices' verb='*' path='*_AppService.axd' preCondition='integratedMode'
type='System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>
<add name='ScriptResource' preCondition='integratedMode' verb='GET,HEAD' path='ScriptResource.axd' type='System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35' />
</handlers>
</system.webServer>


<runtime>
<assemblyBinding xmlns='urn:schemas-microsoft-com:asm.v1'>
<dependentAssembly>
<assemblyIdentity name='System.Web.Extensions' publicKeyToken='31bf3856ad364e35'/>

</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name='System.Web.Extensions.Design' publicKeyToken='31bf3856ad364e35'/>

</dependentAssembly>
</assemblyBinding>
</runtime>

<system.net>
<mailSettings>
<smtp from='[email protected]'>
<network host='XXXXXXX' password='XXXXXXX' port='587' userName='XXXXXXX' />
</smtp>
</mailSettings>
</system.net>
</configuration>

One other strange 'feature' of the 'live' version is that the list of usernames that came up when I was asked to confirm the password change (when I was trying to create a user) where not even in the database I had uploaded, but were in an older version (I rebuilt aspnetdb locally from scratch using aspnet_regsql - which should have cleared the db shouldn't it?). Could there be a problem with the DASP DB attachment process or some caching issue? I've assumed that whenever I have updated (attached) a revised version of aspnetdb that all the old information was overwritten.

Many thanks, Kurt

PS I acquired the username from an administrative chap I worked with in my first professional job who was essentially ridiculing me for having a PhD, but I kinda liked it!

 

It does appear the problem is right there in front of us Professor.
Sorry to hear you picked up that name as a joke because it is cool bro.

Anyway, looks like locally everything is using the Development connection to the Express, disconnected, database.

On the remote system that will fail, only the SQL Server database will be able to succeed.

For this to work everything in that local Express database will need to exist in your remote SQL Server DB, including the roles.

Don't fret, this is all common practice and only requires typical synchronization.
Salute,
Mark

P.S. It's my pleasure to offer assistance.
I'm just going nuts anyway, my three kids being home for Christmas break and all.

 

Well I suppose I shouldn't be surprised that the problem is in the area I have the least knowledge about, i.e., SQL DBs /emoticons/wink.gif I've been programming for 20+ years but somehow managed to avoid database work... until , that is, I discovered ASP.NET which I think is absolutely brilliant.. time to fill that knowledge deficit I suppose!

Can you let me know the details of a 'typical synchronization'? I thought I had done this when I uploaded the aspnetdb file and then attached it using the SQL Toolkit (and rewrote the connection strings), but clearly I approached this far too simplistically (or maybe it is simpler than I'm making it!).

Can I logon to the DASP SQL server remotely from within VS2008 and then always work with the live connection strings as opposed to using my local SQLEXPRESS server as I develop the application further?

Many thanks once again.... I've managed to talk my wife into entertaining the kids outside of the house today so that I can have some peace and quiet to resolve this /emoticons/wink.gif

TTFN, Kurt

 

Wow, 20+ years.
My background is in Electronics...
Started developing software in 1987 soI could better interface with Eproms.

The best tools for synchronizing the DB servers, IMHO, are the SQL Server Management tools.
There are some express versions of SQL Server tools out from Msft now but I never tested them.

If you don't have SQL Server locally, only Express, I'd suggest getting a developer copy.
They sell for under $50, Amazon, eBay, etc.

With the SQL Server management tools you get some very powerful control over remote and local synchronization.

I'm just offering tips, you can always do these things the hard way with SQL strings.
http://msdn2.microsoft.com/en-us/sqlserver/aa336366.aspx

Oh...Lookie here
Download the latest release of SQL Server 2008 Community Technology Preview
http://msdn2.microsoft.com/en-us/sqlserver/default.aspx

 

Thanks again Mark,

I have SQL Server Unleashed and SQL 2005 winging their way to me from Amazon. Hopefully I'll be able to extract what I need to resolve this issue.

Do you happen to know what the servername is for DASP SQL Server? I've been trying to add it to the server manager in VS, but with no luck. I tried sql2k510.discountasp.net (straight from my connection string) with the username and password from the same cstring.

Cheers, Kurt

PS It started for me with a C64 back in '82 - great days!

 

ProfNimrod said...

Do you happen to know what the servername is for DASP SQL Server? I've been trying to add it to the server manager in VS, but with no luck. I tried sql2k510.discountasp.net (straight from my connection string) with the username and password from the same cstring.


That hostname looks correct. You can always double check here: https://my.discountasp.net/mssql2005-manager.aspx

mjp
---
DiscountASP.NET

 

Aren't you still at the point where the focus is synchronizing the remote and localdata/objects?
Salute,
Mark

 

Thanks mjp for the confirmation - I was simply trying to the DASP server as a server in CS2008 Server Explorer, rather than just a connection to either of my DASP hosted databases.

However, now I'm totally confused. I decided to make things a little simpler and not bother with local development connection strings and only work the with remote DBs on the DASP server. So my connection strings are:

<connectionStrings>

<clear/>
<remove name='LocalSqlServer'/>
<add name='ConnectionStringPublications' connectionString='Data Source=tcp:sql2k510.discountasp.net;Initial Catalog=SQL2005_427773_publications;User ID=SQL2005_427773_publications_user;Password=caRo1223liNe;'
providerName='System.Data.SqlClient' />
<add name='LocalSqlServer' connectionString='Data Source=tcp:sql2k510.discountasp.net;Initial Catalog=SQL2005_427773_aspnetdb;User ID=SQL2005_427773_aspnetdb_user;Password=caRo1223liNe;'
providerName='System.Data.SqlClient' />

</connectionStrings>

The confusion arises because I can run my website locally and login into it fine. I can even manage the users and roles via the ASP.NET configuration utility built into VS - these actions are being performed directly with the DASP hosted DBs on the DASP SQL Server. However, if I try to do the same thing from the uploaded site - which has exactly the same providers and connection strings, the same login attempt fails. I cannot find anything in my code that would explain the difference in behavior .

Any thoughts? My provider entry in web.config is:

<authentication mode='Forms' />
<roleManager enabled='true' />
<membership defaultProvider='AspNetSqlRoleProvider'>
<providers>
<clear />
<add
name='AspNetSqlRoleProvider'
type='System.Web.Security.SqlMembershipProvider'
minRequiredNonalphanumericCharacters='0'
maxInvalidPasswordAttempts='3'
passwordAttemptWindow='60'
passwordFormat='Clear'
connectionStringName='LocalSqlServer' />
</providers>
</membership>

Many thanks, Kurt

 

Bugger - can the forum moderator please remove or revise my previous post to remove the connection string password... cheers, Kurt

 

Could the issue be anything to do with the fact that I'm running IIS7 on my local machine as opposed to IIS6 (which is on the DASP server)?

Thnx, K

 

Hi Mark


Yes that was the plan... however, in the process of installing SQL 2008 Developer everything went to s*** and I currently do not have any version of SQL server running - apparently this isn't a particularly rare occurence. So I am now going through the process of figuring out how to get SQL Server back up and running locally.


However, while I messed with this I thought I'd try working only with the remote DASP Databases and remove the connections to local data sources altogether. What I can't understand is why this should work perfectly well and yet if I try to access the same remote DASP hosted databases from the 'live' DASP hosted website none of the user/role functions work. I can add users and roles directly to the remote DBs, both via the local website and the ASP.NET Configuration tool.


It would be useful for me to understand what you think synchronization actually is and what it will achieve, so that I can understand why the local website with remote DBs works fine, but the remote website with remote DBs fails. What is it in the DASP hosted DB that prevents it from being manipulated from the DASP hosted website. I'm sure it is all very simple, but I just haven't gotten my head into the right 'paradigm' yet ;-) I want to be able to understand your advice rather than just act on it.


Apologies for dragging this on...


Cheers, Kurt

 

Believe me I know how this can be, so I'm shoulder to shoulder with ya bro.
By the way, check your private messages. (Up above...)

There are two specific things that can be causing this. (Local to Remote)

1) Synchronizing the data objects and data.

2) The root web.config
Boy are there a lot of things that can go wrong there.
Connection string inheritance.
Having worked with the same code on a local express DB can really be hard to get rid of.

Now the juicy part...
You can avoid this by using your remote DASP SQL Server at all times, local and remote.
Once you get the SQL Server tools on your system you can override some of that. (Configuration tools.)

You can find a few of my previous posts, helping others, on how to trick your pages to always use the remote DB server too.
Add, Clearand Remove commands in your web.config connection area.
Those are very helpful...SQL Server Express is, well, I'll just be nice and call it pesky.
Still here for ya bro,
Mark

 

I certainly appreciate the support Mark...


I am nearly back to the point SQL server-wise before I tried to install SQL 2008... Before I do too much more I think I will install the full SQL 2005 (arriving from Amazon Monday morning - how I love Amazon - I wish UPS delivered on a Sat!), and then start from scratch... at least then we can remove the possible SQL Express issues from the equation. You never know,just the move from Express may be sufficient! Fingers crossed...


Have a great weekend, Kurt

 

In case anyone is interested I finally figured out this niggle of a problem. I was browsing through the aspnetdb data and noticed that there is an Applications table that listed two applications with different applications IDs (apid) - one for the remote (DASP) live application and one for the local development version (I have been accessing the db from both locales). Anyway, it seems that if a user is created it also has the apid associated with it and so if you try and login from the other version of the app (which has a different apid) the login fails. It seems that you can only login from the machine from which the user account was originally established.


After removing the local apid (and keeping only the hosted apid) and associating each user with the hosted apid everything worked fine. Is this the same thing that is acheived when syncing dbs? I don't know... but now that I have my administrator account and all the roles set-up, all future users will only be created via the hosted version.


Thanks for the tips and advice along the way, happy new year,


Kurt

 

Happy New Year bro.

You're a very kind person for following up on this...Thanks.
Salute,
Mark