Merge replication on MSDE over internet

Hi,
We are having a dedicated machine (with a fix IP) running SQl2000 and it is
supposed to be the master database. And we are having 4 clients XP machine
running MSDE (without fix IP), and we would like to have a merge replication
to sync. data from / to the client / server. Coz data will be updated on
server or clients side. I have simulated this environment on a LAN
environment and it works but I 'm not sure whether if those clients machine
are connected to the server through internet via ADSL connection(without a
fix IP).
please help ... !!! thanks.
-Wing
you must use the replication ActiveX merge control. Set the
DistributorAddress and the PublisherAddress to be the IP address of your
publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
"Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it
> is
> supposed to be the master database. And we are having 4 clients XP
> machine
> running MSDE (without fix IP), and we would like to have a merge
> replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients
> machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
|||thanks... is there any sample source code on that ? besides using ActiveX
merge control, is there any way not using control ?
also does the ActiveX merge control support VB6, thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> bl
news:%23f8Kxk1yEHA.2540@.TK2MSFTNGP09.phx.gbl g...[vbcol=seagreen]
> you must use the replication ActiveX merge control. Set the
> DistributorAddress and the PublisherAddress to be the IP address of your
> publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
>
> "Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
> news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
on[vbcol=seagreen]
a
>
|||We currently have 4 locations replicating such. What I do is setup SQL Server
to dial VPN setup at our main office (Publisher). Each subscriber dials VPN,
performs replication, and then disconnects the VPN. This works great...they
sync every hour.
"Wing Chan" wrote:

> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it is
> supposed to be the master database. And we are having 4 clients XP machine
> running MSDE (without fix IP), and we would like to have a merge replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
>
|||Hi

> Each subscriber dials VPN,
> performs replication, and then disconnects the VPN.
Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
job or something else?
I'll appreciate any details.
Regards,
|||Yes, just add new steps to the Merge Agent job. First step would be of Type
"Operating System Command (CmdExec)" and would read something like
rasdial vpn_connection_name user password domain:/your_domain_name
Then add another step after the Replication agent to disconnect. Same as
above but the command text would be:
rasdial vpn_connection_name /disconnect
Important Note: It appears that the Merge Agent job step attempts to run
immediately after the first Connect VPN step is run. If you're relying on
NETBIOS name resolution, you WILL need to add a retry on the replication
step. This is simply because it takes a little bit of time for your VPN IP
settings to be configured upon first connection. The first merge attempt
almost always fails for me because it can't locate the Publisher name yet. If
you're connecting via straight IP addresses, then this will not be a problem.
Besides that, this works like a charm for our multi-city office replication
on an hourly basis.
"Carlos Gutierrez" wrote:

> Hi
>
> Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
> job or something else?
> I'll appreciate any details.
> Regards,
>
>

Merge replication on MSDE over internet

Hi,
We are having a dedicated machine (with a fix IP) running SQl2000 and it is
supposed to be the master database. And we are having 4 clients XP machine
running MSDE (without fix IP), and we would like to have a merge replication
to sync. data from / to the client / server. Coz data will be updated on
server or clients side. I have simulated this environment on a LAN
environment and it works but I 'm not sure whether if those clients machine
are connected to the server through internet via ADSL connection(without a
fix IP).
please help ... !!! thanks.
-Wing
you must use the replication ActiveX merge control. Set the
DistributorAddress and the PublisherAddress to be the IP address of your
publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
"Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it
> is
> supposed to be the master database. And we are having 4 clients XP
> machine
> running MSDE (without fix IP), and we would like to have a merge
> replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients
> machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
|||thanks... is there any sample source code on that ? besides using ActiveX
merge control, is there any way not using control ?
also does the ActiveX merge control support VB6, thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> bl
news:%23f8Kxk1yEHA.2540@.TK2MSFTNGP09.phx.gbl g...[vbcol=seagreen]
> you must use the replication ActiveX merge control. Set the
> DistributorAddress and the PublisherAddress to be the IP address of your
> publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
>
> "Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
> news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
on[vbcol=seagreen]
a
>
|||We currently have 4 locations replicating such. What I do is setup SQL Server
to dial VPN setup at our main office (Publisher). Each subscriber dials VPN,
performs replication, and then disconnects the VPN. This works great...they
sync every hour.
"Wing Chan" wrote:

> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it is
> supposed to be the master database. And we are having 4 clients XP machine
> running MSDE (without fix IP), and we would like to have a merge replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
>
|||Hi

> Each subscriber dials VPN,
> performs replication, and then disconnects the VPN.
Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
job or something else?
I'll appreciate any details.
Regards,
|||Yes, just add new steps to the Merge Agent job. First step would be of Type
"Operating System Command (CmdExec)" and would read something like
rasdial vpn_connection_name user password domain:/your_domain_name
Then add another step after the Replication agent to disconnect. Same as
above but the command text would be:
rasdial vpn_connection_name /disconnect
Important Note: It appears that the Merge Agent job step attempts to run
immediately after the first Connect VPN step is run. If you're relying on
NETBIOS name resolution, you WILL need to add a retry on the replication
step. This is simply because it takes a little bit of time for your VPN IP
settings to be configured upon first connection. The first merge attempt
almost always fails for me because it can't locate the Publisher name yet. If
you're connecting via straight IP addresses, then this will not be a problem.
Besides that, this works like a charm for our multi-city office replication
on an hourly basis.
"Carlos Gutierrez" wrote:

> Hi
>
> Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
> job or something else?
> I'll appreciate any details.
> Regards,
>
>

Merge replication agent schedules question.

I am using SQL Server 2000 on Windows 2003 Server. I have two identical
machines running this configuration. Machine A is primary, machine B is
backup. I have setup a merge replication as such: Distributor running on B,
publisher on A, pull subscriber on B. These machines are installed at a
customer site on a new network that exeriences outages and errors. I
currently have the schedule for the snapshot agent to start with SQL Server
agent. I had previously had the same schedule set for the Merge agent.
However, whenever an error occured on the network the merge agent would
report an error and stop. The system is not monitored frequently by the
customer so I need the agent to restart/continue. I changed the schedule
for the merge agent to run once a minute. This solved the immediate
problem. However, I seem to have a similar problem on the snapshot agent
where it fails and won't restart. I ran the snapshot agent manually and the
replication picked back up. I am leery of scheduling it to run periodically
(once a minute) due to overhead. I am new to replication so I am not sure
what is a good combination for scheduling merge replication where the agents
need to report errors and continue attempting to replicate. Is there any
way to have these agents run continuously and restart after an error? Any
suggestions would be appreciated.
TIA
relax. Schedule the snapshot agent to run every minute, hour or whatever
schedule you think is best.
The snapshot will only be generated if a subscriber needs one. Otherwise the
agent will very gracefully quit and go back to sleep.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Mike M." <nospam@.someplace.com> wrote in message
news:uuE5gPi4EHA.1260@.TK2MSFTNGP12.phx.gbl...
>I am using SQL Server 2000 on Windows 2003 Server. I have two identical
> machines running this configuration. Machine A is primary, machine B is
> backup. I have setup a merge replication as such: Distributor running on
> B,
> publisher on A, pull subscriber on B. These machines are installed at a
> customer site on a new network that exeriences outages and errors. I
> currently have the schedule for the snapshot agent to start with SQL
> Server
> agent. I had previously had the same schedule set for the Merge agent.
> However, whenever an error occured on the network the merge agent would
> report an error and stop. The system is not monitored frequently by the
> customer so I need the agent to restart/continue. I changed the schedule
> for the merge agent to run once a minute. This solved the immediate
> problem. However, I seem to have a similar problem on the snapshot agent
> where it fails and won't restart. I ran the snapshot agent manually and
> the
> replication picked back up. I am leery of scheduling it to run
> periodically
> (once a minute) due to overhead. I am new to replication so I am not sure
> what is a good combination for scheduling merge replication where the
> agents
> need to report errors and continue attempting to replicate. Is there any
> way to have these agents run continuously and restart after an error? Any
> suggestions would be appreciated.
> TIA
>
|||That sounds good. Does the subscriber specify it needs a snapshot using the
synchronization transaction at the distribution database or something? I
don't wan't to add to the network traffic by having the publisher bulk copy
all the data to the distributor (machine B) if it is not needed. Will the
snapshot agent log show that it ran and did not generate any data? I'll
give that a try.
Thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e02jkqq4EHA.1452@.TK2MSFTNGP11.phx.gbl...
> relax. Schedule the snapshot agent to run every minute, hour or whatever
> schedule you think is best.
> The snapshot will only be generated if a subscriber needs one. Otherwise
the[vbcol=seagreen]
> agent will very gracefully quit and go back to sleep.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
> "Mike M." <nospam@.someplace.com> wrote in message
> news:uuE5gPi4EHA.1260@.TK2MSFTNGP12.phx.gbl...
on[vbcol=seagreen]
schedule[vbcol=seagreen]
agent[vbcol=seagreen]
sure[vbcol=seagreen]
any[vbcol=seagreen]
Any
>
|||After further review, did I mention that I allow anonymous subscriptions?
When I set the snapshot agent to run once a minute it generates a full
snapshot each time. I am going to disable anonymous subscriptions and see
how that affects it.
"Mike M." <nospam@.someplace.com> wrote in message
news:uhZYeAs4EHA.4092@.TK2MSFTNGP14.phx.gbl...
> That sounds good. Does the subscriber specify it needs a snapshot using
the
> synchronization transaction at the distribution database or something? I
> don't wan't to add to the network traffic by having the publisher bulk
copy[vbcol=seagreen]
> all the data to the distributor (machine B) if it is not needed. Will the
> snapshot agent log show that it ran and did not generate any data? I'll
> give that a try.
> Thanks.
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:e02jkqq4EHA.1452@.TK2MSFTNGP11.phx.gbl...
> the
identical[vbcol=seagreen]
is[vbcol=seagreen]
> on
a[vbcol=seagreen]
agent.[vbcol=seagreen]
would[vbcol=seagreen]
the[vbcol=seagreen]
> schedule
> agent
and
> sure
> any
> Any
>
|||Pull subscription, not anonymous. Snapshot agent set to run each minute.
Same result. The snapshot was generated each minute.
"Mike M." <nospam@.someplace.com> wrote in message
news:uJXn7Vs4EHA.524@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> After further review, did I mention that I allow anonymous subscriptions?
> When I set the snapshot agent to run once a minute it generates a full
> snapshot each time. I am going to disable anonymous subscriptions and see
> how that affects it.
> "Mike M." <nospam@.someplace.com> wrote in message
> news:uhZYeAs4EHA.4092@.TK2MSFTNGP14.phx.gbl...
> the
I[vbcol=seagreen]
> copy
the[vbcol=seagreen]
whatever[vbcol=seagreen]
Otherwise[vbcol=seagreen]
> identical
B[vbcol=seagreen]
> is
running[vbcol=seagreen]
at[vbcol=seagreen]
> a
I[vbcol=seagreen]
> agent.
> would
> the
> and
not[vbcol=seagreen]
the[vbcol=seagreen]
there[vbcol=seagreen]
error?
>
|||for anonymous the snapshot generated every time the snapshot agent is run.
For named it is not.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Mike M." <nospam@.someplace.com> wrote in message
news:%23%23vIIcs4EHA.1396@.tk2msftngp13.phx.gbl...
> Pull subscription, not anonymous. Snapshot agent set to run each minute.
> Same result. The snapshot was generated each minute.
> "Mike M." <nospam@.someplace.com> wrote in message
> news:uJXn7Vs4EHA.524@.TK2MSFTNGP09.phx.gbl...
> I
> the
> whatever
> Otherwise
> B
> running
> at
> I
> not
> the
> there
> error?
>

Merge replication 32-bit IIS - 64-bit SQL Server 2005 -Windows Mobile 5 device

We have setup a 32-bit IIS server on a 32-bit machine. Installed necessary SQL Server components (32-bit replication components). We have installed SQL Server 2005 64-bit SP1 with latest hotfixes on a 64-bit machine.

On the Mobile device we installed SQL Server 2005 Mobile.

When we start mergereplication the problem we have is error 28009 (An instance of the SQL Server Reconciler cannot be created) on the mobile device. I read allot about it, but still have a questetion.

Should this work?

I found the doc: SQL Server 2005 Upgrade Technical Resource Guide:

Note: If your upgrade involves SQL Server CE subscribers, you must perform additional actions on the IIS server. You will need to install SQL Server 2005 client connectivity components along with SQL Server Mobile Edition components on the IIS server. You will also have to replace sqlcesa30.dlll, sqlcerp30.dll, and all the replication components on the IIS server.

From this I conclude it should work or is the doc in error?

If it does not, what can we do?

32-bit SQL Server 2005 on the 64-bit machine should work. (Can a 64-bit SQL Server 2005 run alongside 32-bit SQL Server 2005?).

Beste regards,
Hans Mank

The SQL Server CE components are also needed on the IIS server. Please install those and try again.