By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,028 Members | 1,945 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,028 IT Pros & Developers. It's quick & easy.

IIS ODBC Logging causing problems with ASP.Net SQLClient database access

P: n/a
I run into a strange problem today while enableding ODBC SQL logging on my
IIS Server.

Once the logging was enabled, and working fine, my two ASP.Net Applications
could no longer connect to the database. I got an Access Denied or Server
does not exist error.

The moment I set the logging back to the normal file based logging, the
applications worked again.

I noticed in the stack trace of the ASP.Net errors that connection pooling
was showing up.

Could the ODBC logging, via a System DSN, somehow be interfering with the
..Net SQLClient access?

Strange thing is that all of the applications, and the logging, use
different usernames, so a connection from the pool should not be used

I'm stumped on this one, any guidance would be appreciated.

Jul 21 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.