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 ...

Similar Messages

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

'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

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?

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.

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

Hi,
By reading though posts this appears to be a very common and some people have been able to solve it by putting their OracleDataAccess.dll and support files in the same folder as the exe. However, I tried putting the OracleDataAccess.dll, oci.dll, ociw32.dll, orannzsbb11.dll, and oraocci11.dll in the folder and the problem persists.
This application works fine on my development system (Windows 7 64, VS2010 SP1) and 2 of our 3 servers (Windows 2008 R2). But on this one server it does not work! The problem first appeared when a developer installed ODT with ODAC 112030 on server. We installed a full version of the 11.2.0.1.0 Oracle Client (this matches our other servers) and removed the clients created by the ODT with ODAC 112030 install. However, I fear there is something somewhere that was not deinstalled causing the issue. Any thought on how we can track down and eliminate this problem.
Thanks,
Jerry
Edited by: user13142870 on May 22, 2012 9:51 AM

I changed the CPU to x86 in the solutions and the project is now working.

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

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.

Cannot publish Webpart - "Invalid SPlistItem. The SPListItem provided is not compatible with a Publishing Page"

Hello All,
I have seen this error message discussed in other posts on the forums here but the solution of deactivating and reactivating server publishing/infrastructure are not working for me. In fact I encountered additional errors when reactivating publishing at
the site level. Powershell was necessary to reactivate site level server publishing.
Here is detail of the error I get when attempting to publish:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 18/11/2014 08:59:05
Event time (UTC): 18/11/2014 08:59:05
Event ID: e2e43649e2164e399fe0aa85892a002c
Event sequence: 165799
Event occurrence: 17
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1827921427/ROOT-1-130607489469090399
Trust level: WSS_Custom
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\portal.cooperstc.com443\
Machine name: CTCSP2
Process information:
Process ID: 7392
Process name: w3wp.exe
Account name: COOPERS\svcSPPortalAppPool
Exception information:
Exception type: ArgumentException
Exception message: Invalid SPListItem. The SPListItem provided is not compatible with a Publishing Page.
Request information:
Request URL: https://portal.cooperstc.com:443/CLG/Student/Videos/Pages/Test101.aspx
Request path: /CLG/Student/Videos/Pages/Test101.aspx
User host address: 10.33.50.119
User: COOPERS\yangro
Is authenticated: True
Authentication Type: Negotiate
Thread account name: COOPERS\svcSPPortalAppPool
Thread information:
Thread ID: 41
Thread account name: COOPERS\svcSPPortalAppPool
Is impersonating: False
Stack trace: at Microsoft.SharePoint.Publishing.PublishingPage.GetPublishingPage(SPListItem sourceListItem)
at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageStateControl.RaisePostBackEventForPageRouting(String eventArgument, SPRibbonCommandHandler control, RaisePostBackEventDelegate raisePostBackEventDelegate)
at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageSaveAndStopEditHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

DeActive and then ReActivate Sharepoint Site Publishing Infrastructure feature at both Site And Web level Scope.
To Deactivate at web level, Open SharePoint Site. Click on Site Actions -> Site Settings, then click on Manage site features and then Deactivate Publishing Infrastructure feature.
Similarly you can deactivate at site level, Open SharePoint Site. Click on Site Actions -> Site Settings, then Site collection administration and then go to Site collection features. there deactivate Publishing Infrastructure feature.
To Reactivate again the feature, follow the above steps.
http://www.c-sharpcorner.com/Blogs/15338/invalid-splistitem-the-splistitem-provided-is-not-compatibl.aspx
1.The simple thing is to try deactivate and reactive the publishing features both at site collection and site level.
2. If the above doesn't work then proceed to below PowerShell script.
$site = Get-SPSite "http://www.mysites/ "
$web = $site.openweb()
$correctId = $web.Lists["Pages"].ID $web.AllProperties["__PagesListId"] = $correctId.ToString()
$Web.AllProperties["__PublishingFeatureActivated"]="True"
$web.Update()
3. The key point is PublishingFeatureActivated bag which has to be true .
http://webcache.googleusercontent.com/search?q=cache:5xpx-C9kKgsJ:nagendra-gunaga.blogspot.com/2013/11/the-splistitem-provided-is-not.html+&cd=4&hl=en&ct=clnk&gl=in
If this helped you resolve your issue, please mark it Answered. You can reach me through http://itfreesupport.com/

The SPListItem provided is not compatible with a Publishing Page.

Hi Everyone,
I know there are a few previous resolution to this issue on TechNet. Secifically:
here... but i'm not convinced by the resolution of this issue.
Basically we have exactly the same problem, but over hundreds of pages that were moved by a 3rd party. You can see my dilemma, I dont want to have to go and recreate all the pages.
Anyone got any new ideas about how to fix this?
Cheers,
Michael

Hi,
I understand that you get the following error message when checking in a publishing page.
"Invalid SPListItem. The SPListItem provided is not compatible with a Publishing Page."
This issue is typically a SharePoint Publishing feature issue on the site/site collection. You can deactivate and reactivate the feature and see how it works.
Alternately, you can activate SP 2010 Publishing Feature using PowerShell. Check the following link for more information:
SharePoint 2010 Publishing Feature Activation
http://social.technet.microsoft.com/wiki/contents/articles/18293.sharepoint-2010-publishing-feature-activation.aspx
Thanks.
Tracy Cai
TechNet Community Support

"The version of this file is not compatible with the version of Windows you're running.[...]".What can I do?

I must run a 32-bit programe on a windows 64-bit operating sistem, and i receive this message:"The version of this file is not compatible with the version of Windows you're running.[...]". I tried with Troubleshoot compatibility - didn't
work. I tried set to run in compatibility mode for Windows XP in file properties window and it didn't work. What can I do more? I
must run this programe to acces my database.

Hello qqnicol,
What program do you run?
Please contact the software provider to confirm if this 32-bit program can run in 64-bit Windows.
As some programs can only run in specific version of Windows, please download the right version of software.
Most programs designed for the 32-bit version of Windows will work on the 64-bit version of Windows. Notable exceptions are many antivirus programs.
Device drivers designed for the 32-bit version of Windows don't work on computers running a 64-bit version of Windows too.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

Windows desktop application -- version of this file is not compatible with the version of Windows you're running

I am developing on 64-bit Windows7 Enterprise using VisualStudio 2013. I created a new Windows desktop VB.net application and just created a release build of the default solution/project targeting "Any CPU". I provided the EXE to a
colleague who is also running 64-bit Windows7 Enterprise but receives the following error...
"The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see
whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."
I changed the build configuration to create a "x86" build but my colleague received the same error. Any ideas why this would be happening (I checked and my colleague has .Net4 Framework installed as well)? Thank you for your time and
response!
Sunish Abraham
"The version of this file is not compatible with the version of Windows you're running.
Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."

Hi sunisha,
According to your description, you'd like to run the application in your colleague's computer.
I provided the EXE to a colleague who is also running 64-bit Windows7 Enterprise but receives the following error...
If you want to test the application, you could provide the whole Debug folder to colleague instead of the single exe.
"The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."
Check if the collegue's computer is running 64-bit windows:
Enter Control Panel, click on System and Security.
Under this, you can view the system type. This will describe whether you have 32-bit or 64-bit.
You can also try compatiblity mode.
If the program is not compatible, then you may try to install and run the program in compatibility mode.
Use the following steps:
1)   Right click on the Program
2)   Click on Properties
3)   Click on Compatibility tab
4)   Select Run this program in compatibility mode and select Windows Vista or whatever operating system the program was running successfully.
And if you still have questions, I suggest you deploy the application to the Local Network with clickOnce, then your collegue can install the application from the network.
#ClickOnce deployment
http://msdn.microsoft.com/en-us/library/t71a733d(VS.80).aspx
And also, you could recreate a new small application in your computer in Any CPU, then check if this small new application can work well in your colleague's computer. This can judge if the problem is caused by your application.
If you have any other concern regarding this issue, please feel free to let me know.
Best regards,
Youjun Tang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Provider is not compatible with the client

Similar Messages

Maybe you are looking for