Re: TNS could not resolve the connect identifier

Charles Hooper wrote:
> 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.

Thanks a lot to Charles, Hank and hpuxrac. The problem is with the database driver. Since

1. The web application works fine with the VWD 2005 built-in web server through MSDAORA.dll database provider on the development machine. The provider name is System.Data.OleDb. This probably suggests that inability to connect to the Database through SqlPlus is not relevant to this issue, which I had indicated.
2. The web application does not work on the production web server.
3. Other web applications on the same production web server works fine with the same database, but through ODBC, and the provider name is System.Data.Odbc.

And I verified today that using ODBC on the development machine will crash the web application on the VWD 2005 built-in web server.

So, I modify the connectionString to use ODBC database provider if I wanna check out this web application through the production web server, and change it back to OleDb database provider on the development machine with the VWD 2005 built-in web server.

This works for me, although a little cumbersome.

I've just installed the M$ ODBC driver for Oracle on the development machine, but it hasn't helped. Received on Fri Nov 24 2006 - 22:40:41 CST