Re: Problems deploying website with membership features from XP to 2003 (take2)

I managed to get a little further ...

in my web.config I was missing the <clear/> tag that solved the Parser Error Message: still could not successfully log on a user .. further blog readings gave me the hint to ensure that the mssql2005.. user account had persmissions in the directory where APSNETDB sat.

Everything worked fine then .. until I changed the port number that the website listens on .. and now nothing I seem to to do will allow me to authenticate a user.

I set the access on the directory to allow all users and that part seems to work (no more redirection to login.aspx) but it will not recognise the users on the 2003 box only the XP ... <hair turning greyer by the hour>

Hello Howard,

I tried adding this by copying this from machine.config to web.config
which
has applicationName="/" field in it
<membership>
<providers>
<add name="AspNetSqlMembershipProvider"
type="System.Web.Security.SqlMembershipProvider,
System.Web,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="LocalSqlServer"
enablePasswordRetrieval="false"
enablePasswordReset="true"
requiresQuestionAndAnswer="true"
applicationName="/"
requiresUniqueEmail="false"
passwordFormat="Hashed"
maxInvalidPasswordAttempts="5"
minRequiredPasswordLength="7"
minRequiredNonalphanumericCharacters="0"
passwordAttemptWindow="10"
passwordStrengthRegularExpression="" />
</providers>
</membership>
knowing that sometimes you can overide whats in the config files with
whats in the web.config ... again on my Dev box it all works fine but
on 2003 it spits back

Parser Error Message: The entry 'AspNetSqlMembershipProvider' has
already been added.

Source Error:

Line 24: <membership>
Line 25: <providers>
Line 26: <add name="AspNetSqlMembershipProvider"
Line 27: type="System.Web.Security.SqlMembershipProvider,
System.Web,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
Line 28: connectionStringName="LocalSqlServer"
so I'm guessing it doesnt overide like I thought ...
And I'm thinking if I change the applicationName in machine.config
then I
will only ever be able to have the one web app ... also the website
application
name in the IIS managment snap in (properties) is blank, the
application
name in ASPNETDB is / and the current Appname in the 2003
machine.config
providers section is "/" .. I thought this was ok ..
Still lost :-(

I believe you can specify 'ApplicationName' in web.config in the
Providers <add> element. Did you try that?

HTH,

Howard Hoffman



.