Login works in DEV but not on server

Hi.My login validation works on my dev machine, but on the discountasp.net server the same code always fails the login. Here is my code:

Connection string:



<connectionStrings>
<remove name="LocalSqlServer"/>
<add name="LocalSqlServer" connectionString="Data Source=tcp:sql2k504.discountasp.net;Integrated Security=false;Initial Catalog=SQL2005_267790_ppi;User ID=SQL2005_267790_ppi_user;Password=*******" providerName="System.Data.SqlClient"/>
</connectionStrings>

Other web.config stuff:

<roleManager enabled="true" />


<authentication mode="Forms">
<forms name=".ASPXAUTH_PPI"
loginUrl="Login.aspx"
protection="All"
timeout="30"
path="/"
requireSSL="false"
slidingExpiration="true"
cookieless="UseDeviceProfile" />
</authentication>
<membership defaultProvider="PpiProvider">
<providers>
<clear />
<add name="PpiProvider"
minRequiredPasswordLength="5"
minRequiredNonalphanumericCharacters="0"
connectionStringName="LocalSqlServer"
type="System.Web.Security.SqlMembershipProvider"/>
</providers>
</membership>

from login.aspx.cs:

 

Scott Gu has a tip on his blog that sounds like your problem
here is the link



Cause:</o>
</o>
The reason this usually happens is because a membership (or roles or profile) provider has been added in the application?s web.config file ? but without an applicationName attribute being specified (assume below that the applicationName in bold was missing):
</o>
<membership></o>
<providers></o>
<clear/></o>
<add name="AspNetSqlMembershipProvider"</o>
type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"</o>
connectionStringName="LocalSqlServer"</o>
enablePasswordRetrieval="false"</o>
enablePasswordReset="true"</o>
requiresQuestionAndAnswer="true"</o>
requiresUniqueEmail="false"</o>
passwordFormat="Hashed"</o>
maxInvalidPasswordAttempts="5"</o>
minRequiredPasswordLength="7"</o>
minRequiredNonalphanumericCharacters="1"</o>
passwordAttemptWindow="10"</o>
passwordStrengthRegularExpression="" </o>
applicationName="/" </o>
/></o>
</providers></o>
</membership>
</o>
When no applicationName attribute is configured, ASP.NET uses the application vroot path within the web-server to automatically calculate the applicationName to use when adding data to an ASP.NET Application Service database. To see this in action, you can open up your ASPNETDB database, and look within the aspnet_Applications table:
</o>

kevinasp.com

 

Thanks a lot! That was the problem. Good blog, too.

Dan

 

I?ve been tearing my hair out for two days, trying to solve this same problem on my site, and this was the fix I needed. Thanks a lot!
</o>Lar