Merge SQL 7 to 2000 problem

I am having a problem running a merge replication between
a SQL 7 publisher/distributor and a SQL 2000 subscriber
(push). After the subscription is initialized, the agent
fails with the error "The process could not query row
metadata at the Subscriber." The error details
says "Could not find stored procedure ''." A clip from
the log is below. This same merge replication works fine
from SQL 7 to SQL 7, but fails to SQL 2000. I have tried
2 different SQL 2k boxes with the same error.
The replication job logs in using SQL Server
authentication. Account is system administrator and dbo
on subscriber. Distributor runs under sa. Both Servers
are at latest SP levels. KB search has turned up no help.
Thanks for any ideas!
~~~~~~~~~~~~~~~~~~snip~~~~~~~~~~~~~~~~~~~
Percent Complete: 55
Processing article 'RequestStatusHistory'
Repl Agent Status: 3
chrs4.ITWorkRequest: {call sp_MSenumcolumns (?,?)}
chrs4.ITWorkRequest: {call sp_MSenumchanges(?,?,?,?,?)}
CHHIST.ITWorkRequest: {call sp_MSgetrowmetadata
(?,?,?,?,?,?,?)}{call sp_MSgetrowmetadata(?,?,?,?,?,?,?)}
{call sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}
Percent Complete: 0
The process could not query row metadata at the
Subscriber.
Repl Agent Status: 6
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number:
Message: {call sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call sp_M
Repl Agent Status: 3
Percent Complete: 0
Category:SQLSERVER
Source: CHHIST
Number: 2812
Message: Could not find stored procedure ''.
Repl Agent Status: 3
Could not find stored procedure ''.
Disconnecting from Publisher 'chrs4'
Disconnecting from Subscriber 'CHHIST'
Disconnecting from Publisher 'chrs4'
Disconnecting from Distributor 'chrs4'
George,
this is not a supported configuration. For merge replication, a SQL 7.0
publisher can only publish to a SQL 7.0 Subscriber.
Rgds,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Thanks for the reply. I read the "...Different Versions"
article in books online, but obviously scanned too
quickly. I see the limitation now for merge, but not for
snap and trans. You might help out "Nick Horrocks" with
an answer to his thread "Unable to create Merge
subscription".
George

>--Original Message--
>George,
>this is not a supported configuration. For merge
replication, a SQL 7.0
>publisher can only publish to a SQL 7.0 Subscriber.
>Rgds,
>Paul Ibison
>(recommended sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
>
>.
>
|||Thanks for the prompt - have posted to Nick as well.
Rgds,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

>--Original Message--
>Paul,
>Thanks for the reply. I read the "...Different Versions"
>article in books online, but obviously scanned too
>quickly. I see the limitation now for merge, but not for
>snap and trans. You might help out "Nick Horrocks" with
>an answer to his thread "Unable to create Merge
>subscription".
>George
>
>replication, a SQL 7.0
>.
>

Merge Replication-Apply BCP files

How can i apply a BCP files generate by Distributor in the Suscribers.

I don′t know wich parameters BCP.EXE need.

Thanks

Can you explain why you need to manually apply them? Is the merge agent not applying them for you?|||

I need to manually apply because there is few information, and i've configured suscription with the option to no send the schema tables.

I've configured the replication via internet (is slow for a very large tables)

But now i need to send data to the suscribers.

Thanks

|||

manually applying the bcp files is not recommended. If you're having problems, then let us know what they so we can walk you through a solution.

What part is slow, applying the snapshot to the subscribers? Are these large tables? Are you using filtering, and using the dynamic snapshots? Is the agent failing? How would bcp'ing the data across the internet be any faster than merge agent applying the snapshot?

|||

I only need to know how can apply manually the BCP files on the susbcribers.

Any body knows what parameters i have to use to do this.

Thanks

|||I thinks I am having same requirements like Jorge,

See What I am looking for is quit similar to Jorge's case,

I have 2 Database Servers, I have set Merge Replication (Pull) between them,

But Sometimes The Connectivity between both of them is not available for many days, still data needs to be transfered through CD.

I thinks this problem is relavant, if not pls ignor, and pls give some solution

Merge Replication works then fails, works then fails, and so on

I have a merge replication environment with one central
publisher/distributor and 35 clients. The merge uses continuous
replication. At the moment, 31 of the 35 subscriptions have error this
error:
The process could not check existence of generation at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147201003)
General network error. Check your network documentation.
(Source: SERVER002 (Data source); Error number: 11)
Occasionally some will start working again; and then later fail again. I'm
sure that all permissions must be correct because they work 70 to 80 % of
the time. I don't understand why so many fail so frequently though, and
then why they start working again. Also, there are 2 that NEVER fail with
this message.
Any ideas? I do have a separate schedule to restart all the replication
jobs every hour just in case they are not running - but that is a band-aid.
Thanks,
Rob Kraft
general network error almost always means that the connection has been
broken - its a network failure problem not a problem with SQL Server or
replication.
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
"Rob Kraft" <robkraft@.msn.com> wrote in message
news:%23Q6xWBJ7FHA.2012@.TK2MSFTNGP14.phx.gbl...
>I have a merge replication environment with one central
> publisher/distributor and 35 clients. The merge uses continuous
> replication. At the moment, 31 of the 35 subscriptions have error this
> error:
> The process could not check existence of generation at the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error number: -2147201003)
> ----
> --
> General network error. Check your network documentation.
> (Source: SERVER002 (Data source); Error number: 11)
> ----
> --
> Occasionally some will start working again; and then later fail again.
> I'm
> sure that all permissions must be correct because they work 70 to 80 % of
> the time. I don't understand why so many fail so frequently though, and
> then why they start working again. Also, there are 2 that NEVER fail with
> this message.
> Any ideas? I do have a separate schedule to restart all the replication
> jobs every hour just in case they are not running - but that is a
> band-aid.
> Thanks,
> Rob Kraft
>
sql

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 with alternate synchoronization partner

Hello:
I have a merge replication and I defined a Publisher A as a primary
publisher and distributor, a Publisher B as an alternate synchronization
partner and distributor and a subscriber to the Publisher A.
We need to turn off the server which is Publisher A and set the Publiser B
as the alternate partner so we can replicate data between Publisher B and
the subscriber even if Publiser A if off.
I followed the following procedure:
-From the Pusbliser A I go to SQL Server agents, Jobs and then modify the
job that is PublisherA-SubscriberA. Modify the commad box to the PublisherB
and the parameter SyncToAlternate 1.
-Re-Start the merge agent
I get the error "The process could not drop one or more tables because the
tables are being used by other publications. The step failed"
Do I need to modify something else? What can I do? Because we need to turn
off the Publisher A and the replication still going between the other two
servers.
Thanks in advance
Jennyfer Barco
did you follow the steps outlined in
http://support.microsoft.com/default...roduct=sql2k#3
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jennyfer J Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
news:uwsCF6VkEHA.3756@.TK2MSFTNGP11.phx.gbl...
> Hello:
> I have a merge replication and I defined a Publisher A as a primary
> publisher and distributor, a Publisher B as an alternate synchronization
> partner and distributor and a subscriber to the Publisher A.
> We need to turn off the server which is Publisher A and set the Publiser B
> as the alternate partner so we can replicate data between Publisher B and
> the subscriber even if Publiser A if off.
> I followed the following procedure:
> -From the Pusbliser A I go to SQL Server agents, Jobs and then modify the
> job that is PublisherA-SubscriberA. Modify the commad box to the
PublisherB
> and the parameter SyncToAlternate 1.
> -Re-Start the merge agent
> I get the error "The process could not drop one or more tables because the
> tables are being used by other publications. The step failed"
> Do I need to modify something else? What can I do? Because we need to turn
> off the Publisher A and the replication still going between the other two
> servers.
> Thanks in advance
> Jennyfer Barco
>
|||Yes, I set up the suscriber following the directions and now the three
servers are replicating OK. Because we need to turn off the PubliserA I
followed the options under "Use SQL Server Enterprise Manager to Synchronize
with Alternate Synchronization Partner" but when I started synch I get the
error. I'm doing these steps from the Publisher A. Is it OK? Is there
anything else Ineed to do?
Thanks so much
Jennyfer
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e4N1Y4akEHA.3428@.TK2MSFTNGP11.phx.gbl...
> did you follow the steps outlined in
>
http://support.microsoft.com/default...roduct=sql2k#3[vbcol=seagreen]
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jennyfer J Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
> news:uwsCF6VkEHA.3756@.TK2MSFTNGP11.phx.gbl...
B[vbcol=seagreen]
and[vbcol=seagreen]
the[vbcol=seagreen]
> PublisherB
the[vbcol=seagreen]
turn[vbcol=seagreen]
two
>
|||Yes, I set up the suscriber following the directions and now the three
servers are replicating OK. Because we need to turn off the PubliserA I
followed the options under "Use SQL Server Enterprise Manager to Synchronize
with Alternate Synchronization Partner" but when I started synch I get the
error. I'm doing these steps from the Publisher A. Is it OK? Is there
anything else I need to do?
Thanks so much
Jennyfer
"Jennyfer J Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
news:esne3BdkEHA.3720@.TK2MSFTNGP12.phx.gbl...
> Yes, I set up the suscriber following the directions and now the three
> servers are replicating OK. Because we need to turn off the PubliserA I
> followed the options under "Use SQL Server Enterprise Manager to
Synchronize
> with Alternate Synchronization Partner" but when I started synch I get the
> error. I'm doing these steps from the Publisher A. Is it OK? Is there
> anything else Ineed to do?
> Thanks so much
> Jennyfer
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:e4N1Y4akEHA.3428@.TK2MSFTNGP11.phx.gbl...
>
http://support.microsoft.com/default...roduct=sql2k#3[vbcol=seagreen]
synchronization[vbcol=seagreen]
Publiser
> B
> and
> the
> the
> turn
> two
>

Merge Replication updating SP3 to SP4

Gurus,
I am planning to update SP3 to SP4 on a replicated server.
A- Please correct me if i wrong in order.
1- Apply SP4 on Publisher / Distributor (on single box)
2- All subscribers.
B- As per my knowledge there are no issues while applying SP4. Is there any
known issue while applying the sp4 has to be taken care of?
TIA
Regards
Javed Iqbal
Javed,
I agree with the order. I've had a search of this newsgroup (using Google
Groups) to check for sp4 and there are hardly any reported errors so far.
The main on e is
http://groups.google.com/group/micro...85 a5a37097d4
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Merge replication trouble

Hello
I have made a merge replication between two server W2k with sql2000 sp3. Those servers are connected via internet. In distributor (also publisher) I have setting up aliases for both servers. Have generated snapshot but when agent run I have this error: -2
147201019 and 14010 : "the subscription for pubblication [bla bla] is invalid".
I have searching in the net some solutions but I have noticed that in all cases it is depended by alias setting. But I have defined its ?
Some ideas ?
Have solved the puzzle.
In subscription I have noticed with sp_helpserver that the subscription server hav id = 1 so have do this:
sp_dropserver 'DIST_SERVER'
sp_dropserver 'SUB_SERVER'
sp_addserver 'SUB_SERVER', @.local = 'LOCAL'
where DIST_SERVER is my distribution, publisher server and SUB_SERVER is my subscription server.
Bests
|||Rafal,
OK, and the last 2 commands will require a restart of the services.
I'm not clear what the first line is for though (sp_dropserver 'DIST_SERVER').
Regards,
Paul Ibison

Merge Replication Pull Subscription Error

I have replication scenario using SQL SERVER 2000 as the Distributor/Publisher and multiple MSDE databases as the subscribers. When I set up the scenario to use push subscriptions the replication seems to work well. All changes flow correctly between al
l subscribers and the publisher.
When I try to run a pull subscription scenario the replication will fail. I think that the snapshot agent is failing because of some type of security problem. I get the error:
“SQL Server Agent could not access the replication agent. Use the DCOMCNFG utility to confirm that the SQL Server Agent Windows account has permissions to launch the replication agent. The step failed.”
The server is using windows authentication and has the sp3a on it. Again, when I run the replication using push subscribers it works. When I change it to pull subscribers, I get the error.
Any advice is greatly appreciated,
Phil
Are you using remove agent activation?
If so, you must use your Publisher, Susbcriber, or Distributor as the location of your remote agent.
If not, someone has messed with where your merge.exe program is running.
open up DCOMCnfg, locate Microsoft SQL Server Replication Merge Agent 8.0. click on properties Verify in the location tab, that the program runs locally, in the security tab, click on edit for launch permissions. Make sure the everyone group has special
access.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
-- Phil wrote: --
I have replication scenario using SQL SERVER 2000 as the Distributor/Publisher and multiple MSDE databases as the subscribers. When I set up the scenario to use push subscriptions the replication seems to work well. All changes flow correctly betwe
en all subscribers and the publisher.
When I try to run a pull subscription scenario the replication will fail. I think that the snapshot agent is failing because of some type of security problem. I get the error:
“SQL Server Agent could not access the replication agent. Use the DCOMCNFG utility to confirm that the SQL Server Agent Windows account has permissions to launch the replication agent. The step failed.”
The server is using windows authentication and has the sp3a on it. Again, when I run the replication using push subscribers it works. When I change it to pull subscribers, I get the error.
Any advice is greatly appreciated,
Phil
sql

Merge Replication problems

Greetings all...

I am trying to patch up a merge replication situation, and I have
1. configured Distributor & publisher
2. created a publication
3. created a subscription.

The subscription (on subscriber server) status=sucdeeded; Details=The initial snapshot for publication is not yet available.

When I go to snapshot agent (on publisher), it is saying: Status=Failed
Detail = The process could not bulk copy out of table 'contB22652175F9A4388BC64D1B43C8E8B30'.

Thanks!
Jester99This will sound crazy, but the first place I'd check is disk space availability, replication can use a lot of space, in particular when creating the initial snapshot.

How big is the database that the publication is based on ? how much of the total db will the publication contain ?

Merge Replication Problem with separate Publisher/Distributor

We are trying to setup merge replication using separate servers for the
publication and distribution. The servers are in the same domain. The same
domain account is used oon all servers involved with the replication. The
setup scripts perform the following task:
Distributor (Master db)
sp_AddDistributor
sp_MSupdateAgentType_default @.profile_id = 1
sp_MSupdateAgentType_default @.profile_id = 2
sp_MSupdateAgentType_default @.profile_id = 4
sp_MSupdateAgentType_default @.profile_id = 6
sp_MSupdateAgentType_default @.profile_id = 11
sp_AddDistributionDB
jobs: Agent History Cleanup
DistributionDB Cleanup
Sp_AddDistPublisher @.SecurityMode = 1
@.Trusted = N'False'
@.ThirdParty_flag = 0
do you have a remote distributor?
If not it sounds like your replication setup is not configured correctly.
Remove replication (follow the menu items to disable publishing) and
reinstall it.
"PaulW" <MSNewsGroup@.Digi-Sol.com> wrote in message
news:%23r2otLqMEHA.2064@.TK2MSFTNGP12.phx.gbl...
> We are trying to setup merge replication using separate servers for the
> publication and distribution. The servers are in the same domain. The same
> domain account is used oon all servers involved with the replication. The
> setup scripts perform the following task:
>
> Distributor (Master db)
>
> sp_AddDistributor
>
> sp_MSupdateAgentType_default @.profile_id = 1
> sp_MSupdateAgentType_default @.profile_id = 2
> sp_MSupdateAgentType_default @.profile_id = 4
> sp_MSupdateAgentType_default @.profile_id = 6
> sp_MSupdateAgentType_default @.profile_id = 11
>
> sp_AddDistributionDB
>
> jobs: Agent History Cleanup
> DistributionDB Cleanup
>
> Sp_AddDistPublisher @.SecurityMode = 1
> @.Trusted =
N'False'
> @.ThirdParty_flag = 0
> .
>
> Jobs: Expired Subscription Cleanup
> Reinitialize subscription having data validation failures
> Replication agent Checkup
> SnapShot
>
>
> Publisher (Master db)
>
> Jobs: Reinitialize subscription having data validation failures
> Replication agent Checkup
>
> sp_AddSubscriber
>
> Server: Msg 14071 Procedure sp_AddSubscriber, line 129 Could not find the
> Distributor or the distribution database for the local server. The
> Distributor may not be installed, or the local server may not be
configured
> as a Publisher at the Distributor
>
>
> E.M. on the distributor list the publisher with out any publications. Line
> 129 of sp_AddSubscriber is sp_HelpDistributor which according to the help
is
> to run only on the distributor, explaining the error. Sp_AddSubscriber is
> supposed to be run on the publisher.
>
> What am I missing?
>
>
> tia
> Paul
>
>
|||We are using a remote distributor. We did not set a password in
sp_adddistributor. In sp_adddistpublisher we tried both trusted and not
trusted. The authentication on all servers is set to Windows only. I noticed
that the distributor_admin account is a SQL Server account. Can this be the
problem? If so, is there a way to get this to run using Windows only?
Paul
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:ujpd7bxMEHA.2484@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> do you have a remote distributor?
> If not it sounds like your replication setup is not configured correctly.
> Remove replication (follow the menu items to disable publishing) and
> reinstall it.
> "PaulW" <MSNewsGroup@.Digi-Sol.com> wrote in message
> news:%23r2otLqMEHA.2064@.TK2MSFTNGP12.phx.gbl...
same[vbcol=seagreen]
The[vbcol=seagreen]
> N'False'
the[vbcol=seagreen]
> configured
Line[vbcol=seagreen]
help[vbcol=seagreen]
> is
is
>
|||We tried to setup merge replication using the remote distributor through
E.M. and it worked. Then we used the option to generate SQL scripts. When we
ran the scripts, errors were generated. One of the errors was, in one job
only; the server name was used for the server name and the distributor
database name. They were not the same name.
We did find out that the distributor must be using SQL and Windows
authentication. That option along did not get our scripts working. There
must be something subtle that I am missing.
Paul
"PaulW" <MSNewsGroup@.Digi-Sol.com> wrote in message
news:#7OrH#3MEHA.1644@.TK2MSFTNGP09.phx.gbl...
> We are using a remote distributor. We did not set a password in
> sp_adddistributor. In sp_adddistpublisher we tried both trusted and not
> trusted. The authentication on all servers is set to Windows only. I
noticed
> that the distributor_admin account is a SQL Server account. Can this be
the[vbcol=seagreen]
> problem? If so, is there a way to get this to run using Windows only?
>
> Paul
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:ujpd7bxMEHA.2484@.TK2MSFTNGP09.phx.gbl...
correctly.[vbcol=seagreen]
the
> same
> The
> the
> Line
> help
> is
>
|||I believe this is because you don't have the addDistributor S.P. being run
on the publisher as well as the distributor. ;)

Merge replication problem

I have one corporate server that acts as both publisher and distributor.
Remote locations all have SQL server loaded and act as subscribers. This
setup has worked great until yesterday. Somehow, and it is still under
investigation, the corporate server "lost" all subscriptions and became
disconnected from the remote locations.
Each location is on a 5 minute schedule for the merge agent to run.
After recreating all the subscriptions and "pushing" them down to the remote
locations, there has been information lost during the down time. The
snapshot agent had to be run in order to recreate the subscriptions. I am
trying to figure out how I could have reconfigured the setup so that when
the subscription was made all the data in the remote locations would have
been preserved and "Merged" with the data from the server.
Thank you in advance for you input.
WB
Should this situation happen again I suggest:
1. Prevent further updates on remote stations until replication is re-setup
OR choose a time for the resync that least interferes with operations - the
longer you leave it the worse your problem becomes
2. Remove publication(s) and subscriptions
3. Use a tool like Red Gates "Data Compare" to see what data the publisher
is missing - it will generate the sql inserts for you, this sql may need to
be manually tweaked
4. Apply update scripts
5. Recreate publication(s) and subscriptions
6. Find the person who caused the problem and apply thumbscrews
Jim.
"WB" wrote:

> I have one corporate server that acts as both publisher and distributor.
> Remote locations all have SQL server loaded and act as subscribers. This
> setup has worked great until yesterday. Somehow, and it is still under
> investigation, the corporate server "lost" all subscriptions and became
> disconnected from the remote locations.
> Each location is on a 5 minute schedule for the merge agent to run.
> After recreating all the subscriptions and "pushing" them down to the remote
> locations, there has been information lost during the down time. The
> snapshot agent had to be run in order to recreate the subscriptions. I am
> trying to figure out how I could have reconfigured the setup so that when
> the subscription was made all the data in the remote locations would have
> been preserved and "Merged" with the data from the server.
> Thank you in advance for you input.
> WB
>
>
|||I don't know how successful I will be at applying the thumbscrews to myself,
as it appears to have happened on my watch. It appears that while trying to
create a new remote server (from the remote location) and then send down the
snapshot and merged replication data, that the SQL server at the main office
removed the subscriptions of all the remote locations. Not sure how the
subscriptions were removed or why SQL thought it needed to do that, but I
may never know....
I will definitely look into the data compare tool; that will probably come
in handy in the future.
"Jim Breffni" <JimBreffni@.discussions.microsoft.com> wrote in message
news:C3E8DA76-F717-4353-8E0B-FACDA058F3DB@.microsoft.com...
> Should this situation happen again I suggest:
> 1. Prevent further updates on remote stations until replication is
re-setup
> OR choose a time for the resync that least interferes with operations -
the
> longer you leave it the worse your problem becomes
> 2. Remove publication(s) and subscriptions
> 3. Use a tool like Red Gates "Data Compare" to see what data the
publisher
> is missing - it will generate the sql inserts for you, this sql may need
to[vbcol=seagreen]
> be manually tweaked
> 4. Apply update scripts
> 5. Recreate publication(s) and subscriptions
> 6. Find the person who caused the problem and apply thumbscrews
>
> Jim.
>
> "WB" wrote:
This[vbcol=seagreen]
remote[vbcol=seagreen]
am[vbcol=seagreen]
when[vbcol=seagreen]
have[vbcol=seagreen]

Merge Replication Performance Issues/Trace Files

We have a merge replication configuration with the distributor and subscriber
on one server and the publisher on another. The performance of the merge
slows down more and more as runs. The bandwidth between servers has already
been ruled out because there they run on a Sonet ring and T3 line between
them. We put SQL Profiler trace on the subscriber end of the merge process
using textdata and duration to try to pin point it down to the source of the
problem. However, the Textdata column has unreadable data, for instance
exec([sp_upd_4FAB988B754745CDECFA93F09EC34073]
'8D8EF6A0-8EDA-4C71-934F-0FAE3E79AFFE',
0x000000000000000000000000008007000000000000000000 0000000000000000, 3, 0x00,
296, 0xECFA93F002000000FF,
0xECFA93F001000000ECFA93F001000000ECFA93F001000000 ECFA93F00100000
Does anyone know if there is any way to translate this into the actual query
executed? Otherwise, I don't see how this helps. I got the trace setup
from a Microsoft web site.
This update proc is being run in binary format.
run this query in your subscription database
select name from sysmergearticles where update_proc
='sp_upd_4FAB988B754745CDECFA93F09EC34073'
to determine which table it is updating.
Basically here are the parameters
Rowguid=0x0000000000000000000000000080070000000000 000000000000000000000000,
metadata_type=3,
lineage_old=0x00,
generation=296,
lineage_new=0xECFA93F002000000FF,
colv= 0xECFA93F001000000ECFA93F001000000ECFA93F001000000 ECFA93F00100000
Then there should be a bunch of parameters whose values you have not
supplied me with
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"SandiDBA" <SandiDBA@.discussions.microsoft.com> wrote in message
news:4946584E-0713-4190-BC0A-A35998E63CDA@.microsoft.com...
> We have a merge replication configuration with the distributor and
subscriber
> on one server and the publisher on another. The performance of the
merge
> slows down more and more as runs. The bandwidth between servers has
already
> been ruled out because there they run on a Sonet ring and T3 line between
> them. We put SQL Profiler trace on the subscriber end of the merge
process
> using textdata and duration to try to pin point it down to the source of
the
> problem. However, the Textdata column has unreadable data, for instance
> exec([sp_upd_4FAB988B754745CDECFA93F09EC34073]
> '8D8EF6A0-8EDA-4C71-934F-0FAE3E79AFFE',
> 0x000000000000000000000000008007000000000000000000 0000000000000000, 3,
0x00,
> 296, 0xECFA93F002000000FF,
> 0xECFA93F001000000ECFA93F001000000ECFA93F001000000 ECFA93F00100000
> Does anyone know if there is any way to translate this into the actual
query
> executed? Otherwise, I don't see how this helps. I got the trace
setup
> from a Microsoft web site.
|||Thanks so much, that helps. Do you also know where can I translate the
index being used for the update?
"Hilary Cotter" wrote:

> This update proc is being run in binary format.
> run this query in your subscription database
> select name from sysmergearticles where update_proc
> ='sp_upd_4FAB988B754745CDECFA93F09EC34073'
> to determine which table it is updating.
> Basically here are the parameters
> Rowguid=0x0000000000000000000000000080070000000000 000000000000000000000000,
> metadata_type=3,
> lineage_old=0x00,
> generation=296,
> lineage_new=0xECFA93F002000000FF,
> colv= 0xECFA93F001000000ECFA93F001000000ECFA93F001000000 ECFA93F00100000
> Then there should be a bunch of parameters whose values you have not
> supplied me with
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "SandiDBA" <SandiDBA@.discussions.microsoft.com> wrote in message
> news:4946584E-0713-4190-BC0A-A35998E63CDA@.microsoft.com...
> subscriber
> merge
> already
> process
> the
> 0x00,
> query
> setup
>
>
|||What index?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"SandiDBA" <SandiDBA@.discussions.microsoft.com> wrote in message
news:58CF081D-5141-4F87-B9C9-54ACD0D514AE@.microsoft.com...[vbcol=seagreen]
> Thanks so much, that helps. Do you also know where can I translate the
> index being used for the update?
> "Hilary Cotter" wrote:
Rowguid=0x0000000000000000000000000080070000000000 000000000000000000000000,[vbcol=seagreen]
between[vbcol=seagreen]
of[vbcol=seagreen]
instance[vbcol=seagreen]
|||The update statement must have a where clause in it. I would like to know
what columns the where clause use to find the row to update. Then from
there, determine if an index is being used for optimization.
"Hilary Cotter" wrote:

> This update proc is being run in binary format.
> run this query in your subscription database
> select name from sysmergearticles where update_proc
> ='sp_upd_4FAB988B754745CDECFA93F09EC34073'
> to determine which table it is updating.
> Basically here are the parameters
> Rowguid=0x0000000000000000000000000080070000000000 000000000000000000000000,
> metadata_type=3,
> lineage_old=0x00,
> generation=296,
> lineage_new=0xECFA93F002000000FF,
> colv= 0xECFA93F001000000ECFA93F001000000ECFA93F001000000 ECFA93F00100000
> Then there should be a bunch of parameters whose values you have not
> supplied me with
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "SandiDBA" <SandiDBA@.discussions.microsoft.com> wrote in message
> news:4946584E-0713-4190-BC0A-A35998E63CDA@.microsoft.com...
> subscriber
> merge
> already
> process
> the
> 0x00,
> query
> setup
>
>
|||use the index tuning wizard to help you determine this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"SandiDBA" <SandiDBA@.discussions.microsoft.com> wrote in message
news:732D8E62-ECA5-4D75-B793-6E4F6F0544D6@.microsoft.com...
> The update statement must have a where clause in it. I would like to
know[vbcol=seagreen]
> what columns the where clause use to find the row to update. Then from
> there, determine if an index is being used for optimization.
> "Hilary Cotter" wrote:
Rowguid=0x0000000000000000000000000080070000000000 000000000000000000000000,[vbcol=seagreen]
between[vbcol=seagreen]
of[vbcol=seagreen]
instance[vbcol=seagreen]

Merge Replication Overwritting Data

Hi,
I have a problem with merge replication overwriting data without any
reason. Here is my setup:
Publisher/Distributor runs on Windows 2003 Server
Subscribers running on Windows 2000/XP using SQL desktop engine.
Subscribers update/modify data via an application and sync back to the
publisher.
Users also log straight into the server via an application to update/
modify data.
Data is been overwritten by an older version of that record. To give
you an example of the process a user enters in a record it then gets
reviewed by a manger who approves a "status" change, the data is then
entered into a secondary system then the record is closed/completed.
What is happening is that record for some reason is reverting back to
a previous version with an old status and is coming up on managers
reports again, causing work flow issues.
This is happening inconsistently and very rarely and we cant seems to
reproduce the scenario. Can anyone give me incite into what is
happening here why replication is reverting data back.
Regards,
Ben
Are you seeing any conflicts?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Setting the flag is an option. If this is the issue, I'd also like to know
exactly why this occurs though - ie why can't the change be applied at the
replica. Are the constraints different perhaps? Is the change being applied
to the PK etc.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||On Mar 7, 8:51 pm, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> Setting the flag is an option. If this is the issue, I'd also like to know
> exactly why this occurs though - ie why can't the change be applied at the
> replica. Are the constraints different perhaps? Is the change being applied
> to the PK etc.
> Cheers,
> Paul Ibison SQL Server MVP,www.replicationanswers.com
That is a good question, my biggest problem is trying to reproduce the
problem to isolate where it is occurring. Unfortunately I haven't been
able to do this. The only thing I know thus far is it happens
intermittently and it's affecting records at random, both of which are
no help. I do know however that this problem only began when
replication started.
Would any of the following 2 scenarios be related to this problem:
1. A subscriber (Salesperson) sync's their data but fails in the
attempt,
the user then continues to modify data on their local machine and then
sync's
again only this time successfully, causing previous changes to be
overwritten.
2. A subscriber (Salesperson) sync's their data but fails in the
attempt, a
snapshot is taken of the publisher's data then the user sync's again
only
this time successfully, causing previous changes to be overwritten.
I'm not sure what else to check as I have nothing else to go on, any
other suggestions?

Merge Replication over internet Problem: Couldn't propagate schema to the subscriber.

Hello All,
I am implementing Pull merge replication over internet, I have a sql
server which I have set as Publishe/Distributor and MSDE which I have
set a subscriber. I have a sample Database FTP_REPL which I have
published. whenever I try to run merge Agent it succssfully connects
to the publisher, Distributor,but it gives error "The schema script
<ScriptName> could not be propagated to the subscriber".
Plz anyone help me to resolve this problem.
Locate your agent, right click on it, select agent properties, and ensure
the job owner is sa. Then restart your agent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501100407.d4c3f56@.posting.google.co m...
> Hello All,
> I am implementing Pull merge replication over internet, I have a sql
> server which I have set as Publishe/Distributor and MSDE which I have
> set a subscriber. I have a sample Database FTP_REPL which I have
> published. whenever I try to run merge Agent it succssfully connects
> to the publisher, Distributor,but it gives error "The schema script
> <ScriptName> could not be propagated to the subscriber".
> Plz anyone help me to resolve this problem.

Merge replication over internet

Good morning,
I am attempting to set up merge replication between a SQL Server on SBS2003
box (publisher and distributor) and a SQL Server 2000 box (subscriber) in a
different state (hosted, connect via IP addresses).
I can push the publication to the subscriber, but the synch process fails
with error 14010 (I think..not in front of right now).
This is my first attempt at replication...any help is appreciated
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
Kevin,
are you using an IP address - it'll need to be an alias instead. Have a look
at this article to see if you have missed anything out:
http://support.microsoft.com/?id=321822
HTH,
Paul Ibison
|||Kevin,
are you using an IP address - it'll need to be an alias instead. Have a look
at this article to see if you have missed anything out:
http://support.microsoft.com/?id=321822
HTH,
Paul Ibison
|||My bad...I have set up the alias through the Client Network Utility on the
Publisher, using the correct name of the server as the alias name. Did same
at the Subscriber to connect to the Publisher...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> Kevin,
> are you using an IP address - it'll need to be an alias instead. Have a
look
> at this article to see if you have missed anything out:
> http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison
>
|||My bad...I have set up the alias through the Client Network Utility on the
Publisher, using the correct name of the server as the alias name. Did same
at the Subscriber to connect to the Publisher...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> Kevin,
> are you using an IP address - it'll need to be an alias instead. Have a
look
> at this article to see if you have missed anything out:
> http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison
>
|||make sure you download the snapshot using FTP and use anonymous pull
subscribers.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
> My bad...I have set up the alias through the Client Network Utility on the
> Publisher, using the correct name of the server as the alias name. Did
same
> at the Subscriber to connect to the Publisher...
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> look
>
|||make sure you download the snapshot using FTP and use anonymous pull
subscribers.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
> My bad...I have set up the alias through the Client Network Utility on the
> Publisher, using the correct name of the server as the alias name. Did
same
> at the Subscriber to connect to the Publisher...
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> look
>
|||OK...so a push to the subscriber does not work? Is that only for
local/Lan/trusted setups?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> make sure you download the snapshot using FTP and use anonymous pull
> subscribers.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
> news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
> same
a
>
|||OK...so a push to the subscriber does not work? Is that only for
local/Lan/trusted setups?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> make sure you download the snapshot using FTP and use anonymous pull
> subscribers.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
> news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
> same
a
>
|||Not really. You can push or pull within a LAN, locally, or within a trusted
network or across a WAN, Internet, etc.
The decision to use push or pull depends on many factors
1) pull performance is better, but you have no central point of
administration
2) It is a security risk to open the ports necessary to push over the
internet.
3) You can't do a push using FTP.
4) pull is better when your subscribers are occasionally connected, push is
better when they are always connected.
In general when you hear the word internet - think pull.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:OEs0JSgXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> OK...so a push to the subscriber does not work? Is that only for
> local/Lan/trusted setups?
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...
> the
Did[vbcol=seagreen]
DBAs.[vbcol=seagreen]
Have
> a
>

Merge Replication not merging updates made to subscriber

Hope someone can help with this. I've implemented merge replication and when
I make an update to the server that acts as the distributor the update is
reflected on the subscribers. However when I make a change on the subscriber
I cannot see it on the other subscribers or on the distributor. Any help
regarding this would be appreciated.
Thank you,
Abdul Rauf
Abdul,
how are you making the change on the subscriber? If it is a bulk insert
without firing the triggers, it won't replicate to the publisher. In some
rare other cases this also happens (eg when the filter is set to 1=2 and you
are adding records onto the subscriber. If there is no coresponding record
in MSmerge_contents try using sp_addtabletocontents to include the rows then
resynchronise. Alternatively you can use sp_mergedummyupdate for a single
row.
HTH,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]
|||Paul, I'm new to replication so I will do more research on what you have
below. I'm testing this scenario so I'm just going into the enterprise
manager of the subscriber database and updating a row in the Pubs database.
Updating a row in the Distributor database works but not in the Subscriber
through enterprise manager.
"Paul Ibison" wrote:

> Abdul,
> how are you making the change on the subscriber? If it is a bulk insert
> without firing the triggers, it won't replicate to the publisher. In some
> rare other cases this also happens (eg when the filter is set to 1=2 and you
> are adding records onto the subscriber. If there is no coresponding record
> in MSmerge_contents try using sp_addtabletocontents to include the rows then
> resynchronise. Alternatively you can use sp_mergedummyupdate for a single
> row.
> HTH,
> Paul Ibison (SQL Server MVP)
>
>

Merge Replication Issue

Hello, I have a merge replication problem. I have one publisher/distributor
and roughly about 40 subcribers to a replicated database of about 10 gig
in size. I'm using SQL 2000 and have Sql sp3 on all my machines. I
wanted to do some maintenance on my publsher and so I changed in the
subscriber's job schedule the "Start Date" to be the next day. I don't know
why but this caused the replications between the subscribers and the
publishers to fail. The error message I received stated the following,
"The process could not check the existence of the generation at the 'Publisher'".
This message would appear after a 10 minute delay. So, I decided to
change the "Start Date" back to the original date and just synch one of
my subscriber. It started synching alright, but it seems to be going
through several generations. It has taken the subscriber over six hours
to synch and it has it not finished. I need to know if this is normal
and how can I shorten the process. I thought it would just synch back
with the publishers and upload the 1-day changes and not go through all
the generations.

Thanking you in advance for any assistance with this issueYou probably need to check this and see what settings need to be affected when attempting to suspend merge agents:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replmon_9pwh.asp|||First thank you for the reply. The article explained the problem I was going through.

We fortunately found the root of our problem. It was not so much the validations that were happening at the subscriber but an individual subscriber that had a extremely large msgenhistory table that it wanted to compare with the distributor. This particular subscriber was a new subscriber and should not had needed to be trying to validate it's data since it had just received a new snapshot. So, we dumped it's gehist and that helped. After this we started to first start to synch our subscribers and as soon as they started validating the articles, we stopped the synchronization procees. We then immediately started the synch process again and everything was fine. We had to do this for every one of the 40 subscribers.

Hope our experience helps others.

merge replication generation problem

Merge Replication Web Sync - Pull subscriptions
publisher and distributor: SQL Server 2005 X64 build 2221
clients are SQL Express builld 2047
We have 3 of our clients that received the following error at the end
of a merge.
SessionStatistics:
============================
UploadInserts:4
DownloadInserts:1748
DownloadUpdates:67
DownloadDeletes:15
SchemaChanges:1
ChangeDeliveryTime:64sec
SchemaChangeandBulkInsertTime:26sec
DeliveryRate:28.66rows/sec
TotalSessionDuration:368sec
================================================== ===========
2007-04-1823:50:38.669 The merge process was unable to create a new
generation at the'Subscriber'.Troubleshoot by restarting the
synchronization with verbose history logging and specify an output
file to which to write.
Since that time, they recieve the same error message at the beginning
of every merge attempt and fail immediately:
2007-04-1900:28:06.672 The merge process was unable to create a new
generation at the 'Subscriber'...
We have marked for re-init, but they get the above message prior and
fail, before ever doing a re-init.
Has anyone seen this? Have any suggestions what to look for/at?
TIA,
jg
Hi,
I am having the same problems with Merge Replication, did you find a solution?
Cheers
Pieter
"johng@.garrisonenterprises.net" wrote:

> Merge Replication Web Sync - Pull subscriptions
> publisher and distributor: SQL Server 2005 X64 build 2221
> clients are SQL Express builld 2047
> We have 3 of our clients that received the following error at the end
> of a merge.
> SessionStatistics:
> ============================
> UploadInserts:4
> DownloadInserts:1748
> DownloadUpdates:67
> DownloadDeletes:15
> SchemaChanges:1
> ChangeDeliveryTime:64sec
> SchemaChangeandBulkInsertTime:26sec
> DeliveryRate:28.66rows/sec
> TotalSessionDuration:368sec
> ================================================== ===========
> 2007-04-1823:50:38.669 The merge process was unable to create a new
> generation at the'Subscriber'.Troubleshoot by restarting the
> synchronization with verbose history logging and specify an output
> file to which to write.
>
> Since that time, they recieve the same error message at the beginning
> of every merge attempt and fail immediately:
> 2007-04-1900:28:06.672 The merge process was unable to create a new
> generation at the 'Subscriber'...
>
> We have marked for re-init, but they get the above message prior and
> fail, before ever doing a re-init.
> Has anyone seen this? Have any suggestions what to look for/at?
> TIA,
> jg
>

Merge replication failure

Hello,
I have an SQL2000 server, which acts as the distributor and as the
publisher. The clients are Pocket PC's, using SQL Server CE. I have the
latest SP for both. The replication is a merge replication, with a lot of
join filters, more than 100 articles (only tables, no views or procedures
included). The average size of the database on the clients is about ~7MB.
Sometimes, following a massive delete on several tables (delete from table,
than insert into table select from sthing), I have got the following error
message during replication:
1. "a call to the sql server reconciler has failed"
2. "failed to enumerate changes"
3. "select permission denied on column <pk> of object MS_<long-long guid>"
The error occurs in the stored procedure sp_MSsetupbelongs.
Actually, the message is right, the user has no rights to the referred
table. But. This is a generated table, created by the replication itself (I
think this is the table used for deletion). After I've added the rights, the
error disapperared. Reinitialize also helps.
Do I have to do this all for the tables in the publication? I could not do
this, because of the generated table names.
Or this is a bug?
Thanks for replies,
Tamas Beri
Funny, but I can't find anything better solution than this one:
select
'grant select on '+sysobjects.name+' to sales;'
from
sysobjects
where
name like 'MS_bi%_v_%'
order by
sysobjects.name;
After you ran this generated script, the whole problem described down there
disappears.
Do You have any information about the Service Pack 4? I have a lot of
problems with sql server ce and merge replication.
Regards,
Tamas Beri
"Beri Tamas" <gfoyle@.freemail.hu> az albbiakat rta a kvetkezo zenetben
news:uYP%23YL89EHA.2984@.TK2MSFTNGP09.phx.gbl...
> Hello,
> I have an SQL2000 server, which acts as the distributor and as the
> publisher. The clients are Pocket PC's, using SQL Server CE. I have the
> latest SP for both. The replication is a merge replication, with a lot of
> join filters, more than 100 articles (only tables, no views or procedures
> included). The average size of the database on the clients is about ~7MB.
> Sometimes, following a massive delete on several tables (delete from
table,
> than insert into table select from sthing), I have got the following error
> message during replication:
> 1. "a call to the sql server reconciler has failed"
> 2. "failed to enumerate changes"
> 3. "select permission denied on column <pk> of object MS_<long-long guid>"
> The error occurs in the stored procedure sp_MSsetupbelongs.
> Actually, the message is right, the user has no rights to the referred
> table. But. This is a generated table, created by the replication itself
(I
> think this is the table used for deletion). After I've added the rights,
the
> error disapperared. Reinitialize also helps.
> Do I have to do this all for the tables in the publication? I could not do
> this, because of the generated table names.
> Or this is a bug?
> Thanks for replies,
> Tamas Beri
|||Hi Beri,
Replication shouldn't require you to issue the explicit select on this
particular object. Can you please provide some more info so that we can try
to create the repro in our test environment?
1. What kind of permission have you provided to publisher and distributor
login?
2. What's the type of object 'MS_bi%_v_%' - view, SP, etc?
3. Can you please provide the content of following tables - sysmergearticles
& sysmergepublications?
4. In case you are okay - can you post your scripts which you used to setup
your replication?
thanks - Deepak
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Beri Tamas" <gfoyle@.freemail.hu> wrote in message
news:Ocybvt%239EHA.2984@.TK2MSFTNGP09.phx.gbl...
> Funny, but I can't find anything better solution than this one:
> select
> 'grant select on '+sysobjects.name+' to sales;'
> from
> sysobjects
> where
> name like 'MS_bi%_v_%'
> order by
> sysobjects.name;
> After you ran this generated script, the whole problem described down
there[vbcol=seagreen]
> disappears.
> Do You have any information about the Service Pack 4? I have a lot of
> problems with sql server ce and merge replication.
> Regards,
> Tamas Beri
> "Beri Tamas" <gfoyle@.freemail.hu> az albbiakat rta a kvetkezo zenetben
> news:uYP%23YL89EHA.2984@.TK2MSFTNGP09.phx.gbl...
of[vbcol=seagreen]
procedures[vbcol=seagreen]
~7MB.[vbcol=seagreen]
> table,
error[vbcol=seagreen]
guid>"[vbcol=seagreen]
> (I
> the
do
>
|||Same error here, but I run the script and still get it.
Any more on this one?

Merge Replication fails on deadlocked

I have a merge replication environment with one host is
publisher/distributor and one subscriber. The merge uses continuous
replication. My MSSQL's are 2000SP4.
The process could not enumerate changes at the 'Publisher'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
Transaction (Process ID 70) was deadlocked on lock resources with another
process and has been chosen as the deadlock victim. Rerun the transaction.
(Source: SERVA_SQL (Data source); Error number: 1205)
Thanks for any help,
Darek
These errors are normally transitory. Try restarting your merge agent.
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
"Dlib" <dlib@.pap.pl> wrote in message
news:dltakk$hlr$1@.nemesis.news.tpi.pl...
>I have a merge replication environment with one host is
>publisher/distributor and one subscriber. The merge uses continuous
>replication. My MSSQL's are 2000SP4.
>
> The process could not enumerate changes at the 'Publisher'.
> (Source: Merge Replication Provider (Agent); Error number: -2147200999)
> ----
> Transaction (Process ID 70) was deadlocked on lock resources with another
> process and has been chosen as the deadlock victim. Rerun the transaction.
> (Source: SERVA_SQL (Data source); Error number: 1205)
> ----
> Thanks for any help,
> Darek
>