I am new in replication, but really need your help... My replication is simple but I am struggling
Set up
-Win 2000 server with sql200
- 2 server, non trusted domain and hapy to use sql authentication.
- Both server have the same sqlexec user and impersonating the sqlserver agent
- I am trying a simple replication between a publisher/ distributer and a subscriber using just one article and it is working when they are in the same LAN
- the snap shot is located in a shared directory, I also used the default directory \\server name\C$\bl bla
- Once I move to the WAN using a VPN the agent fails with fail to proprogate snapshot data
- Note I can register both server and query both of them without a problem using both query analyzer and enrpMgr, so communication is fine...
Where is the problem please ... your help is appreciated
Regards,
Haith,
this could be a number of issues - often it is simply a case of setting up
the alias to an IP address. Have a look at the detailed instructions in this
article: http://support.microsoft.com/?id=321822.
A few extra points outside of the article from when I set it up:
(a) don't use an administrative share to set this up - create an explicit
share as \\server\repldata.
(b) if you use pass-through security then you won't need to set up security
on the fiolder, but with SQL security I have to give the windows guest
account access.
(c) finally, I found I had to add an entry to the Hosts file to be able to
see the snapshot share.
HTH,
Paul Ibison
|||Hi Paul,
Thanks for your prompt reply ...
... My problem is when I have more than one article aded to the publication it comes with the message "The schema script '\\YKUL8K2WEFKEFSZ\D$\ABIS\ReplData\unc\YKUL8K2WEF KEFSZ_Northwind_Northwind\20040527153100\Region_8. sch' could not be propagated to t
he subscriber." As you can see I was just testing using Northwind DB. I have the aliases in place and what is funny is that it works when I have a simple small one article per publication and only a handfull of changes... Is this to do with the size of th
e snapshot (Schema scrip) against the slow rate I have in my link (Down to 23KB at times)... My connection time out is set up really high and I never had any timeout message for both connection and query and I have no probem seeing and accessing the other
server's DB.
I will use your advice and change to a private share and will also edit the host file... But more info in this sympton will really help as I have alot of replication to do and all will have the same problems I beleive...
Thanks again Paul for your help and looking forward to your next reply
|||Haith,
there's no need to convert the share or host file if it's working for one
article. Presumably you are now using pass-through security as I noticed you
have an admin share (D$) which is accessible by local admins? Anyway, if it
is only the initialization that is the problem due to a slow/intermittent
link, I'd consider BCPing the data to a textfile, zip it up, send it over,
restore it then initialize with nosync. After that, choose the slow link
agent profile for synchronization.
HTH,
Paul Ibison
Showing posts with label merg. Show all posts
Showing posts with label merg. Show all posts
Friday, March 23, 2012
Merg replication - data from subscriber is not updated at publisher
Hi,
I try to set Merg replication.
no data that is changed on the subscriber is updated at the publisher.
The updated/new data is removed from the subscriber and he return to
present the publisher data.
I checked scurity issus can find somthing.
Thanks in advance.
Yohai
Yohai,
this sounds like a compensating changes issue. Please have a look at
http://support.microsoft.com/default...&Product=sql2k
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks for the answer.
I didnt mention that we are using MS-SQL 2000 SP4.
does the patch mention on the article is included in this SP ?
Yohai
|||Yes - you have the option to control this process in sp4 (see
http://www.replicationanswers.com/sp4.asp).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I try to set Merg replication.
no data that is changed on the subscriber is updated at the publisher.
The updated/new data is removed from the subscriber and he return to
present the publisher data.
I checked scurity issus can find somthing.
Thanks in advance.
Yohai
Yohai,
this sounds like a compensating changes issue. Please have a look at
http://support.microsoft.com/default...&Product=sql2k
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks for the answer.
I didnt mention that we are using MS-SQL 2000 SP4.
does the patch mention on the article is included in this SP ?
Yohai
|||Yes - you have the option to control this process in sp4 (see
http://www.replicationanswers.com/sp4.asp).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
merg replication
Hi
when want to creat a merg replication , irecieved below error message!!
------------------
The process could not make a generation at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200994)
----------------------------------
Cannot insert the value NULL into column 'nicknames', table 'MSmerge_genhistory'; column does not allow nulls. INSERT fails.
(Source:'Subscriber'. (Data source); Error number: 515
--------------------Check @.@.servername on all servers - I did have a situation like this.
when want to creat a merg replication , irecieved below error message!!
------------------
The process could not make a generation at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200994)
----------------------------------
Cannot insert the value NULL into column 'nicknames', table 'MSmerge_genhistory'; column does not allow nulls. INSERT fails.
(Source:'Subscriber'. (Data source); Error number: 515
--------------------Check @.@.servername on all servers - I did have a situation like this.
Labels:
below,
creat,
database,
error,
generation,
irecieved,
merg,
message---the,
microsoft,
mysql,
oracle,
process,
replication,
server,
sql
Subscribe to:
Posts (Atom)