Posted by Erland Sommarskog on 02/17/07 15:57

(kk035@hotmail.com) writes:
> It seems that it does not wait for 15 seconds - it returns at once.
> The password is hard coded. Changing to SQLNCLI doesn't change
> anything. Using the same ASP-application on a remote IIS without
> changing anything works fine. Using a wrong password in the ODBC-
> Configuration to get additional configuration options produces an
> entry in the error log of the SQL-Server,

You are talking about the ODBC applet in the Control Panel?

> Using a wrong password in the DSN for the ASP-
> application does not result in an error log entry.

A password in the DSN? Didn't you also have a password in the connection
string?

I still don't know why you think the connection failed.

If you leave out "if errDb.Number <> 0 then" do you get anything in
your Session array?

When you changed to SQLNCLI, did you remove the DSN reference?

What happens if you add "SERVER=bogus;" to the connection string?

What happens if you replace UID and PWD with "Integrated Security=SSPI;"?

Since I don't have to access to your system I have to ask questions in
the dark. Please keep this in mind when you answer the questions, and
try to be as clear and unambiguous as possible. It's enough of a guessing
game for me anyway.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]