Merge reversed

Running Win 2000 & SQL 2000
I have a merge publication/subscription (rows are
filtered by location), replicating data between 16
servers (15 remote location & a main office). When data
is changed at the a remote location, the changes gets
propagated to the main office, but at some point, the
change gets reversed.
Any idea what is causing this?
Larry,
when you say it gets reversed, do you mena the row is deleted from the
subscriber? This could be caused if you are partitioning data and a row has
been added on a subscriber which doesn't accord with its filter.
HTH,
Paul Ibison
|||Look in the conflict table, for the article, on the publisher. This might
give you a clue as to what is going on.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Paul,
No the row is not deleted, but changed back to its
original state, prior to being updated at the
subscriber. This happens sporadically, but is causing
MAJOR problems.
Larry...
|||Rand,
There is nothing in the conflict tables for any article
in the publication.
Larry...
|||I saw your reply to Rand and if both filtering and conflicts are ruled out
(and no user on the publisher is altering the data!) then this is very
strange. I'd use profiler or an audit trigger to capture what is going on.
HTH,
Paul Ibison
|||Thanks Paul...will do.
|||Does the MSmerge_history table on the distributor offer any reason why
the updates were not applied?
Reinout Hillmann
SQL Server Product Unit
This posting is provided "AS IS" with no warranties, and confers no rights.
anonymous@.discussions.microsoft.com wrote:
> Rand,
> There is nothing in the conflict tables for any article
> in the publication.
> Larry...
>

Merge Replication with different Service Packs

I have a Win 2003 server with SQL 2000 SP3 that is publisher and distributor for several merge replication publications. Subscribers are a mixture of SQL 2000 (running SP3 and SP4) and MSDE. I've run into a problem in creating publications that is fixed in SP4 but for various reasons I can't update all of the subscribers that are running SP3. I don't expect any issues updating just my server but will I have any issues running SP4 on my server and SP3 on the subscribers?

Thanks for the help.

GaryI have not experienced any issues related to mis-matched service packs in my development environment. On the other hand, I have not yet deployed to full scale production.

Regards,

hmscottsql

Merge replication using wins mobile 5.0

Hi all,

I have developed a mobile program with sql server 2000 merge replication. It works fine in Win mobile 2003 OS, but, not working at all after I upgrade the mobile OS to Win mobile version 5.0

Does anyone have any idea at all what's going on?

Thanks a lot.

AngelaC

What makes you think it's not working, are you getting an error message?|||

Thanks Greg for your prompt reply. The pocket pc program is written in vb.net and I got the following error when I tried to run these codes:

Codes:

Dim replSQL As New SqlCeReplication

...

replSQL.AddSubscription(AddOption.CreateDatabase) <-- error occur

Error raised:

"cannot view indexed property"

I have sp3a installed in SQL Server 2000 and "sqlce.ppc3.arm.CAB" installed in the pocket pc.

Any idea?

Thanks!

|||

Can you catch the exception and dump the HRESULT, Major Number, Minor Number, Native Number, Error Collection ... etc from the exception for us to understand your problem better.

Thanks,

Laxmi Narsimha Rao ORUGANTI, SQL Ev, Microsoft Corp.

|||

Hi Laxmi,

Here is the error message;
Errors: System.data.sqlserverce.SqlCeErrorCollection

Count: 2

Item: Cannot view indexed property

HResult: -2147467259

InnerException: Nothing

Message "SqlCeException:

NativeError 28558

Source: "Microsoft SQL Server 2000 Windows CE Edition"

Any idea?

Thanks

Merge replication issue - The subscription to publication is invalid

I am trying to configure a merge replication of publication with 151 table-articles over 128 kbps line via proxy (Win XP, WinProxy), which is used for connection to internet as well.
The whole snapshot runs well, all the data are pumped to the subscriber and all dri, trg etc. scripts are executed without problem, but instead of the message "No data needed to be merged" comes out this error message:

Last Command: {call sp_MSgetreplicainfo(?,?,?,?,?,?,?)}

The subscription to publication 'Katalog' is invalid.
(Source: Merge Replication Provider (Agent); Error number: -2147201019)
--------------------------
General network error. Check your network documentation.
(Source: FANTOM (Data source); Error number: 11)
--------------------------

When I try to replicate the small Northwind database, everything works fine, no errors. When I try to replicate only a few tables from my big database, everything works fine.

Thank you very much for any ideas.The problem is probably in WinProxy. When comunicating without Proxy everything goes OK.|||Hi,

I had seen your psting and asking your help.

How do I use the FTP option in Merge Replication

I am using Merge Replication on SqlServer 2000 with SP2 and MDAC2.7 loaded on my system.
My database version is 8.00.534 on Windows2000 Advancedserver.

Both Publisher and Subscriber are running with same versions.

I created a publication and I created a pull subscription using internet.
I want the subscriber machine to access the Publisher
machine via ftp and get the Snapshot and do
Synchronization.

I had setup the following parameters at the Publisher side
for the publication.

1.Generate snapshots in the following location as

\\myservername\D$\Microsoft SQL Server\MSSQL\REPLDATA\ftp which is UNC shared with full access.

2.Checked - Subscribers can access this folder using FTP

ftpservername -myservername
port-21

Login-Anonymous, no password

3.At subscriber side I had setup SnapshotLocation property as
Download the folder using File Transfer Protocol - checked

I get the following errors at Synchronization time
After configuring subscriber for merge replication i am getting staus as succeeded at the subscriber.

when performing data modifications I am getting following errors during synchronisation time.

Errors

Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script '' could not be propagated to the subscriber.

Category:AGENT
Source: SRVH
Number: 0
Message: The process could not connect to FTP site 'HERITAGEAMERICA' using port 21.

Category:OS
Source:
Number: 12007
Message: The server name or address could not be resolved

The schema script '' could not be propagated to the subscriber. The step failed.

Microsoft conformed this is a bug and that details are
Question number is Q318592.
BUG #: 356652 (SHILOH_BUGS) BUG #: 356652 (SHILOH_BUGS)

Microsoft confirmed that this is a bug when we use different versions check with the Question in microsoft site in fixes.

I am getting same error for same versions also.

Can anyone help me on how to use FTP for accessing
Snapshots?

Thanks|||Hello,

I have not any experience with using FTP for merge replication over internet, we are using VPN connection to the server on port 1433.
But as far as I understood, you do not get the error message when transferring a snapshot but at the moment, when the distributor needs to propagate data changes between publisher and subscriber.
I suppose it is important when do you get the error message: whether on the very beginning of applying the snapshot or at the end.
Also would be useful to check, whether the FTP connection is reliable (proxies, switches etc.).

Caruso|||Hi

May be you can help me wit a minor problem in Merge replication. I am trying to perform merge replication on two SQL Server 2000 databases on Windows Nt 4.0 platform using TCP/IP and FTp. Have set everything in Publication and Subscriber for FTp and the subscriber can connect to publisher.

I am getting the followiing error message afetr running replmerg.exe withh all required parameters for FTP.

Microsoft SQL Server Merge Agent 8.00.194
Copyright (c) 2000 Microsoft Corporation

Connecting to Subscriber 'RAJ'
Connecting to Distributor 'VTPL'
Initializing
Connecting to Publisher 'VTPL'
Retrieving publication information
Retrieving subscription information
Snapshot files will be downloaded via ftp
Connecting to ftp site 'VTPL'
The subscription has been marked for reinitialization. Reinitialization will occur the next time you synchronize this subscription.
The schema script '\\VTPL\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\ftp\VTPL_Caryaire_F2\2003010 7120306\RightMain_1.sch' could not be propagated to the subscriber.
Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script '\\VTPL\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\ftp\VTPL_Caryaire_F2\2003010 7120306\RightMain_1.sch' could not be propagated to the subscriber.
Category:AGENT
Source: VTPL
Number: 0
Message: The process could not retrieve file 'VTPL_Caryaire_F2\20030107120306\RightMain_1.sch' from the FTP site 'VTPL'.
Category:OS
Source:
Number: 12003
Message: 200 Type set to I.
200 PORT command successful.
550 VTPL_Caryaire_F2\20030107120306\RightMain_1.sch: The system cannot find the path specified.
550 VTPL_Caryaire_F2\20030107120306\RightMain_1.sch: The system cannot find the path specified.

The process finished. Use CTRL+C to close this window.

I am desparately in need of a solution. Can anyone help me out?

Thanks and regards,
Anamika|||Hi,

Anamika, first thing I would like you to do is check the verison of SQL server 2000. Merge Replication module has some problems. It have been fixed in the SQL server SP3. It is essential to apply this pack on SQL server.

Secondly you need to check ftp settings. your ftp service or root directory of ftp is not configured properly. Due to this you are getting "The process could not retrieve file 'VTPL_Caryaire_F2\20030107120306\RightMain_1.sch' from the FTP site 'VTPL'. "VTPL_Caryaire_F2" parent folder should be root of ftp site.
Details are available in windows or in IIS about ftp configuration.

Merge Replication Agents

Hi everybody,
I have a system of 2 PC, with installed Win XP and SQL 2000. I
configured one PC as Publisher and Distrbutor, and the other as a
Subscriber with a "push" subscription. The snapshot and the merge
agents are running on the Publisher/Distributor. This PC is always ON
for 24 hours everyday, while the subscriber PC at the evening is
turned off and restarted at the morning.
Looking the Replication monitor at the morning, I see red cross on
both agents (snapshot and merge) and the synchronization doesnt' seem
working; if I restart the agents a message tells that the agent is
already running and the red flags disappear.
Anyone can help me to undertand better the situation, or give me some
suggestion?
Thanks a lot.
Marco
What error messages exist for the agents when there is a red cross - can you
please post it up. I'd expect that the merge agent would be killed if it is
synchronising during the process of rebooting the subscriber, but if there is
a schedule or it is set to run continously then it should restart ok. The
snapshot agent shouldn't be running at all after initialization. So, perhaps
the initialization never worked, and the merge agent failed because the
snapshot agent hadn't run? Anyway, please post up some more info and things
whould get clearer.
Paul Ibison
|||On 19 Giu, 17:57, Paul Ibison <Paul.Ibi...@.Pygmalion.Com> wrote:
> What error messages exist for the agents when there is a red cross - can you
> please post it up. I'd expect that the merge agent would be killed if it is
> synchronising during the process of rebooting the subscriber, but if there is
> a schedule or it is set to run continously then it should restart ok. The
> snapshot agent shouldn't be running at all after initialization. So, perhaps
> the initialization never worked, and the merge agent failed because the
> snapshot agent hadn't run? Anyway, please post up some more info and things
> whould get clearer.
> Paul Ibison
Hi Paul,
I don't know exactly what kind of error there is, because I dont' have
the PC with me; this problem has been explained me by another
technician that is testing the system. But I know that the merge agent
is setted to run continously, and that the synchronization was working
when I setted the replication process; only I tested it with the 2 PC
both running and I didn't test the condition with 1 PC running and the
other PC turned off.
|||OK - there's not much I can do without the error message. Try to get it off
your colleague and post it up and I'll take a look.
Cheers,
Paul Ibison