TheFlash
04-23-2007, 06:09 AM
I have implemented a section of my site to be password protected. I used the asp web admin tool to set up and configure the data, then deployed it to our live SQL Server 2000 box and amended the web.config file for the site to point to the new directory. I then deleted the old aspnetdb file (to double check it wasn’t ignoring the new config changes) and when testing it from my dev machine, I can log in fine. However, when I try it from any other machine the process doesn’t work.
I have added
<membership defaultProvider="SqlProvider" userIsOnlineTimeWindow="15">
<providers>
<clear />
<add
name="SqlProvider"
type="System.Web.Security.SqlMembershipProvider"
connectionStringName="LocalSqlServer"
applicationName="MyApplication"
enablePasswordRetrieval="false"
enablePasswordReset="true"
requiresQuestionAndAnswer="true"
requiresUniqueEmail="true"
passwordFormat="Hashed" />
</providers>
</membership>
To the relevant section and verified the data was copied across when i deployed it to the live server. I cannot log in at all, it just tells me Your login attempt was not successful. Please try again. even though the details are correct.
If I change the connection string to an invalid database name it does moan that It cannot find the database, so I know its connecting to the right database to authenticate the user, but for some reason its not happy with the login, even though its valid.
Can anyone suggest why this isn’t working?
I have added
<membership defaultProvider="SqlProvider" userIsOnlineTimeWindow="15">
<providers>
<clear />
<add
name="SqlProvider"
type="System.Web.Security.SqlMembershipProvider"
connectionStringName="LocalSqlServer"
applicationName="MyApplication"
enablePasswordRetrieval="false"
enablePasswordReset="true"
requiresQuestionAndAnswer="true"
requiresUniqueEmail="true"
passwordFormat="Hashed" />
</providers>
</membership>
To the relevant section and verified the data was copied across when i deployed it to the live server. I cannot log in at all, it just tells me Your login attempt was not successful. Please try again. even though the details are correct.
If I change the connection string to an invalid database name it does moan that It cannot find the database, so I know its connecting to the right database to authenticate the user, but for some reason its not happy with the login, even though its valid.
Can anyone suggest why this isn’t working?