G
Guest
Hi Everyone,
I've got an issue that I hope you might be able to help with. If you know
what is causing this problem, please let me/us know. If you also happen to
know what to do to fix it, even better!
Here is the situation:
I created an application on a hosted server running ASP.NET 2.0 and a SQL
Server 2005 instance of a database.
I ran ASPNET_REGSQL -C (connectionString) on the hosted DB. It ran and
created the environment. I verified this by checking out the db.
I run this great app
(http://www.code-magazine.com/Article.aspx?quickid=0511031) and made some
small changes in the web.config so that it attached to the hosted db, and
created an Application, a User account, a Role, and then attached the Role to
the User.
I then checked the db to make sure that the data was in there. Indeed, the
data was in the right places in the hosted db.
So far, I think, everything looks good.
Here is what is strange, when using the login control and pointing the
web.config to the same database, the user is not recognised. The app doesn't
crash, it only says that the login is incorrect. If I change the connection
string in the web.config to a password that doesnt work, the app crashes,
causing me to think that the connectionstring is valid, and that the app is
making the connection. For some reason though, even though the user *IS* in
the database, it is not being recognised and login cannot happen.
I wonder if somehow the Application has anything to do with it? Does the
login control need to know which Application the User belongs to in the DB?
If so, how can I tell it? If it could be anything else, including this,
please let me know. I'm a bit stumped.
Thank you in advance,
Michael
I've got an issue that I hope you might be able to help with. If you know
what is causing this problem, please let me/us know. If you also happen to
know what to do to fix it, even better!
Here is the situation:
I created an application on a hosted server running ASP.NET 2.0 and a SQL
Server 2005 instance of a database.
I ran ASPNET_REGSQL -C (connectionString) on the hosted DB. It ran and
created the environment. I verified this by checking out the db.
I run this great app
(http://www.code-magazine.com/Article.aspx?quickid=0511031) and made some
small changes in the web.config so that it attached to the hosted db, and
created an Application, a User account, a Role, and then attached the Role to
the User.
I then checked the db to make sure that the data was in there. Indeed, the
data was in the right places in the hosted db.
So far, I think, everything looks good.
Here is what is strange, when using the login control and pointing the
web.config to the same database, the user is not recognised. The app doesn't
crash, it only says that the login is incorrect. If I change the connection
string in the web.config to a password that doesnt work, the app crashes,
causing me to think that the connectionstring is valid, and that the app is
making the connection. For some reason though, even though the user *IS* in
the database, it is not being recognised and login cannot happen.
I wonder if somehow the Application has anything to do with it? Does the
login control need to know which Application the User belongs to in the DB?
If so, how can I tell it? If it could be anything else, including this,
please let me know. I'm a bit stumped.
Thank you in advance,
Michael