Newer versions of ODBC (MDAC?) allow you to test
the DSN from within the ODBC DSN setup applet, I
would first try that.
I would also suggest using iODBC, a command-line
ODBC utility that works just like isql, instead
of ODBC PING. You can get that at
The third (and messiest/most time consuming) thing
to test is the permissions of the account IIS4 is
using to attempt to access the database. Check
your event log (assuming you have set bad logins
to be logged in the User Manager), check the SQL
Server Error Log, and try changing the IIS4
Anonymous Login Account (Dir Security: Anon Access/
Auth Control: Edit Anon Access: Browse) to
your user account (if you have been able to
interactively access the db through ODBC).
That should let you know if you need to examine
the NTFS permissions of your %SystemRoot% (you
must have at least Read access to the DLLs
ODBC uses), or if you need to allow the Anon
account to "Access This Computer Over The Network",
Just a few ideas, hope they help...
> I have my IIS 4.0 server trying to log to my sql 6.5 sp4 server via ODBC.
> The NT event log has indicated than it isn't working becuase of an ODBC
> timeout from the IIS server. Note, sql and iis are on the same PC. I have
> 1. Tested connection with MS Query--it works
> 2. Tried to ODBC PING the server--it didn't find the server (I found this
> 3. Made sure I was using Standard Security
> 4. Made sure network support was both Multi and Pipes, then tried just
> Pipes, neither worked.
> 5. When to Client Config. Utility and tried default network of Pipes and
> then Multi, neither worked.
> Does anyone have an idea on this?
> Any help is appreciated,
Spokane Public School District 81