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

ODBC DSN Connection

P: n/a
Using ODBC DSN connection in ASP.net does not work, but same code will
execute properly as a Windows application, is this the result of .NET Code
Access Security, since user DSNs are registry based?

What would be required to allow (ASP.net) Web Application to use ODBC DSN
connection?

Bravo security (what a concept),

Karl Mikesell MCSE
Nov 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi Karl,

First, I have to wonder why you would want to use an ODBC DSN, as ODBC is a
wrapper for OLE DB, and almost every major database product out there has
OLE DB drivers nowadays. Be that as it may...

You are correct that you are dealing with a permissions issue here, and that
it is related to the fact that System DSNs are stored in the registry. The
user accoount under which your ASP.Net app is running must have permission
to read that registry key in order to use a System DSN.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Karl A Mikesell" <mu*****@ieee.org> wrote in message
news:OX**************@TK2MSFTNGP12.phx.gbl...
Using ODBC DSN connection in ASP.net does not work, but same code will
execute properly as a Windows application, is this the result of .NET Code Access Security, since user DSNs are registry based?

What would be required to allow (ASP.net) Web Application to use ODBC DSN
connection?

Bravo security (what a concept),

Karl Mikesell MCSE

Nov 18 '05 #2

P: n/a
Thank you for confirming so quickly. The DSN in question is not a database,
it is a proprietary device interface (yet another legacy device), just
trying to hook into it. This is were Web Services helps greatly.

Thank again.

"Kevin Spencer" <ks******@takempis.com> wrote in message
news:eC**************@tk2msftngp13.phx.gbl...
Hi Karl,

First, I have to wonder why you would want to use an ODBC DSN, as ODBC is a wrapper for OLE DB, and almost every major database product out there has
OLE DB drivers nowadays. Be that as it may...

You are correct that you are dealing with a permissions issue here, and that it is related to the fact that System DSNs are stored in the registry. The
user accoount under which your ASP.Net app is running must have permission
to read that registry key in order to use a System DSN.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Karl A Mikesell" <mu*****@ieee.org> wrote in message
news:OX**************@TK2MSFTNGP12.phx.gbl...
Using ODBC DSN connection in ASP.net does not work, but same code will
execute properly as a Windows application, is this the result of .NET

Code
Access Security, since user DSNs are registry based?

What would be required to allow (ASP.net) Web Application to use ODBC DSN connection?

Bravo security (what a concept),

Karl Mikesell MCSE


Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.