When trying to create a system DSN using ODBC on the client, I got this message:<BR><BR>Connection failed:<BR>SQLState: '28000'<BR>SQL Server Error: 18456<BR>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(domain name)(windows user name)'<BR><BR>Does anyone know what this means?Why this question is on an ASP.NET forum, I'm not sure...<BR><BR>Anyway, it means you don't have an account created on your SQL server based on your Windows login, or have that account setup wrong, or without appropriate access rights. Remember that when you create a user account, you not only have to give access rights to each database, but also must specify what permissions are available on each table. <BR><BR>Using your windows login to access SQL can be a dangerous practice. I'd suggest creating a test login to SQL and using that instead.That's what I thought, too, but this didn't seem to be the case. I had that account given full privileges on the server, but still no luck.There is an old sight gag - The patient says, "Doctor, it hurts when I do this...". And the doctor says, "Then don't do that!"<BR><BR>Try creating a SQL server login (not based on Windows login). Then when you create your system DSN, click the radio button to use the SQL login, and enter the username and password of the account you created.<BR><BR>Note that if you are going to be using a connection string from an ASP page, then you want to click the SQL login radio button, but UNCHECK the login info so it greys out. When you click TEST at the end, it will FAIL. But this is OK. When your ASP app uses the DSN to connect, the connection string will provide the username and password at runtime.Do you mean that I should check the box next to "verify with SQL authentication..."? When I do this, then the login and password boxes below become white. When I try the login and password that are for the database (supplied by the network administrator), or any other name and password, it still gives the same error.That's correct, the login and password should become white. You can clear them by unchecking the box next to them, however...<BR><BR>If you entered the login/pwd supplied by the admin and it still failed, then I'm not sure what to tell you. It sounds like you are not the admin of the SQL box, and if that is the case, then your hands are mostly tied. <BR><BR>Again, be aware that two things are needed on the server side. When a new account is created, the SQL Admin must do things to enable the account to function. First, he must check off which databases the account has access to, such as the Northwind and Pubs databases (the sample ones Microsoft includes by default). The second thing is that he must set what permissions that account has to the data (read, write, execute, etc.)<BR><BR>If all of this is done and done correctly, then it should work, barring any other problems, such as a connection problem perhaps, or even a version problem with the MDAC on your PC. <BR><BR>Good luck, keep trying!
What does this SQL server error mean?
- Thread starter HenrXpX
- Start date