Re: SQL 2005 Login
- From: "Andy Ball" <ng@xxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 11 Mar 2006 09:55:10 -0000
Buc,
Note that in SQL 2005 SQL Logins are case sensitive.
Blog article below has a good table on the different Error States in a 18456
error state recorded in the SQL Server ErrorLog
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
cheers,
Andy.
<Buc> wrote in message news:OU9Y6ZIRGHA.256@xxxxxxxxxxxxxxxxxxxxxxx
I am very frusted.. I have a vb.net app that used to work fine with SQL
2000.
I installed a new server with SQL 2005, and the new vb.net app fails login
from any workstation. Every username I create in SQL fails login from
vb.net app, EXCEPT sa. I guess the app is OK since just replacing the
username and password in the connection string with sa clears the problem
up. What do I have to do to make a single user work. I have 2 diff DB
servers and the same happens on both. Here's what I've done so far, is
this wrong? What else do I need to do?
TRIED THIS:
Created a user 'testuser' in the management console under databases >
security >logins
( I even made the user a sysadmin, if that makes any difference)
Went under the TESTDB > SECURITY >LOGINS , made sure he was there and made
him under the general tab a db_owner.
All I get is login failed for user 'testuser' from my vb.net app, of
course replacing the user/pass with the sa account connects fine. I would
rather not use the sa account credentials from my remote app.
TRIED THIS:
I then tried this did the same stuff above with a new user called
'testuser1' but made hime a local windows user on the standalaone DB
server. No effect, same error...
Ideas are appreciated.. This is driving me nuts..
Thanks BUC
.
- References:
- SQL 2005 Login
- From: Buc
- SQL 2005 Login
- Prev by Date: Re: User Permissions disappearing
- Next by Date: Re: Exporting Logins
- Previous by thread: SQL 2005 Login
- Next by thread: Re: Exporting Logins
- Index(es):
Relevant Pages
|