Devart Forums

when I use the manifest setting ProviderManifestToken="Ora10gR2" in SSDL, I get this exception.

EXCEPTION (System.Data.ProviderIncompatibleException): The provider did not return a ProviderManifest instance

the manifest token was infact generated by the Devart Entity Developer whie connecting to Oracle 10g.

any ideas?

thanks
slaxman

Could you please replace "Ora10gR2" with "ORA"?
We will fix this issue in one of the nearest builds.
Please notify me if anything goes wrong.

Below is the detailed exception I get.
System.Data.ProviderIncompatibleException: The provider did not return a Provider Manifest instance. ---> System.ArgumentException: Could not determine storage version; a valid version hint is required.

My version of Devart on Server is::6.30.185.0
Server is Windows 32 machine with .Net framework 4.

My development machine is Windows 7 with latest devart version recently downloaded from nuget.
Devart Version:: 8.4.457.0

Please help

My ConnectionString looks like this
<add name="Entities" connectionString="metadata=res://*/Model1.csdl|res://*/Model1.ssdl|res://*/Model1.msl;provider=Devart.Data.Oracle;provider connection string="User Id=myuser;Password=mypassword;Server=myserver;Home=OraClient11g_home1;Persist Security Info=True"" providerName="System.Data.EntityClient" />

Please specify:
a) the value of the ProviderManifestToken property of your model
b) the version of your Oracle server

oracle Client Version: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64
With the Partitioning, Real Application Clusters, Automatic Storage Management,
Data Mining and Real Application Testing options (with complications)

ProviderManifestToken="Oracle, 11.2.0.4"

mukund.katpatal wrote:latest devart version recently downloaded from nuget

Only Express edtion is available via NuGet Gallery. The Entity Framework support is included in the Professional and Developer editions of dotConnect for Oracle. You can check your current edition via the Tools > Oracle > About menu of Visual Studio.

If you installed Professional edition and this didn't fix the issue, please specify the full call stack with all inner exceptions.