RE: ASP/ODBC failing to connect to SQL when PythonWin succeeds?

[Bill Seitz]

Title: ASP/ODBC failing to connect to SQL when PythonWin succeeds?

It turned out the SQL drives on the one server were not consistent with the others. Time to shoot the sysadmin.

-----Original Message-----
From: Mark Hammond [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 25, 2001 6:29 PM
To: Bill Seitz; [EMAIL PROTECTED]
Subject: RE: ASP/ODBC failing to connect to SQL when PythonWin succeeds?

The most likely reason is that the user under whom ASP runs does not have the same permissions as the interactive user.  This has come up a few times on the newsgroups with various work arounds, but as I dont do this very often I can not remember the specific details...

 

Mark.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Seitz
Sent: Thursday, 26 April 2001 6:32 AM
To: [EMAIL PROTECTED]
Subject: ASP/ODBC failing to connect to SQL when PythonWin succeeds?

Environment: Win2K, Sql2K, IIS5, ASP, PythonWin

Have suddenly run into problems rolling out some code to a production web server, after it worked fine on development machine and staging server. There's a single MsSql server involved across all 3 cases.

On the production box, none of my ASP pages which make ODBC calls work. I get an error at the time of trying to make the initial connection: "[Microsoft][ODBC SQL Server Driver]Client unable to establish connection in LOGIN".

Yet
- when I go into the control panel for the DSN I'm using, and hit the Test button, it works fine
- when I launch PythonWin environment on the server itself, and run the equivalent code interactively, it works fine.

Any clues as to what could be going wrong here? I've already spent a couple days on this, it's getting embarrassing.