ODBC SQL SERVER DRIVER Login Failed for user .... 1

[Gert74]

I try to connect with a SQL-database named ESMKENNISSQL from an ASP-page using the follwoing code:

conn.open "esmkennissql", "gert","password"

User "gert" is an existing user for the SQL-database. I'm using an ODBC-connection for the connection.

For some reason I get the following error in Ineternet Explorer.


Microsoft OLE DB Povider for ODBC Drivers error '80040e4d'

[ODBC SQL SERVER DRIVER][SQL SERVER] Login failed for user 'WASHINGTON\IUSR_WASHINGTON'

/kennisbank/mwdropdown.inc, line 6


Line 6 in mwdropdown is the line conn.open "esmkennissql","gert","password"

I don't understand why I get an error saying loging failed for user WASHINGTON (which is the name of the NT-server!)while I'm explicitally referring to user "gert"

I have no clue why this isn't working because it has worked in the past. I suppose someone (maybe it was me) changed some settings in SQL enterprise manager by accident, but I can't figure out what. I hope someone can help me, because it's driving me nuts.

Thanks,
Gert

 

[foxdev]

The connection is trying to use NT security, not Standard security. You should specify "Trusted_Connection=No".
Robert Bradley

http://www.foxdev.com/

http://www.agrainofhope.org

 

[Gert74]

Maybe a stupid question, but where should I specify trusted connection=NO. In ASP-code, ODBC-connection or SQL manager.

 

[foxdev]

Not a stupid question. If you are using the string connect method, simply include it in the connection string, like this:

[tt]"driver={SQL SERVER};SERVER=MyServer;UID=me;
PWD=mypwd;DATABASE=mydb;trusted_connection=No&quot[/tt]
Robert Bradley

http://www.foxdev.com/

http://www.agrainofhope.org

 

[Gert74]

Thanks!!! It worked great.

 

[foxdev]

A pleasure to help.

For a complete list of SQL Server ODBC keywords and descriptions, visit:

http://msdn.microsoft.com/library/psdk/sql/odbc_d_2.htm

Robert Bradley

http://www.foxdev.com/

http://www.agrainofhope.org

 

[TomSark]

Kudos to Robert...

Also, if at all possible for you developers out there, try to populate the APP argument as well. This makes it a lot easier for us DBAs to know what applications are locking what resources in SQL Server...
Tom Davis
tdavis@sark.com

http://www.sarkdallas.com

 

[foxdev]

Good point, Tom. When there is just you, its not obvious, but when you get more than a few different people and apps connecting and you need to diagnose a block or long-running operation, having the APP= can be very, very handy.
Robert Bradley

http://www.foxdev.com/

http://www.agrainofhope.org