Looks like you're using the Microsoft ODBC Driver for Oracle, yes? If so, make sure you have an Oracle client installed (full client or instant client) and make sure you have your PATH and ORACLE_HOME environment variables set accordingly.

I also have this problem, but in a different way:

I am using 'Actuate 7' (A report writer) to access an ODBC connection to an Oracle DB.
I have created a System DSN and when I connect through Actuate as an 'Admin' user, the connection goes through fine (my SQLNET & TNSNAMES .ora files are correct) - however, if I use Actuate as a 'Non-Admin' user, i get:

" The Oracle(tm) client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3 (or greater) client software installation."

along with a "Login Failed (3) (0)" error.


I've trawled various forums and have found this issue several times, but none of the fixes I've tried have made any difference!

Any input will be greatly appreciated!

Many thanks,

Greg

What permissions are set on the client directories?

Thanks for replying, Jonah.

Would it be just the \bin directory that the Non-Admin User group would need access to (and I guess R&X would be sufficient?) , or would it be wiser to set the permissions on the \ora92 directory to be propagated to all child objects?


Kind Regards,

Greg

All parent directories would need to permit your user to access the bin directory.

Thanks Jonah - that appears to've solved the problem. Now I have a problem with an actuate script! Hooray! :)