Login control does not work... Why?

[RedEye]

Hello,

Here is the problem. I have two sites both of which use the asp.net v2 login
controls.

Both sites are coded identicaly including the config file.

There is only one thing that is different which is the location of the
database.

One which is on SQL 2000 and one on SQL 2005.

The site that uses SQL 2005 does not seem to work.
I have used the web site config tool to add users and roles.
Once I was finished I checked to see if the users were added to the database
and they were.

Now I try to log into the site and I get the "Your login attempt was not
successful. Please try again." error.

You can't debug the control so how do I figure out what is going wrong? What
could be going wrong?

Thanks!

 

[dave]

I am also having a problem with the no code login control. I am using
the mysite sdk and every thing works greate in the test server
environment but when I publish to the IIS webserver on the same machine
I experience the same problems that "Redeye" gets, only I get Red
something else. If we could see the code we could debug it. Is there
any other way to debug it?Please help Microsoft

 

[Scott Allen]

Do you have SQL Server 2005 profiling tools installed? The first piece
I'd check is to run SQL Profiler and watch to make sure the correct
database is being hit. I'd also double check the password settings
(hashed versus plain text, etc. ).

 

[Tim Cartwright]

Silly question, but can you make sure you are not using a trusted
connection?

 

[Scott Allen]

Silly question, but can you make sure you are not using a trusted
connection?

From code I'm not aware of any property. I'm guessing you'd have to
parse the connection string and look for "Trusted Connection".

 

[gdsmith]

I have the same problem (I'm using the release version of ASP.NET 2.0
from within VS 2005). I've configured my web app to work with a SQL
Server 2000 database as per 'How To: Use Forms Authentication with SQL
Server in ASP.NET 2.0'
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/paght000022.asp),
and I've set up a trace using Profiler to check that the DB is being
hit. The results are that it is NOT being hit by the Login control, bit
it IS being hit by the PasswordRecovery control. Presumably some sort
of config glitch. Anyone any ideas?

Cheers - Graham

 

[gdsmith]

Problem sorted - I had some (test) code in the Login1_Authenticate
event. Removing it got things working.

 

[Scott Allen]

Problem sorted - I had some (test) code in the Login1_Authenticate
event. Removing it got things working.

Glad you caught that - I had no ideas!