Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SQL Compact Merge replication no longer works after VS SP1 is installed

0 views
Skip to first unread message

T Thompson

unread,
Aug 19, 2008, 10:40:19 AM8/19/08
to
I have 2 separate machines that recently had a clean install. Both machines
are Windows XP SP3 with Visual Studio 2008. I have a project that uses SQL
Compact Merge replication to a backend SQL 2005 database; In each case after
installing VS 2008 SP1 the merge replication gives the following error after
calling the synchronize methoed of the SqlCeReplication object.

When I reproduced this on machine #2 I verified that the merge process ran
fine before the SP install. Immediately after installing VS 2008 SP1 and
re-running my project I get the same error that I was getting on my primary
development machine.

Any help would be greatly appreciated as I think my only option is to
remove VS SP1?

Error Code: -2147201019
Message: Initializing SQL Server Reconciler has failed. Try again.
Minor Error: 29045
Source: Microsoft SQL Server Compact
------------------

Error Code: -2147198719
Message: The merge process could not connect to the message file from
Subscriber XXXX Check to ensure that the server is running.
Minor Error: 0
Source: Merge replication provider.
------------------

Error Code: -2147201019
Message: The subscription to publication 'Interlink' 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.
Minor Error: 0
Source: Merge Process (Web Sync Server)

T Thompson

unread,
Aug 26, 2008, 5:49:21 PM8/26/08
to
This was solved by installing the new Server Tools 3.5 SP1 (which is a
separate download from VS 2008 SP1) on the IIS box which handled the web
synchronization.


"T Thompson" <tthomp...@hotmail.com> wrote in message
news:OvbKsmgA...@TK2MSFTNGP02.phx.gbl...

Hurrell@discussions.microsoft.com Ian Hurrell

unread,
Oct 26, 2008, 1:41:00 PM10/26/08
to
Not sure if this is useful by i had the exact same problem and resovled it in
a different way...

In the log C:\Program Files\Microsoft SQL Server Compact
Edition\v3.1\sync\SQL\JobTrackMobile

Thread=1754 RSCB=4 Command=SYNC Hr=80045005 ERR:Initialize failed for
DistributorSessionID = 0
Thread=1754 RSCB=4 Command=SYNC Hr=80045901 The merge process could not

connect to the message file from Subscriber

'{7AF625B6-55C4-1BB2-1CD9-F857EDAF8E56}:C:\Program Files\Microsoft SQL Server
Compact
Edition\v3.1\sync\SQL\JobTrackMobile\35.53B1D8E5B625_3E3ED6FD-7D2B-312B-A7FC-368DF046B73F.IN'. Check to ensure that the server is running. -2147198719
Thread=1754 RSCB=4 Command=SYNC Hr=80045005 The subscription to publication
'FL Publication' 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. -2147201019

In the rep monitor:

The merge process could not connect to the message file from Subscriber

'{7AF625B6-55C4-1BB2-1CD9-F857EDAF8E56}:C:\Program Files\Microsoft SQL Server
Compact
Edition\v3.1\sync\SQL\JobTrackMobile\35.53B1D8E5B625_3E3ED6FD-7D2B-312B-A7FC-368DF046B73F.IN'.
Check to ensure that the server is running. (Source: MSSQL_REPL, Error number:

Resolution – after tying everything i.e. reinstalling 3.1 3.5 and 3.5 sp1
and still getting this error

I ran the "Reinitialize subscriptions having data validation failures" job
from the SQlL Server Agent \ Jobs menu in SSMS

hope it works for you!

Ian Hurrell

unread,
Nov 1, 2008, 4:24:00 AM11/1/08
to
I've been suffering a lot with this one!

I just got it on another machine.
All i had done is installed the Server Tools 3.5 sp1 and re ran the
"configure web sync wizard".

My "Reinitialize subscriptions having data validation failures" didn't solve
the problem

Solved by restarting IIS. (i'd previously reinitialized all subs but i don't
think this solved it)

0 new messages