Provider Not Compatible with client

I downloaded the Oracle 11g ODAC 11.1.0.7.20 and installed it on my development computer.
The C# aspx web pages are running fine on my computer now on localhost. But when I publish the files to the development server, I am getting the error: "The provider is not compatible with the version of Oracle client".
The only access I have on that development server is to one directory for uploading the web pages. I have no other access. I believe they have the older version 10 something of the client installed but I want to use the latest one on my site. Also, I don't want them to install a new driver; don't want to mess up other sites on that server since they may need to use the older odp.net / clients.
I have read somewhere that I can put the dll files in the bin directory and it would work. I followed the instructions from here http://splinter.com.au/blog/?p=156 and I am still getting the error.
How can I deploy my web pages to the server and still use the latest odp.net drivers?
Thanks,

Hi,
As suggested in the last reply, this is the binary mismatch issue, essentially ODP is not able to find correct / compatiible client binaries during runtime. Now couple of points:
1. ODP needs a service layer binary (ORAOPS), which needs to be exactly same version as ODP or else execution fails with exception, as suggested in the link - http://www.oracle.com/technology/tech/windows/odpnet/faq.html#MOH
first place to pick it is application directory and then registry / path variable comes into the picture, so this could not be an issue in this case, since you have coipied everything to the same directory.
However, please remember for an assembly signed with the strong name first place to probe is GAC not application directory, so in case on the development server ODP is installed in the GAC then there could be a mismatch, since it is trying to match with your oraops binary.
2. Also, in case you haven't copied oraops dll then regitry comes in to the picture and in case development server doesn't point to the right directory, then it would lead to the same error.
So, you need to make sure that development server loads the right odp and oraops combination.\
May be use process explorer to see the binaries / versions loaded.
Also, let me add, beside oraops even if other client binaries are 10g specific, there wouldn't be a compatibility issue, since Oracle products maintain backward compatibility, so odp 11g binary would be fine with client 10g binary till the point, there's are no new unsupported APIs are called, that would be a certain exception
Hope this helps,
Mrinal

Similar Messages

Provider not compatible with Ora Client

Hi,
I just installed the Oracle DB 10G v. 10.2.0.1.0 and the ODP.NET v. 10.2.0.2.20 in my computer.
After I did that, I tested it and received the message: "the provider is not compatible with the version of oracle client". Do you know how to solve this issue? Which version of the Oracle Client or ODP should I install?
TIA

In your other post you mention OraOps10w.dll. That suggests that you developed on a machine with a version 10 client, and are now deploying to a machine with a version 9(.2) client. This won't work. Either install client version 10 on the deployment machine (best) , or install odp.net v9 on your development machine and rebuild.

Error :"The provider is not compatible with the version of Oracle client"

Hi guys!
I'm facing this problem:
When my .Net application tries to access the DB, I get this error message above.
The application is into the same machine of DB and the operational system is Windows Server Enterprise 64 bits.
I'm comparing to another machine that has the same scenario but runs in Windows Vista 64 bits. This problem doesn't happen and I can normally access the DB.
The both database versions are 10g Release 2 (10.2) and all components from Oracle Database Components 10.2.0.2.21 are installed as the containing bellow:
-Oracle Data Provider for .NET 1.x 10.2.0.2.20
-Oracle Data Provider for .NET 2.0 10.2.0.2.20
-Oracle Developer Tools for Visual Studio .NET 2003 10.2.0.2.20
-Oracle Developer Tools for Visual Studio 2005 10.2.0.2.20
-Oracle Provider for OLE DB 10.2.0.2.20
-Oracle Objects for OLE 10.2.0.2.20
-Oracle Services For Microsoft Transaction Server 10.2.0.1.0
-Oracle Net 10.2.0.1.0
-Oracle Universal Installer 10.2.0.2.0
Oracle.DataAcces.DLL is 2.102.2.20 and it is reference in my .Net app (that is published and located into IIS).
These are the Oracle assemblies installes in 'C:\Windows\Assembly':
Windows Vista Machine:
ASSEMBLY NAME VERSION CULTURE PUBLIC KEY TOKEN PROCESS ARCHITECTURE
Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 pt-BR 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 it 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 fr 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 es 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 de 89b483f429c47342
Oracle.Management.Omo 2.102.2.20 Neutral 89b483f429c47342 x86
Oracle.VsDevTools 2.102.2.20 Neutral 89b483f429c47342 x86
Policy.10.1.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Policy.10.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Windows Server Machine:
ASSEMBLY NAME VERSION CULTURE PUBLIC KEY TOKEN PROCESS ARCHITECTURE
Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Oracle.DataAccess 2.102.2.20 Neutral 89b483f429c47342 x86
Oracle.DataAccess.resources 10.2.0.100 pt-BR 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 zh-CHT 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 zh-CHS 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 ko 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 jp 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 it 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 fr 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 es 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 de 89b483f429c47342
Policy.10.1.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Policy.10.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Policy.9.2.Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
Policy.9.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
What should I check and do to solve this problems?
Thanks for help,
Anderson

Hi,
Often the error "The provider is not compatible with the version of Oracle client" is raised when the unmanaged dll OraOpsX.dll can't be found, can't be loaded, or is the wrong version. For version 10.2.0.x of ODP.NET and .NET Framework 2.x the file should be called "OraOps10w.dll" and should be found in the %ORACLE_HOME%\bin directory.
Since the ODAC pieces are installed on the same host as the database, are they in a separate Oracle Home or the same Oracle Home as the database software? If there are multiple Oracle Home directories, which one is in the system path first?
I would start with verifying the version of OraOps10w.dll and the system path on the server. You might also confirm that the Oracle Home directory (and everything under it) has the following permissions for Authenticated Users:
- Read & Execute
- List folder contents
- Read
Regards,
Mark

The provider is not compatible with the version of Oracle client

We are running Server 2012 64 bit with multiple homes one is 32 bit and the other 64 bit. We installed the 64 bit first then the 32 bit next in order to get our Classic ASP WebSite that is using COM+ and OLEDB to see the provider.
C:\oracle\product\12.1.0\x86
C:\oracle\product\12.1.0\x64
The other Websites are ASP.Net 4.0 and are running in 64 bit application pools. They are using a DAL .Net assembly built x64 with a reference to the 64 bit ODP.Net version 4.121.1.0 in C:\oracle\product\12.1.0\X64\client_1\odp.net\bin\4.
I also see there is another folder C:\oracle\product\12.1.0\X64\odac_1\odp.net\bin\2.x with version 2.121.2.0. We are on running Framework 4.0 but when I switch to this version it works but with the version out of the bid\4 we are receiving the following error when the 64 bit Websites call the assembly:
The provider is not compatible with the version of Oracle client
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client
Source Error:
Line 87: mDataSource = dataSource
Line 88: mConnectionString = GetDBConnectionString(dataSource)
Line 89: mConnection = New OracleConnection(mConnectionString)
Line 90: mParams = New List(Of IDbDataParameter)
Line 91: End Sub
I have not been successful in getting this to work after spending endless hours, so any help would be appreciated.

Hi,
Oracle Client/ODP build with certified Visual C++ Libraries so application using ODP.NET requires "runtime components of Visual C++ Libraries" to be installed.
Oracle Database Client installation includes the Visual C++ Libraries but ODAC doesn't contain these libraries which may cause such issue.
Please check the Note 43208.1 for the particular version of Visual C++ installs with Oracle Database Client installation(e.g. 11.2.0 Database Client installs Visual C++ .NET 2005) and also you can refer the windows event log error massage to verify which version of Visual C++ is missing.
thanks and regards
Venkat

Provider is not compatible with the client

Hi,
I'm new to this forum so I don't know if this prob was already posted.
It might be something that i misunderstood.
My application VB.NET is connecting to Oracle 10g database.
Using client from the ODAC 10.2.0.2.21 installation file.
DB version is 10.2.0.1.0
Even before connection is open application throws an exception:
The provider is not compatible with the version of Oracle client at Oracle.DataAccess.Client.OracleInit.Initialize()
Any ideas?
Thanks for help ;O)
Nice day to everybody.
Renata Belakova

Thanks
1, I'm developing an application on Win 2003 Server with Ora10g DB 10.2.0.1.0
2, I developed an application in VS.NET 2005, VB.NET
3, Application works OK on develop. PC
4, my PC name, IP and DB name are the same as customers
5, i published application and went to install it on customers PC
I was thinking about the same environment on developing and customer PCs.
then i went to customer to try application on their LAN
1, They have DB server with the same version of DB and the same name of DB and the same name of server as i got
2, firstly I've installed ora client on customer computer not server
I've used ODTwithODAC1020221.exe file and installed client part
3, set up listener on clients comp
4, installed .net application on this client comp
5, run and got exception i wrote in previous message
Im really not an Oracle professional. I'm a .NET developer but fist time in my life developing application under Oracle DB (mostly was using Microsoft SQL ...)
So I don't know if these steps were OK .... but it's what i've read.
Thanx ...

'The provider is not compatible with the version of Oracle client' exceptio

Hi
I installed ODAC-11.1.0.7.10 Beta on my development system and developed a .net application which uses Oracle.DataAccess.dll to connect to Oracle10g database.
the application is working fine, means opening connection successfully when I run it from my development system. but the same application is throwing
'The provider is not compatible with the version of Oracle client' exception when I run it on my 10g database server system.
what I need to do to run the application successfully on the machine where 10g server exists?
any help is appreciated.
thanks,
harry

Hi Harry,
I am not sure why you installed 11.1.0.7.10 Beta as 11.1.0.7.20 has been released and you should not be using the beta at this time. That error message is because the dependencies being loaded by the process are the wrong version. When you deploy an ODP .NET application using 11.1.7.x, you need to make sure you deploy it to a machine where the 11.1.0.7.x dependencies are installed. My guess is if I read your poat correctly is that Oracle.DataAccess.dll version 11.1 is loaded but its finding 10.2 dependencies on the target deployment box.
HTH
Jenny

Provider is not compatible with this version of Oracle client

I am trying to access Oracle(10.2) DB from a .NET 2.0 Console Application.(.exe) in a Win 2008.Web code is also on the same Win 2008 system
The Web application works fine and connects to teh DB , but when I try to run any of the Console applications it gives the error as:
Provider is not compatible with this version of Oracle client.
The Oracle.Dataaccess.dll versions which are available in GAC are 1.102.2.20 and 2.102.2.20.
and the Oracle client installed is 10.2.0.100
The complete error message is:
Unhandled Exception: Oracle.DataAccess.Client.OracleException The provider is not compatible with the version of Oracle client
at Oracle.DataAccess.Client.OracleInit.Initialize()
at Oracle.DataAccess.Client.OracleParameter..ctor(String parameterName, OracleDbType type, ParameterDirection direction)
Can any of you help me find a reason for this error.
Thanks in advance!!

Hi Greg,
I found out another reason this error was appearing.I am compiling the Console application in a 32-bit machine on 32-bit Oracle client.
The pre-compiled DLL and EXE is then exported to a 64-bit Win 2008 machine.
Also,The code has been compiled with ‘Any CPU’ .
The Web Application on the same system is working because the "Enable 32-bit Applications" is set to True.
Are there any DLLs or EXEs created when compiling in the 32-bit machine which is not compatible with the 64-bit machine?
Please help!!
Thanks,
Veena

Another: The provider is not compatible with the version of Oracle client

Hi everybody,
We still have problems with the ODP dll. with our .Net development. I copied all the dlls as mentioned here: [http://splinter.com.au/blog/?p=156] and in many other posts here in the forum. The .Net development works fine on our Development PCs (WIN XP32) and on many other PCs in the company. But we still have some PCs (As well WIN XP32) that come up with the Error: The provider is not compatible with the version of Oracle client.
Has anyone an idea???
Thanks a lot for your help
Best Jan

Hi Jan,
If there has never been any Oracle Client software installed on the machines, it seems unlikely that there would be Oracle policy files and version(s) of Oracle.DataAccess in the GAC. But, yes, the CLR will look to the GAC first for loading the Oracle.DataAccess assembly. I'm not sure what Framework or Domain setting would be involved here if there is no Oracle client installed. Are the machines configured the same as far as Regional/Language settings, etc?
One thing you might be able to try is to create an application configuration file and enable ODP.NET trace in the file. This is an ODP.NET 11.1 new feature. However, it's possible the error will prevent the trace file from being created. You would create a file named YourApplicationName.exe.config and here is a sample of the minimum content to enable ODP.NET trace:
{noformat}
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<oracle.dataaccess.client>
   <settings>
     <add name="TraceFileName" value="c:\odpnet2.trc"/>
     <add name="TraceLevel" value="1"/>
   </settings>
</oracle.dataaccess.client>
</configuration>
{noformat}
I wish I had an easy answer for you!
Regards,
Mark

The provider is not compatible with the version of Oracle client... again!

Please, please, please help me!
I get the error, "The provider is not compatible with the version of Oracle client", intermittently on my Test Server. Strangely, without restarting the server or IIS, my application suddenly decides that I don't have the right Oracle client. I don't have any such issue on my local machine even though I'm using the same Oracle 11g client from Beta 1.
I have Oracle 11g (D:\Oracle11g\product\11.1.0) installed. I tried specifying which assembly to use in my web.config:
<compilation debug="true" defaultLanguage="c#">
<assemblies>
<add assembly="Oracle.DataAccess, Version=2.111.5.10, Culture=neutral, PublicKeyToken=89b483f429c47342" />
</assemblies>
</compilation>
I'm not even trying to use a 10g client with the Providers as discussed here: "The provider is not compatible with the version of Oracle client"
What I don't understand is why this error comes and goes?!?! Has anyone experienced anything like this?

The server is Win 2003. The local development machine is WinXP.
...I was trying to wait to install Beta 2 because of the nasty bugs reported on this forum.
I'm now seeing that ORACLE_HOME wasn't set on my server because my co-worker removed the path. Somehow it was able to find an Oracle Home on the server, but apparently, it didn't always find the same home causing this error intermittently.
Now, my question is how can I get my application to use the 11g Client as its Oracle Home, while my co-worker can use 10g Client as his Oracle Home? To be a bit more specific, he needs to use an ODBC client to connect because his application uses Classic ASP.
Is this possible, or are we going to have to set up separate machines?
Bee

'The provider is not compatible with the version of Oracle client error' popping up randomly

I have several asp.net pages running on an application server which generally work without issue. However I've had the Server error "The provider is not compatible with the version of Oracle client error" crop up twice seemingly randomly that affects all of my pages that interact with the DB server. A simple reboot of the application server solves the issue and the pages run again with no problems. What could be causing this problem?

Sorry if I wasn't clear initially. Basically I've got 2 different applications in 2 different IIS folders on the webserver, each with several asp.net pages. They work fine for a period of time and then inexplicably that error gets thrown and affects all of my asp.net pages in both applications. The admin tells me that the other older applications on the same server are unaffected. A simple reboot of the server fixes the issue until the next time it happens (I can't identify any consistent point where this crash happens, the admin originally suggested that there might be something in my code causing a memory issue). I had the same applications hosted on my local machine for a time and this never happened as well as it never happening when I run them in localhost. How can I trace whether or not another part of my application is trying to load ODP.NET by itself? How can I verify the DLL search order for my application?

API5036: Client Version 10.1.0.4 is not compatible with Repository version

I have an OWB repository version 10.1.0.1.0 and a client of 10.1.0.2.0. We have have been running this fine. I need to upgrade to 10.1.0.4.0 of OWB so I can begin to use a 10gR2 database as my target. I exported (database wise) my repository and imported it into the 10.2.0.1 database - all went well. I now went to upgrade the repository from 10.1.0.1.0 to 10.1.0.4.0 and ran the shell in the ../bin/unix dierctory. It ran fine, yet when I connect to the repository using the 10.1.0.4 client I get the "API5036: Client Version 10.1.0.4 is not compatible with Repository version 10.1.0.1.0" as if I never ran the DT upgrade shell. I then noticed the shell provided with the 10.1.0.4 install is DTupg92to10g.sh and I am not upgrading a 92 repos to a 10 repos. Is there a upgrade for 10.1.0.1.0 to 10.1.0.4.0?
Thanks,
Sean

for OWB metadata, run this following script
<OWB_HOME>/owb/reposasst/upg/upg10gTo10104.sql
For runtime data
<OWB_HOME>/owb/bin/unix/RT_upgrade_to_10_1
This is only if it's NOT upgrading to 10gR2 database
If you are upgrading to Oracle10g Release 2 with partial export and
import and if you are changing the database instance or the computer
hosting the database, then run the migration script:
For UNIX, navigate to OWB_HOME/owb/bin/unix and run
RT_migrate_to_10_1.sh.
The RT_migrate_to_10_1.sh prompts you for several parameters:
the User Name and Password of your original Runtime Repository
schema, the database connection string for your original Runtime
Repository (in the form of host:port:servicename), the User Name
and Password for your new Runtime Repository schema (whose values
should match the original Runtime Repository), and the database
connection string for the new Runtime Repository (also in the form of
host:port:servicename). Additionally, as it runs, the script prompts
you for SYS User Names and Passwords for the Oracle Database
instances for any Target Schemas and Oracle Workflows being upgraded.

Provider not compatible version of Oracle client after upgrade 4.112.1.2

I had an ASP.NET 3.5 website running
on intranet small business server as production with:
OS Win2008 Standard 32-bit
Oracle Database 11g107 32-bit
Oracle DataAccess 2.111.60 32-bit
On a development laptop,
I upgraded the website to ASP.NET 4.0.
The development laptop had
OS Windows 7 32-bit
VS 2010
Oracle Database 11g201 32-bit
Oracle DataAccess 4.112.12
Application was running without errors.
On the production server,
I uninstalled Oracle Database 11g107,
to include removing Oracle home and install folders,
and in HKLM > Software > Oracle registry folder.
I installed Oracle Database 11g201
and installed the ODP.NET upgrade to 4.112.12.
(except for VS components).
In the website web.config,
I changed the referenced assembly to:
<assemblies>
<add assembly="Oracle.DataAccess, Version=4.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342" />
I changed IIS70 Application pool advanced settings to ASP.NET 4.0,
restarting application pool and website.
Rebooted system.
On starting the application when it accesses the Oracle connection,
I get the dreaded: Provider not compatible.
Exception Details: Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[OracleException (0x80004005): The provider is not compatible with the version of Oracle client]
Oracle.DataAccess.Client.OracleInit.Initialize() +433
Oracle.DataAccess.Client.OracleConnection..cctor() +844
It is not the VB.NET Oracle connection code,
as it runs fine on the development laptop.
So I look into the GAC.
GACUTIL /l shows 2.111.60 is still in the .NET
The Global Assembly Cache contains the following assemblies:
Oracle.DataAccess, Version=1.111.6.0, Culture=neutral, PublicKeyToken=89b483f429c47342
Oracle.DataAccess, Version=2.111.6.0, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Oracle.DataAccess, Version=2.112.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Oracle.DataAccess, Version=2.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Oracle.DataAccess, Version=4.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Oracle.Database.Extensions, Version=1.111.6.0, Culture=neutral, PublicKeyToken=89b483f429c47342
Oracle.Database.Extensions, Version=2.112.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Oracle.Database.Extensions, Version=2.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Oracle.Database.Extensions, Version=4.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Oracle.Web, Version=2.112.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Oracle.Web, Version=2.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Policy.2.102.Oracle.DataAccess, Version=2.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Policy.2.111.Oracle.DataAccess, Version=2.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Policy.2.111.Oracle.Web, Version=2.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Policy.2.112.Oracle.DataAccess, Version=2.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Policy.2.112.Oracle.Web, Version=2.112.1.2, Culture=neutral, PublicKeyToken=89b483f429c47342, processorArchitecture=x86
Is there a command I need to run to remove the old 111.6.0 Oracle client references from GAC?
Eventhough Oracle ODP.NET installer put a policy to refer the older version to the new?

In
C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0
and in
C:\Windows\Microsoft.NET\Framework\v4.0.30319
There is only SYSTEM.DATA.ORACLECLIENT
I suspect that we would not see Oracle.DataAccess.dll in these locations anyway.
++++++++
In
C:\Windows\assembly
There is:
Oracle.DataAccess 2.112.1.2
Oracle.Database.Extensions 2.112.1.2
Oracle.Web 2.112.1.2
This is the GAC for ASP.NET 2.0-3.5,
so this appears to be correct
++++++++
In
C:\Windows\Microsoft.NET\assembly\GAC_32
There is:
C:\Windows\Microsoft.NET\assembly\GAC_32\Oracle.DataAccess\v4.0_4.112.1.2__89b483f429c47342
C:\Windows\Microsoft.NET\assembly\GAC_32\Oracle.Database.Extensions\v4.0_4.112.1.2__89b483f429c47342
C:\Windows\Microsoft.NET\assembly\GAC_32\Oracle.Web\v4.0_4.112.1.2__89b483f429c47342
with the appropriate 4.112.1.2 dlls in these folders
This is the GAC for ASP.NET 4.0,
so this appears to be correct.
+++++++
In
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\Machine.config
Removed Oracle Providers references, I just need ODAC to update and insert data into schema data tables,
and do not use the ASP.NET Oracle Providers schema.
Should I need ASP.NET Oracle Providers schema, I can always add references in the application web.config.
<system.data>
<DbProviderFactories>
<add name="Microsoft SQL Server Compact Data Provider" invariant="System.Data.SqlServerCe.3.5" description=".NET Framework Data Provider for Microsoft SQL Server Compact" type="System.Data.SqlServerCe.SqlCeProviderFactory, System.Data.SqlServerCe, Version=3.5.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/></DbProviderFactories>
</system.data>
<membership>
<providers>
<add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="LocalSqlServer" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10" passwordStrengthRegularExpression=""/>
</providers>
</membership>
<profile>
<providers>
<add name="AspNetSqlProfileProvider" connectionStringName="LocalSqlServer" applicationName="/" type="System.Web.Profile.SqlProfileProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
</providers>
</profile>
<roleManager>
<providers>
<add name="AspNetSqlRoleProvider" connectionStringName="LocalSqlServer" applicationName="/" type="System.Web.Security.SqlRoleProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
<add name="AspNetWindowsTokenRoleProvider" applicationName="/" type="System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
</providers>
</roleManager>
<siteMap>
<providers>
</providers>
</siteMap>
<webParts>
<personalization>
<providers>
</providers>
</personalization>
</webParts>
<healthMonitoring>
<providers>
</providers>
</healthMonitoring>
+++++++++++++
In
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\web.config
No Oracle references, and I would expect this as it is added in application level web.config
+++++++++++++
In
C:\Windows\Microsoft.NET\Framework\v4.0.30319\ASP.NETWebAdminFiles\web.config
No Oracle references, and I would expect this as it is added in application level web.config
+++++++++++++
In
D:\ORA\DB11G201\ODP.NET\bin\4
Oracle.DataAccess.dll 4.112.1.2
and in
D:\ORA\DB11G201\ASP.NET\bin\4
Oracle.Web.dll 4.112.1.2
+++++++++++++
So... why would I get provider not compatible version of Oracle Client...
there are no other versions of ODAC hanging around,
unless there are other locations I am not aware of.
The application works fine in development laptop.
The application works fine on production server when I use SYSTEM.DATA.ORACLECLIENT.
But we need to migrate away from SYSTEM.DATA.ORACLECLIENT according to Microsoft,
and I am sure Oracle would rather have me use Oracle.DataAccess client anyway.
++++++
I even tried a trick from another post to move what appears to be Oracle Instant Client components,
oci.dll, et al, from an installation into a new home of the Oracle 11g201 Cllent 32 along with Oracle.DataAccess.dll into the website BIN folder
and set references for Oracle.DataAccess.dll to LOCAL TRUE.
+++++++
So I remain stuck.

Inner Exception The provider is not compatible with the version of Oracle

I am using the 64 bit ODP and Net 2.0 SDK in a C# program which runs standalone and is also hosted by another win32 process.
When running standalone it works ok. But when being hosted by another process, I get the following exceptions thrown when i create a connection:
INFO 2007-01-10 12:38:26,843 265ms frmCCMain LogMessage - Exception During Batch Processing1: [The type initializer for 'Oracle.DataAccess.Client.OracleConnection' threw an exception.]
INFO 2007-01-10 12:38:26,843 265ms frmCCMain LogMessage - Inner Exception The provider is not compatible with the version of Oracle client
I checked the DllPath value under the ODP.NET key and it points to the directory where OraOps10w.dll is installed. I also tried copying that Dll into the host process working directory and searched and found no other versions of that DLL.

Yes, this sounds like you may be using the 9.2 client with ODP.NET and ASP.NET Providers for 11g. Usually, you can stop and start IIS to resolve this. IIS will then pick up that the 11g client directory is first in the Windows PATH, ahead of the 9.2 client directory, then use that for any subsequent Oracle client calls.

API5036: Client version 10.2.0.1.31 is not compatible with repository ver..

API5036: Client version 10.2.0.1.31 is not compatible with repository version 10.2.0.2.0
I got this error after upgraded with patch p5696353_10202_AIX64-5L
I tried to log in but there was a pop up dialog told me about this error. Do I have to install new client version?? I cannot find owb client 10.2.0.2.0 on the download site. Would you guys help me to get though this please?? Any solotion if I still used owb client version 10.2.0.1??
Rgds,
Godtee

Hi Godtee,
you have to use the same version on the client as on the server.
There is only one software package containing owb client and server components. Use it for server and client side installations.
It seems that you have patched your server installation to 10.2.0.2.0. Apply this patch to your client installation and you will be able to connect to the repository with version 10.2.0.2.0
Regards,
Carsten.

Error 2000 - The server is not compatible with this deployment client

I'm getting an error trying to deploy a composite. It works for everyone else on the team, and our configurations are the same (as far as we can tell). We've compared JDev version info.
Any idea what I can try? Thank you.
[12:57:48 PM] ---- Deployment started. ----
[12:57:48 PM] Target platform is (Weblogic 10.3).
[12:57:48 PM] Running dependency analysis...
[12:57:48 PM] Building...
[12:58:05 PM] Deploying profile...
[12:58:06 PM] Wrote Archive Module to C:\pkgs\svn\mdm\trunk\src\DRM WDK Source Code\Workflows\DrmRequestWorkflowSelection\deploy\sca_DrmRequestWorkflowSelectionComposite_rev3.0.jar
[12:58:06 PM] Deploying sca_DrmRequestWorkflowSelectionComposite_rev3.0.jar to partition "default" on server soa_server1 [http://10.22.2.40:8001]
[12:58:06 PM] Processing sar=/C:/pkgs/svn/mdm/trunk/src/DRM WDK Source Code/Workflows/DrmRequestWorkflowSelection/deploy/sca_DrmRequestWorkflowSelectionComposite_rev3.0.jar
[12:58:06 PM] Adding sar file - C:\pkgs\svn\mdm\trunk\src\DRM WDK Source Code\Workflows\DrmRequestWorkflowSelection\deploy\sca_DrmRequestWorkflowSelectionComposite_rev3.0.jar
[12:58:06 PM] Preparing to send HTTP request for deployment
[12:58:06 PM] Creating HTTP connection to host:10.22.2.40, port:8001
[12:58:06 PM] Sending internal deployment descriptor
[12:58:06 PM] Sending archive - sca_DrmRequestWorkflowSelectionComposite_rev3.0.jar
[12:58:07 PM] Error deploying archive sca_DrmRequestWorkflowSelectionComposite_rev3.0.jar to partition "default" on server soa_server1 [http://10.22.2.40:8001]
*[12:58:07 PM] HTTP error code returned [2000]*
*[12:58:07 PM] Error message from server:*
The server is not compatible with this deployment client: please verify that the server is a SOA managed server and that its version is supported by this deployment client
[12:58:07 PM] Check server log for more details.
[12:58:07 PM] Error deploying archive sca_DrmRequestWorkflowSelectionComposite_rev3.0.jar to partition "default" on server soa_server1 [http://10.22.2.40:8001]
[12:58:07 PM] #### Deployment incomplete. ####
[12:58:07 PM] Error deploying archive file:/C:/pkgs/svn/mdm/trunk/src/DRM WDK Source Code/Workflows/DrmRequestWorkflowSelection/deploy/sca_DrmRequestWorkflowSelectionComposite_rev3.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Edited by: J Keller on Jun 6, 2013 8:03 AM

Can anyone reply plz???

Provider Not Compatible with client

Similar Messages

Maybe you are looking for