Last post Mar 27, 2010 09:11 PM by Rype69
Dec 30, 2005 12:26 AM|Wayward780|LINK
Dec 30, 2005 07:34 AM|Fredrik N|LINK
Did you use the Site Amin tool to create the user also?
The problem is that your user information is porbably not the same as you enter. So try to remove or add a new user and check if you can login with that user.
Dec 30, 2005 11:04 AM|Wayward780|LINK
Dec 30, 2005 11:37 AM|Wayward780|LINK
Dec 31, 2005 02:46 PM|Wayward780|LINK
Dec 31, 2005 06:53 PM|app_blocksGuy|LINK
post the code which is failing to work.......
Dec 31, 2005 09:14 PM|Wayward780|LINK
Jan 22, 2006 07:08 PM|akaKlen|LINK
Feb 10, 2006 11:16 PM|Efterhanden|LINK
Do you use a firewall?
I had trouble with my admin tool running, and later even the application running, because my firewall was interfering with something (i don't know what) happening behind-the-scenes while running an asp.net 2.0 application.
If you do have a firewall, I suggest try allowing ALL traffic and see if that helps.
Feb 11, 2006 07:22 AM|guillefd|LINK
I have the same problem. If I try to login typing my (NO-IP) DNS, it doesn´t autenticate the user (
Your login attempt was not successful. Please try again).. If I press F5 in VWD, it does the same. But If press ctrl +F5 ,
start with no debugging, it simply works! .. I really don´t know whats going on, If someone can just throw me a line, y would really apreciate.
Feb 13, 2006 02:32 PM|gmpeng|LINK
Have you got your ASPNETDB.mdf file under source control? I have found that the log in control doesn't work while this file is checked in. My current problem is that I can't get it to work at all once I deploy it to a remote
server... Hope this helps../
Feb 13, 2006 03:01 PM|cckiat|LINK
Feb 13, 2006 03:06 PM|cckiat|LINK
Feb 13, 2006 07:44 PM|gmpeng|LINK
I think the problems described here and unsolved in quite a few other posts on this forum, including
one from me, is that when you add a user using the Membership API it also stores the name of the application that was used to add it in the aspnet_Applications table. When a user is added from
a page running on the Visual Studio web server it is linked to a record in this table containing the name of the web site shown in solution explorer in VS.
When you run the site in IIS the application name seems to come from the IIS settings (on the Home or Virtual Directory tab in site properties).
If the application names do not match then the a user added on the VS server won't authenticate when the site and membership db are run in IIS.
To fix this I have updated the ApplicationName and LoweredApplicationName on my deployed database to match the IIS application name and all works well. I suppose ensuring that they are both
the same before adding any users or deploying the database would be an easier way to do things...
Hope this helps with your issues...
Architecture, Visualisation, Design, 3d, Application, Web, Windows, Development, Liverpool, UK
Feb 14, 2006 08:57 AM|gmpeng|LINK
The cause of the issue I describe above is described by Scott Guthrie here:
Feb 14, 2006 01:26 PM|erichar11|LINK
Feb 14, 2006 03:38 PM|erichar11|LINK
Feb 15, 2006 05:28 AM|gmpeng|LINK
I am not sure what could be causing your problem but maybe you could try a couple of things:
Also, this is a bit of a shot in the dark, are you using roles in your application and if so is that why the user isn't logging in?
Hope this helps...
Feb 22, 2006 02:43 PM|gabbyrozow|LINK
I have been struggling with this issue for a while myself.
I had the applicationName="/" attrubiute in my web.config, and only had one entry in the applications table in ASPNETDB.
I tried to change that value to "ECMA" (the name of my application) and also change the values in the database. I only have one application record and one user record in my database, but I still can't log in when the app is deployed to IIS.
Is there anything else that needs to be done?
I am pasting the complete web.config file here:
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
Visual Basic options:
Set strict="true" to disallow all data type conversions
where data loss can occur.
Set explicit="true" to force declaration of all variables.
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
Feb 23, 2006 06:45 AM|gabbyrozow|LINK
I tried to create a new website directly on the IIS instead of a file system web site. Using the default memebership settings, with nothing added to web.config, login worked.
Looking into the aspnetdb database, the application table contained one record with the applicationName set to "/", so it seems that the application works on IIS even when the application name in IIS is different from the application name in the database.
So now I need to see what happens to a web site that was created directly under IIS, when it is transferred to a different machine. If this works, then at least I know that I can continue developing and hope to find a solution to this problem later on.
Feb 23, 2006 10:21 PM|gmpeng|LINK
It certainly is confusing. The way I initially found out what was going on was to add a 'create user' page outside of the area of the site that required authentication. I uploaded it to IIS, created a user while the site was
running on the server rather than my dev machine, and then examined the aspnetdb to see what had been added. It was then that I realised that the application names didn't match.
Perhaps you could try this and see if it helps you diagnose your issue...
Mar 27, 2010 09:11 PM|Rype69|LINK
I had this issue and I fixed it by replacing this code in the web.config
With this code:
I hope this helps,