Greetings,

I have built a .NET DLL (C#) that acceses Oracle thru ADO "classic". It accesses an Oracle DB thru ODBC using a COM dll that wraps ADO functionlity.

It is executed from a VBS as called by a web service written by a company named Datacap. All of this operates under IIS on Server 2003.

My DLL preforms when I execute locally, but when the web service invokes it, It throws the message

System.Runtime.InteropServices.COMException (0x80040E4D): [Oracle][ODBC][Ora]ORA-12154: TNS:could not resolve the connect identifier specified

Seems like a permissions issue, because I have several other COM dlls that can do this. I'm not sure where to start with this one.

Any ideas??
Thanks

RedEye

It's been a while since I've dealt with Oracle but I don't recall any problems when connecting to oracle from IIS based apps. Can you confirm that the tnsnames files has the connection you need?

It sounds likely that IIS permissions might be a problem. You might start by looking at the file permissions for the IIS user to see if it has the rights to read the TNS names file.

-Peter
peterlanoie.blog

The way Oracle is configured on this computer, Oracle gets TNSNames info from the TNS_NAMES environment variable, which points to a network drive. It may be an issue with ORACLE executing for an IIS process not being able to see a network drive.

My next guess is the the process can't see the ODBC connection

I had to copy a file called ADODB to a directory under \Assemblies\ on this sever. May be an issue of IIS getting to that.

Just thinking out loud.

Thanks


RedEye

Ah, this could definitely be a problem.

A) Is the environmental variable a system variable or user variable?

B) How is the network drive configured? Is it mapped by the user account? This will definitely not work with IIS. Can you change the path to use an UNC address instead of a mapped drive? What kind of permissions issues will arise with accessing the network drive from IIS? The IIS account is typically a local system account, not a domain account, so although you may be able to easily access the UNC path without additional credentials, you'll find that IIS will have all sorts of trouble.

-Peter
peterlanoie.blog