Merge replication over VPN

I currently have a client who needs to replicate a database between a server
in the office and a computer at home using a VPN connection.
Here is the currnet setup:
-Merge Replication
-Both the server and the client have SQLSERVERAgent logged in with the same
username and password for pass-through authentication
-Subscriber impersonates SqlServerAgent
-Anonymous subscription
The snapshot has been created successfully on the server and I am able to
register the client on the server's Enterprise Manager (so they can see each
other). The replication starts and runs for quite a while (most of the work
is done). Eventually, it fails with the message
//<servername>/<sharename>/<filname>.dri could not be propagated to the
subscriber. With no further details. I don't think it is security related,
because most of the work is already done.
Any ideas what I'm missing?
You might try, from the client, to see if you can browse this share. When I
have set it up, it required an entry in the HOSTS file to map the IP address
to the NETBIOS name.
HTH,
Paul Ibison
|||The share is visible. I fixed that with an entry in the HOSTS file in the
beginning.
"Paul Ibison" wrote:

> You might try, from the client, to see if you can browse this share. When I
> have set it up, it required an entry in the HOSTS file to map the IP address
> to the NETBIOS name.
> HTH,
> Paul Ibison
>
|||OK, if it is running, transferring the snapshot and fails after a while, you
might try increating the -QueryTimeout parameter of the merge agent's
profile.
HTH,
Paul Ibison
|||I did that already as well after having a timeout problem. The current
problem just says that the file could not be propagated to the subscriber.
"Paul Ibison" wrote:

> OK, if it is running, transferring the snapshot and fails after a while, you
> might try increating the -QueryTimeout parameter of the merge agent's
> profile.
> HTH,
> Paul Ibison
>
>
|||Problem Solved:
It turns out that there is no guarantee that the order that records are
inserted during replication will be the same as when they were inserted
originally. Therefore, it is possible that a chile record can be inserted
before its parent, causing a conflict with the foreign key constraint.
After setting all foreign key constraints to "not for replication", the
client took the snapshot without a problem.
"b1@.ckh013" wrote:

> I currently have a client who needs to replicate a database between a server
> in the office and a computer at home using a VPN connection.
> Here is the currnet setup:
> -Merge Replication
> -Both the server and the client have SQLSERVERAgent logged in with the same
> username and password for pass-through authentication
> -Subscriber impersonates SqlServerAgent
> -Anonymous subscription
> The snapshot has been created successfully on the server and I am able to
> register the client on the server's Enterprise Manager (so they can see each
> other). The replication starts and runs for quite a while (most of the work
> is done). Eventually, it fails with the message
> //<servername>/<sharename>/<filname>.dri could not be propagated to the
> subscriber. With no further details. I don't think it is security related,
> because most of the work is already done.
> Any ideas what I'm missing?

Merge Replication Issues

I was trying to test out how well my merge replication is working, so I
created a new table on my main database and on my remote computer I created
the same table but with data in it. I then tried to merge the two up and the
data from my remote computer did not appear on the table on the main
database. What am I doing wrong? Please let me know something...
Corey
Hey --
Well, without knowing all the details...if this was SQL 2K, then you need to
create the table and then add it as an article to the publication...then to
the subscription. So, if you did that already, and started the merge agents
and it STILL isn't working...slap an output file on the merge agent and lets
see what's going on.
Also, try looking in sp_helparticle and see if it even shows up as an
article (sysmergearticles).
Donna
"panacorey" wrote:

> I was trying to test out how well my merge replication is working, so I
> created a new table on my main database and on my remote computer I created
> the same table but with data in it. I then tried to merge the two up and the
> data from my remote computer did not appear on the table on the main
> database. What am I doing wrong? Please let me know something...
> Corey
|||Yes I am using SQL 2k, how would I add the output file to the merge agent?
Sorry, but I am learning as I go. I tried to run the sp_helparticle and i
got the error "Invalid object name 'syspublications'
"Donna W" wrote:
[vbcol=seagreen]
> Hey --
> Well, without knowing all the details...if this was SQL 2K, then you need to
> create the table and then add it as an article to the publication...then to
> the subscription. So, if you did that already, and started the merge agents
> and it STILL isn't working...slap an output file on the merge agent and lets
> see what's going on.
> Also, try looking in sp_helparticle and see if it even shows up as an
> article (sysmergearticles).
> Donna
> "panacorey" wrote:
|||Hmmm...were you in the db that is published in Query Analyzer when you ran
sp_helparticle?
Cause if there's no syspublications, then replication isn't set up properly.
My guess is that you were in master when you ran it...
to put an output file on the agent, follow this article:
http://support.microsoft.com/kb/312292/en-us
For OutputVerboselevel put 3 (undocumented).
Remember to take this off later, as it will very seriously slow down
replicaton.
Look in Books Online for information on sp_addmergearticle, as well as
DEFINITELY read this in Books Online:
Schema Changes on Publication Databases
It's important that you are FULLY aware of what you can and can't do to a
replicated db.
Let us know what you find!
Donna
"panacorey" wrote:
[vbcol=seagreen]
> Yes I am using SQL 2k, how would I add the output file to the merge agent?
> Sorry, but I am learning as I go. I tried to run the sp_helparticle and i
> got the error "Invalid object name 'syspublications'
> "Donna W" wrote:
|||Oh hey, that might be my fault...
sp_helpMERGEarticle...
I always want to forget that...
:D
Donna
"panacorey" wrote:
[vbcol=seagreen]
> Yes I am using SQL 2k, how would I add the output file to the merge agent?
> Sorry, but I am learning as I go. I tried to run the sp_helparticle and i
> got the error "Invalid object name 'syspublications'
> "Donna W" wrote:
|||By default merge replication will whack the table and its data on the
subscriber. While it is possible to put the table in place on the
subscriber, add the rowguid column and the required metadata, in general
this is not recommended.
To make life easier for your self, have merge replication deploy the
subscription itself.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"panacorey" <panacorey@.discussions.microsoft.com> wrote in message
news:1C31DDA1-2696-4470-A929-705C26127870@.microsoft.com...
>I was trying to test out how well my merge replication is working, so I
> created a new table on my main database and on my remote computer I
> created
> the same table but with data in it. I then tried to merge the two up and
> the
> data from my remote computer did not appear on the table on the main
> database. What am I doing wrong? Please let me know something...
> Corey