Re: TNS could not resolve the connect identifier

antonyliu2002_at_yahoo.com wrote:
> I did install the Oracle ODAC for .NET on the production web server
> some time ago. I don't think I did a custom install. So you are
> suggesting that I reinstall it and customize it? I can try it.
>
> But, the connectionString in web.config suggests that the provider I
> used with Visual Web Developer (VWD) 2005 is MSDAORA, which is a M$
> product. I'm not sure if I am getting the point, but as I said, this
> DB provider works fine in VWD 2005. Pls note that VWD 2005 has a
> built-in web server, and the web application works great with this
> built-in web server.

I write quite a few programs for in-house use, and found that a Custom installation is required so that the necessary drivers are installed.

Regarding the MSDAORA connection, I believe that you are correct that this is a Microsoft supplied file. I have been using that in the connection specification for ASP pages on my IIS server for roughly the last five years. I have also used connection strings like this on ASP pages (MYODBC_CONNECTION is an ODBC connection that uses the Oracle ODBC client):
"Data Source=MYODBC_CONNECTION;User ID=" & session("Username") & ";Password=" & session("Password") & ";OLE DB Services=-1;"

In other environments, I use either (connect without ODBC): "Provider=OraOLEDB.Oracle;Data Source=MY_SID;User ID=MY_USER;Password=MY_PASSWORD;"

Or (connect with ODBC)
"Data Source=MYODBC_CONNECTION;User IDMY_USER;Password=MY_PASSWORD;"

You might try using Provider=OraOLEDB.Oracle

As I mentioned, I have not yet switched to ASP.Net, so I cannot verify the correct connection.

The first hurdle that you need to solve is being able to connect using SQLPlus from the computers.

Charles Hooper
PC Support Specialist
K&M Machine-Fabricating, Inc. Received on Fri Nov 24 2006 - 15:32:34 CST