Hello,
We have an C# VS.NET 2003 compact framework application running on Windows
Mobile 5.0, utilising MS SQL Server CE 2.0 against an Microsoft SQL Server
Standard Edition (8.00.2039 SP4) database server.
We have set anonymous subscriptions to expire after 14 days (default). Also,
we use basic authentication for the Windows Mobile 5.0 clients to connect
to our database backend through SSCESA20.DLL (Merge Agent). IIS and MSSQL
are on the same box (Windows Server 2003 X86 with RAM 3583 MB and four processors).
The Snapshot Agent runs once a week and we generate snapshots in the normal
snapshot folder. Of course, the snapshot format is Character mode format
so as to support heterogeneous subscribers and data transformations using
DTS.
We have a very strange issue: Although the anonymous subscriptions are set
to expire within 14 days of a subscriber NOT synchronizing with the backend
server, we have examples of particular subscribers that they have NOT synchronized
for more than a month and when they finally attempt to synchronize with the
backend server, the merge replication synchonization process completes successfully
(!), i.e. they don't get a message saying that the subscription to the publication
'XXXXXX' is invalid (i.e. expired) and that they need to reinitialize by
getting a new subscription.
The backend database has new data every day (10-30 records) and the Snapshot
Agent only runs once a week.
Can you please help me understand what is the reason for this issue ?
Thank you
Panos
Alberto Silva, MVP - 12 Jun 2009 00:07 GMT
Hi,
Check if the following page may apply and explain the behaviour you have
found:
http://msdn.microsoft.com/en-us/library/ms151188.aspx
Read in particular the paragraphs about MergeReplication.
Alberto Silva
> Hello,
>
[quoted text clipped - 34 lines]
>
> http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4149 (20090611) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Panos Administrator - 12 Jun 2009 08:33 GMT
Hello Alberto,
Thank you for the link, however, it seems that it applies only to MS SQL
Server 2008/2005 and not on MS SQL Server 2000 SP4 that we use. In addition,
it mentions that certain stored procedures need to be executed at the Subscriber,
which is not possible in our case since the subscribers are Windows Mobile
clients utilising the MS SQL Server CE 2.0 mobile database which does not
have any stored procs.
Do you have any other suggestions?
Thank you for your time,
Panos
> Hi,
> Check if the following page may apply and explain the behaviour you
[quoted text clipped - 52 lines]
>
> http://www.eset.com
Tim Layton - 25 Jun 2009 15:54 GMT
Hi, this is a rather detailed and complex issue, but I think the best place
to start is to read up on MergeReplication and that should take you in the
right direction.
> Hello,
>
[quoted text clipped - 27 lines]
> Thank you
> Panos