ADO/ODBC call via Python/IIS

Bill Seitz fluxent at yahoo.com
Fri Feb 9 12:36:01 EST 2001


OK, I tried going back to the DSN approach. I dumped my user DSN and
created a system DSN. It looks to me like:

* you have to turn off IIS anonymous access, else you get an error
message of "COM Error: [Microsoft][ODBC SQL Server Driver][SQL Server]
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'."

* you have to turn on Basic Authentication for IIS, supporting only the
(more secure) Windows-integrated or digest authentication doesn't do it!

* since the web-page-user's ID is what's being passed along, you have
to set up SQL server accounts for all potential users, right?

Am I missing something, or is this horribly lame?

In article <3A81E8B4.2000402 at ActiveState.com>,
  Mark Hammond <MarkH at ActiveState.com> wrote:
> Bill Seitz wrote:
>
> > Well, it's a User DSN. Do you know that ASP expects a system DSN?
>
> ASP does not execute as your user, but as its own system user.  Thus,
a user DSN created for your user is simply not visible by ASP.  It must
be system DSN, or a user DSN for the ASP specific user
>
> > And, I'm not clear on what a DSN-less connection is. Does this mean
>
> Neither do I - hopefully someone else will ;-)
>
> Mark.
>
>


Sent via Deja.com
http://www.deja.com/



More information about the Python-list mailing list