Merge Replication MS SQL CE 3.5 <-> SQL SERVER 2005

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

WernerG - 16 Jul 2008 13:10 GMT

Hi there.

I have been trying to get merge replication to work between a Windows CE
device with SQL Server Compact Ed 3.5 and SQL Server 2005. I have made good
progress but got stuck with an error that Google can’t help me with. Firstly,
I will discuss my progress for those who might hope to get as far as I have.

1.) Installation steps on the DBase server
- Install IIS
- Install SQL Server 2005
- Install SQL Server Compact 3.5 Tools. You need this for the IIS part
because the tools that come with 2005 cannot work with v3.5
2.) Installation steps on your development env
- Install VS 2008 with which you create a Compact DB v3.5
- Install MS SQL 2008 RC0 SSMC which will be needed to setup a
subscription from the Compact DB to the publication on the SQL Server 2005.
The following is needed to install MS SQL 2008 SSMC:
-> Install the latest Windows installer 4.5
-> Install .NET Framework 3.5 SP1 beta
- Configure windows firewall to allow remote connections etc. (Important)
3) Setup a publication on MS SQL 2005.
- Create a publication
- Configure the snapshot directory share folder with the correct
permissions
- Run the Web Sync Wizard under Start->programs->MS SQL Compact 3.5 that
we installed in step 1.
4) Setup the Subscription
- Run SSMC ( the one that comes with SQL Server 2008 RCO)
- Connect to the Compact DB 3.5
- Setup a subscription

This is where I get stuck. I have determined that I do have access to the
IIS web share. I also have access to the snapshot share directory. All
permissions are correct for the IIS anonymous user etc. When I want to
conclude my subscription I get the following error:

The merge process could not connect to the message file from Subscriber
'{5251EDCC-B1EE-4900-9E5A-87999688E431}:C:\Program Files\Microsoft SQL Server
Compact
Edition\v3.5\sync\SQL\CEREP\30.BB743578CCED_616689DE-76F8-4BB0-A9A6-7921AF3E48FD.IN'. Check to ensure that the server is running.
HRESULT 0x80045901 (0)

I have no idea what is causing this. If it is firewall related then I don’t
know which executables to unblock etc.

Any ideas will be greatly appreciated

Reply to this Message

Paul G. Tobey [eMVP] - 16 Jul 2008 16:09 GMT

It looks to me like the SQL Server instance might not be running; worth a
quick verification. I didn't run into this during my own recent MergeRep
work. I never did step 4. I just created the subscription in my code
running on the device. I suppose that there could be some problem with
using this SQL2008 code or something...

Paul T.

> Hi there.
>
[quoted text clipped - 49 lines]
>
> Any ideas will be greatly appreciated

Reply to this Message

WernerG - 17 Jul 2008 09:05 GMT

I guess it is running. To access the publication the wizard needs to scan for
them first. So I assume if the scan picked it up then all is well.

What I don’t understand why the error message is so cryptic. In no way does
it help me to understand what the problem is.

The Merge Process is a concept not an actual process that can connect to
something. We are merging. That’s like saying the reading process cannot open
the book so we can’t read. No sense at all. Highly frustrating for me.

Thanks for the help.

> It looks to me like the SQL Server instance might not be running; worth a
> quick verification. I didn't run into this during my own recent MergeRep
[quoted text clipped - 3 lines]
>
> Paul T.

Reply to this Message

Laxmi Narsimha Rao Oruganti [MSFT] - 17 Jul 2008 16:49 GMT

30.SESSION_ID.IN is a temporary message file that gets created by Server
Agent (SA) with a list of changes received from Client Agent (CA). I have
the following questions to you:

1) When this error shows up, were you able to see this file still lying
there and has got some size (want to know whether upload of changes
successful). It may not actually exist as these are temporary files and we
clean them up once we are done with it.

2) The directory "C:\Program Files\Microsoft SQL Server Compact
Edition\v3.5\sync\SQL\CEREP\" does not have the necessary permissions for
Replication Reconciler to start reading the file. This module impersonates
the logins you provide (PublisherLogin, InternetLogin). Do these logins
have permissions on this folder? Are you running the IIS and SQL Server on
Windows Vista/Server 2008. If so, we need to dig more as there are so many
security related changes in Windows Vista/Server 2008 that might interfere
here.

The other thing you could try is to enable full logging of SA as specified
in Books Online and see what does SA log look like. Since, this is
somewhere in replication reconciler, look up on SQL Server side books online
if there is any way to get a log on that side.

Thanks,
Laxmi [Disclaimer: All postings are as-is and confer no rights]

> Hi there.
>
[quoted text clipped - 49 lines]
>
> Any ideas will be greatly appreciated

Reply to this Message

WernerG - 18 Jul 2008 15:47 GMT

Thanks for the reply.

I appreciate it. I have since then found the problem solved on technet
forums. I had to uninstall SQL Server v3.5 SP1 and reinstall the standard
one. This instantly fixed my replication issue. However... unfortunately for
me uninstalling the SP1 made the compact database useless in my application
as there seems to be a bug in the vanilla install of VS2008 and you cannot
actually add any compact databases as data sources because you get the
following error that the SP fixes:

An unexpected error has occurred.
Error Message:
Could not load type
'Microsoft.VisualStudio.DataDesign.SyncDesigner.SyncFacade.SyncManager' from
assembly
'Microsoft.VisualStudio.DataDesign.SyncDesigner.DslPackage.Version=9.0.0.0,
Culture=neutral, PublucKeyToken=b03f5f7f11d50a3a'

My boss is going to crusify me. I am making absolute no progress with my
Microsoft implementations. Must go linux.

> 30.SESSION_ID.IN is a temporary message file that gets created by Server
> Agent (SA) with a list of changes received from Client Agent (CA). I have
[quoted text clipped - 75 lines]
> >
> > Any ideas will be greatly appreciated

Reply to this Message

Laxmi Narsimha Rao Oruganti [MSFT] - 18 Jul 2008 20:33 GMT

I am really sorry about that and I hope you will have better time with
Microsoft Technologies going ahead.

All the best,
Laxmi [Disclaimer: All postings are as-is and confer no rights]

> Thanks for the reply.
>
[quoted text clipped - 112 lines]
>> >
>> > Any ideas will be greatly appreciated

Reply to this Message

Ian Hurrell - 26 Oct 2008 18:44 GMT

Not sure if this is useful by i had the exact same problem (I think) 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!

> I am really sorry about that and I hope you will have better time with
> Microsoft Technologies going ahead.
[quoted text clipped - 118 lines]
> >> >
> >> > Any ideas will be greatly appreciated

Reply to this Message