In case, they are not, then install Compact SP2 x86 and 圆4 MSIs from following link as needed: Therefore, if you face any similar issues, make sure that the computer has both x86 and amd64 MSIs of Compact are installed and they are of the same version. Therefore, it throws the exception.Īt any given point of time, the correct state of a 64-bit computer, for SQL Server Compact, would be the following:īoth x86 and amd64 MSIs are of the same version. However, it cannot find native binaries of the same version on the system. When a 64-bit application that uses Compact SP1 or SP2 is running on the computer, it loads the ADO.NET Provider from the GAC (version ). It results in the x86 installation of Compact being different from the 圆4 installation. Installing the 32-bit version of SQL Server Compact 3.5 SP2 upgrades SQL Server Compact 3.5 SP1 x86 installations to SQL Server Compact 3.5 SP2. When you run the application, it fails with the “Unable to load ME dll " exception. You run a 64-bit application that uses SQL Server Compact SP1 or SP2.
On the same computer, you download and install the 32-bit version of SQL Server Compact 3.5 SP2 from the Web. Then, you install the 圆4 version of SQL Server Compact 3.5 SP1. You install the x86 version of SQL Server Compact 3.5 SP1 on a 64-bit computer.
There is a version mismatch which is not enabled as per the policy. When the 64bit application that privately deploys SQL Server Compact SP1 is run, the ADO.NET Provider is loaded from GAC (version ) but native 64bit components are loaded from the application folder which is version. SQL Server Compact 3.5 Service Pack 2 for Windows Desktop: this can be downloaded from here. When the 32-bit version of the SQL Server Compact 3.5 SP2 is installed, it adds the ADO.NET provider () of version to the Global Assembly Cache (GAC) and the native x86 components are put under the %Program Files(x86)% folder. Install these before running the QuickSnap installer. Install SQL Server 2008 R2 (this installs the 32-bit version of SQL Server Compact 3.5 SP2).Then, when you run a 64-bit application privately deploying SQL Server Compact SP1, It fails with the “Version Mismatch" exception.
SSCERuntime-ENU-圆4.msi was first developed on for the Windows 10 Operating System in Microsoft Visual Studio 2010 Ultimate 2010.
The following are some sample scenarios where this policy will be broken, and that will result in one of the previously mentioned two exceptions: This file is considered a FPX (Microsoft Windows Installer Package) file, and was first created by Microsoft for the Microsoft Visual Studio 2010 Ultimate 2010 software package. In order to avoid various inconsistencies, a Compact ADO.NET provider of a certain version can talk only to the Compact native components of the same version. This provider in-turn communicates with the native Compact components. (Exception from HRESULT: 0x8007007E) CauseĬompact based applications generally program against the Compact ADO.NET provider (). Unable to load DLL 'sqlceme35.dll': The specified module could not be found. Please install SQL Server Compact binaries of matching version
This could be due to the presence of multiple instances of SQL Server Compact of different versions. There is also a table here that allows you to determine which Transact-SQL commands, features, and data types are supported by SQL Server Compact 3.5 (which are the same a 4.0 with very few exceptions), compared with SQL Server 20.File version mismatch detected between ADO.NET Provider and native binaries of SQL Server Compact which could result in an incorrect functionality.
Procedural T-SQL – Select Case, If, features Runs on Windows Mobile / Windows Phone platform Privately installed, embedded, with the application