Error using Merge Replication to SQL Compact 3.5

We are getting the following error when syncing with sql server (2005 SP3):

Initializing SQL Server Reconciler has failed. Try again.; The merge process could not connect to the message file from Subscriber ‘{F238C7BC-E13B-40E4-99F2-F11A203BD65A}:W:\http_content\Secure\SECURE_PROD\data_merge\30.18F5D9B4BCC7_B1415013-9FB7-424A-AB45-643A0D4A6320.IN’. Check to ensure that the server is running.; The subscription to publication ‘COREPublication’ could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription.

  • How do I enforce data integrity rules in my database?
  • SQL Query need to show blank records
  • How to grant the database owner (DBO) the EXTERNAL ACCESS ASSEMBLY permission?
  • Is COUNT(*) in SQL Server a constant time operation? If not, why not?
  • Default column value based on the value of a different column
  • Implement Lucene on Existing .NET / SQL Server stack with multiple webservers
  • As far as I can work out, everything is fine on the sql server side. I’ve done all the checks mentioned in the error message.

    Can anyone tell me what this error message actually means? Is it unable to read the shapshot file off the server? (this is my guess currently).

  • How to avoid NULL when using Value-Name Mapping in SQL
  • Linux - PHP 7.0 and MSSQL (Microsoft SQL)
  • Pass A User-Defined Table to a Stored Procedure
  • If DateTime Object Is Null
  • Using PIVOT in SQL Server 2008
  • SQL Server : Msg 102, Level 15, State 1, Line 2 Incorrect syntax near '='
  • 2 Solutions collect form web for “Error using Merge Replication to SQL Compact 3.5”

    This is caused when you have SQL Compact 3.5 SP1 installed, and talking to a pre-SP1 server. Something changed in the service pack that stops it working.

    Uninstalling the service pack works, so this is our current workaround until the service pack is approved and installed in production (i.e. the server).

    I cannot test at this time, but I assume that SP1 talking to a SP1 server works fine.

    I am using both 3.5 SP1 client and 3.5 SP1 server and both works perfectly well.
    The version of both components is 3.5.5692.0.
    The referenced client assembly shall be in the .NET client solution (running on CE).

    I got the same error (and it did not make any sense) but simply restarting the server (in my case Windows 2003 Server) made the error go away. It may have to do with some previous version component still running after installation.

    You can verify that you have 3.5 SP1 running by visiting its URL, e.g.

    Under “SQL Server Compact Modules Test”, it should say “sqlcesa35.dll” Version 3.5.5692.0, and all tests should pass with status SUCCESS.

    MS SQL Server is a Microsoft SQL Database product, include sql server standard, sql server management studio, sql server express and so on.