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 stopping

Hi All,
I have selected merge replication because both servers are constantly
updating information. We have continuous merge replication (push) and
everything works pretty good.
The problem is in some occassions the job stops saying that it can not
enumerate the changes on the subscriber, if I restart it works fine. This is
causing more than a headache because we always have to be watching if
replication is working. I try to change the job to restart when it fails but
it doesn't work.
I have one publisher with the distributor on the same machine pushing the
continuous merge to one subscriber.
Can this happen because the subscriber is busy and the job can connect? Have
anyone seen this happening?
Thanks a lot
Yes, it is typically a transitory error. Many dba's run their merge agents
in infinite loops by having step 3 looping back to step 1.
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
"Salvador" <Salvador@.discussions.microsoft.com> wrote in message
news:723F7F3D-6BE0-4205-B79F-01CA227E7EF7@.microsoft.com...
> Hi All,
> I have selected merge replication because both servers are constantly
> updating information. We have continuous merge replication (push) and
> everything works pretty good.
> The problem is in some occassions the job stops saying that it can not
> enumerate the changes on the subscriber, if I restart it works fine. This
is
> causing more than a headache because we always have to be watching if
> replication is working. I try to change the job to restart when it fails
but
> it doesn't work.
> I have one publisher with the distributor on the same machine pushing the
> continuous merge to one subscriber.
> Can this happen because the subscriber is busy and the job can connect?
Have
> anyone seen this happening?
> Thanks a lot
|||We have the job running every minute and it seems to work fine. I have
noticed that the retry doesn't work like one would think it should.
If you go to Merge Agent History, Session Details, Error Details, you should
get more information on why it can't continue. We get a lot of deadlocks
causing the agent to fail, but when it picks back up a minute later it
usually works fine.
Dylan Peters
"Hilary Cotter" wrote:

> Yes, it is typically a transitory error. Many dba's run their merge agents
> in infinite loops by having step 3 looping back to step 1.
> --
> 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
> "Salvador" <Salvador@.discussions.microsoft.com> wrote in message
> news:723F7F3D-6BE0-4205-B79F-01CA227E7EF7@.microsoft.com...
> is
> but
> Have
>
>
sql

Merge Replication Status

I'm using sp_replmonitorhelpmergesession to determine the status of
multiple push subscriptions.
When I set the Merge Agent to Slow Link, I get a status of 4 and the
message "No Data needed to be Merged" when there are no changes.
I'd like to get it to return the Status 4 when it's idle, but I want
to increase the polling interval from 60 to 180.
So I copy the Agent Profile "Slow Link" and alter the polling interval
and validation intervals only.
When I copy the slow Link Profile and use the copy, I get a Status of
3 and the message "Waiting xxx second(s) before polling for further
changes."
Where/how are these controlled?
pollinginterval
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
"Brian Bunin" <BBunin@.SBCGlobal.net> wrote in message
news:1176335136.270222.63650@.n59g2000hsh.googlegro ups.com...
> I'm using sp_replmonitorhelpmergesession to determine the status of
> multiple push subscriptions.
>
> When I set the Merge Agent to Slow Link, I get a status of 4 and the
> message "No Data needed to be Merged" when there are no changes.
> I'd like to get it to return the Status 4 when it's idle, but I want
> to increase the polling interval from 60 to 180.
> So I copy the Agent Profile "Slow Link" and alter the polling interval
> and validation intervals only.
> When I copy the slow Link Profile and use the copy, I get a Status of
> 3 and the message "Waiting xxx second(s) before polling for further
> changes."
> Where/how are these controlled?
>
|||On Apr 12, 8:48 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> pollinginterval
> --
> Hilary Cotter
>
Yes, but why does changing that alter the behavior of the Status and
messages?

Merge Replication Recovery

Hi,
Had merge replication set up between two servers. with push subscription.
For various reasons the replication stopped running for a few days and now
we have different data at both sites.
Does anybody have a series of steps to get this back up and running other
than the following.
1. Create new db at subscriber.
2. Publish to this new sunscriber from existing publication.
3. Piece in missing data from offline subscriber.(data inserted at
subscriber since merge stopped).
Any other suggestions?
You should be able to synchronize to get things back up, provided you
haven't exceeded the retention period - the publication retention value is
used to determine when subscriptions that have not synchronized within the
retention period should expire and it is set to 14 days by default. If this
is not an option, then I'd use Redgate'd DataCompare to generate the change
script to be applied at the publisher then reinitialize the subscriber.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||run a validation to determine how out of sync you are. Run the merge agent
until it completes. Chances are you will be in sync after it runs.
The problem with trying to enter the data manually or through applets like
DataCompare is that when you enter this data on the subscriber to try to
sync it
it will raise all sorts of conflicts when you run the merge agent, and
they will be kicked back and you will be returned the state you where in
before.
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
|||Fair point, but I was recommending using the RedGate change script at the
publisher and subsequently reinitializing the subscriber. It's not very
sophisticated and the data size might make it unattractive, but it should
work.
Rgds,
Paul
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:opso0n92xurj9kur@.hcottter-lap.ap.org...
> run a validation to determine how out of sync you are. Run the merge agent
> until it completes. Chances are you will be in sync after it runs.
> The problem with trying to enter the data manually or through applets like
> DataCompare is that when you enter this data on the subscriber to try to
> sync it
> it will raise all sorts of conflicts when you run the merge agent, and
> they will be kicked back and you will be returned the state you where in
> before.
> --
> 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
|||Thanks for all the suggestions guys. The replicationanswers website is very
informative. Just a quick question Hilary you mentioned run a validation,
what exactly did you mean by that? write my own routine.
Just for info we did get the snapshot reapplied to the subscription but the
data changes at the subscriber did not get applied, despite being well
within the retention period so we had to maunally rebuild the data.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eh4LsOdPFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Fair point, but I was recommending using the RedGate change script at the
> publisher and subsequently reinitializing the subscriber. It's not very
> sophisticated and the data size might make it unattractive, but it should
> work.
> Rgds,
> Paul
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:opso0n92xurj9kur@.hcottter-lap.ap.org...
>
|||if your subscription is a global subscription you should be able to
synchronize!
MB wrote:
> Thanks for all the suggestions guys. The replicationanswers website
is very
> informative. Just a quick question Hilary you mentioned run a
validation,
> what exactly did you mean by that? write my own routine.
> Just for info we did get the snapshot reapplied to the subscription
but the
> data changes at the subscriber did not get applied, despite being
well[vbcol=seagreen]
> within the retention period so we had to maunally rebuild the data.
>
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:eh4LsOdPFHA.2748@.TK2MSFTNGP09.phx.gbl...
at the[vbcol=seagreen]
very[vbcol=seagreen]
should[vbcol=seagreen]
merge[vbcol=seagreen]
runs.[vbcol=seagreen]
applets[vbcol=seagreen]
subscriber to[vbcol=seagreen]
and[vbcol=seagreen]
where in[vbcol=seagreen]

Merge Replication Push using IP address fails? WTF?

I have a Merge publication that has multiple subscribers. They are all SQL Express, so it's all Push Subscriptions.

When I try to add a subscriber by it's IP address, the snapshot gets delivered. Schema created, data loaded, but I see the following error in Replication Monitor:

The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

Cannot find the object 'MSmerge_ctsv_E0801EECCA824BB29D48D36D64D2BAEA', because it does not exist or you do not have permission. (Source: MSSQLServer, Error number: 15151)

When I change the IP address in the script to the name of the machine it works perfectly. The ONLY thing I changed in the script was the IP address to the name.

The reason for this is that I have several client machines that will have connectivity, but NO name resolution back at the Server.

Please, Please, Please help!

Sample follows:

Code Snippet

execsp_addmergesubscription

@.publication = N'TestPub',

@.subscriber = N'10.126.22.30',

@.subscriber_db = N'dbTest',

@.subscription_type = N'Push',

@.sync_type = N'Automatic',

@.subscriber_type = N'Local',

@.subscription_priority = 0,

@.description =null,

@.use_interactive_resolver = N'False'

execsp_addmergepushsubscription_agent

@.publication = N'TestPub',

@.subscriber = N'10.126.22.30',

@.subscriber_db = N'dbTest',

@.job_login =null, @.job_password =null,

@.subscriber_security_mode = 0,

@.subscriber_login = N'Valid SQL LOGIN',

@.subscriber_password = N'ValidPassword',

@.publisher_security_mode = 1,

@.frequency_type = 64,

@.frequency_interval = 0,

@.frequency_relative_interval = 0,

@.frequency_recurrence_factor = 0,

@.frequency_subday = 0,

@.frequency_subday_interval = 0,

@.active_start_time_of_day = 0,

@.active_end_time_of_day = 235959,

@.active_start_date = 20070607,

@.active_end_date = 99991231,

@.enabled_for_syncmgr = N'False'

Pushing to an IP address is not supported. No doubt that is why it is failing. You must push to the server name. However you can setup an Alias and push to that. I think the Alias must match the server name.

I did read somewhere that Aliases may not be supported either but I know that does work. You could also consider adding entries to your hosts file.

Martin

|||

DOH!

Thanks for the reply.

I really HATE having to edit the hosts file......

Merge Replication Problem

Hi all I have a problem !!!
I use a Merge replication between 2 SQL Servers (I try with PUSH or PULL
Subscription but same problem)
Each morning in the server A I have scheduled an Import from exterenal data
( I make a DELETE all table and INSERT al data each morning)
After I schedule the creation of Snapshot in the Publisher and each hour is
scheduled the Merge replication (PUSH or PULL is the same)
The result is that in the Subscriber it make correctly the DELETE but not
the INSERT, the table in the Subscriber is empty and for all the day it says
"No merge data to replicate"
If manually it make the reinitialization in the Subscription, next merge
replication work perfectly and it works for all the day until next morning
when the script make the Import (DELETE with INSERT)
Some suggestions? Please...
Thanks a lot
Bonato Pierantonio, MCSD
Bonato - how are you doing the insert? There are 2 common reasons why the
merge triggers don't fire:
(1) If you bulk insert the rows and choose the defaults, then FIRE_TRIGGERS
is false and consequently the rows are not added to MSmerge_contents.
(2) If you do a fast-load using the Transform Data task in DTS
Fixing either of these will help new imports. In the case of already-added
rows which need replicating, you need to run sp_addtabletocontents to
include the rows then resynchronise. Alternatively you can use
sp_mergedummyupdate for a single row. For the fast load case, in future if
you deselect the check box the triggers will fire.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

merge replication one way

I saw a brief sample of a switch you can add to the merge
replication so the replication only goes one way...I know
you have to use push scription to do it...the switch is
ExchangeType='value'...can i add this within the gui
interface or am I going to have to add it commandline?Hi Jamie,
Thanks for Vyas' help. I agree with him. Also, I'm including some
supplemental information below:
-ExchangeType [1|2|3]
It specifies the type of exchange. A value of 1 indicates that the agent
should upload data changes from the Subscriber to the Publisher. A value of
2 indicates that the agent should download data changes from the Publisher
to the Subscriber. A value of 3, the default, indicates that the agent
should first upload data changes from the Subscriber to the Publisher and
then download data changes from the Publisher to the Subscriber.
For additional information regarding this issue, please refer to the
following information on SQL Server Books Online.
Topic: "Replication Merge Agent Utility"
Thanks for using MSDN newsgroup.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Merge replication not working (Push or Pull)

I'm trying to setup merge replication between two server (serverA and serverB). serverA houses the publisher DB (pubs) and Distribution DB (distribution), server B has the subscriber DB (subs). I tried first to setup a pull subscription, but the snapshot is never created in the subs db, even though the snapshot agent says everything was successful. The merge agent also never changes from the status 'Never Started'.
So I tried a push subscription. This gets me a little further, it creates the snapshot in the subs DB, but then the merge agent fails with the following error.
The subscription to publication 'pubs_customer_test' is invalid.
(Source: Merge Replication Provider (Agent); Error number: -2147201019)
------
The remote server is not defined as a subscription server.
(Source: BBLABCW03 (Data source); Error number: 14010)
------
Please help. Thanks.After creating a pull subscription to a transactional Publication, the status
of the pull subscription in the Database -> Pull Subscription Folder will
never change from the default of 'Never Started'
The job and the Pull Subscription Agent will show history for the agent, but
the status does not change in this view.
The problem is that the name of the job is greater than 100 characters, and is
trying to be placed into a temporary table that only allows 100 characters for
the job name.
SELECT job_id
FROM msdb.dbo.sysjobs
WHERE (name = N'SQL02-MyProj-DBReplication-SQL01-RptDB-D3E11F67-B38E-4DE4-82AE-9A3358B902AF')
-- Get job ID
-- Run below command with the job id as input
sp_MSenum_replication_job @.job_id = '388BFC85-BB28-434F-A7AE-77EEBB1A3C8B'
-- If you see this error, then you may need to reduce the -- job description name to resolve this issue
Server: Msg 8152, Level 16, State 6, Procedure sp_help_jobhistory, Line 91
String or binary data would be truncated.
NOTE: Then name of the job is a automatically concatenated by SQL of the
Publishing Server Name + Publishing Database + Publication Name + Subscribing Server + Subscribing Database.

Merge Replication Issue

Hi,
My Merge replication setup for a particular table has 1 subscriber and
muliple publishers. Each publisher will push the subscription to the
subscriber.
However, I am encountering some issues with this setup.
Findings:
Any record inserted/deleted/updated in either Publisher 1 or Publisher 2
will be reflected in Subscriber.
Any record inserted/deleted/updated in Subscriber will be reflected in
Publisher 1 and Publisher 2.
Issue:
Any record replicated in Subscriber from one publisher is NOT reflected in
the other publisher (e.g. Insert new record in Publisher 1, inserted record
gets replicated in Subscriber but does not insert this new record in
Publisher 2, vice versa)
I will like to find out if there is any setting or consideration that I need
to make with regards to my merge replication setup, in order to allow changes
made in any of the publisher to be replicated in the subscriber and then
reflected in other publishers.
Will definitely appreciate any of your inputs and advice.
Thanks In Advanace,
Roy Tan
Had made changes to my configuration. I have a single publisher and multiple
subscribers and everything seems to work fine. I am just wondering when do we
actually apply a "single subscriber and multiple publisher" scenario.
"Roy Tan" wrote:

> Hi,
> My Merge replication setup for a particular table has 1 subscriber and
> muliple publishers. Each publisher will push the subscription to the
> subscriber.
> However, I am encountering some issues with this setup.
> Findings:
> Any record inserted/deleted/updated in either Publisher 1 or Publisher 2
> will be reflected in Subscriber.
> Any record inserted/deleted/updated in Subscriber will be reflected in
> Publisher 1 and Publisher 2.
> Issue:
> Any record replicated in Subscriber from one publisher is NOT reflected in
> the other publisher (e.g. Insert new record in Publisher 1, inserted record
> gets replicated in Subscriber but does not insert this new record in
> Publisher 2, vice versa)
> I will like to find out if there is any setting or consideration that I need
> to make with regards to my merge replication setup, in order to allow changes
> made in any of the publisher to be replicated in the subscriber and then
> reflected in other publishers.
> Will definitely appreciate any of your inputs and advice.
> --
> Thanks In Advanace,
> Roy Tan

Merge Replication Error

Hi,
I'm getting this error on trying to setup a push Merge subscription.
The Merge Process could not initialize the subscription
{call sp_MSmergesubscribedb *;true') }
Invalid column name 'maxversion_at_cleanup'
Invalid column name 'published_in_tran_pub'
The system tables for the merge replication could not be created
successfully.
The push Merge subscription does work with two other SQL Servers. When
reviewing the table schemas, both columns are located in the
sysmergearticles table on the publisher yet neither exists on the
subscriber. Also, the creation date for the system table (sysmergearticles)
on the subscriber is over a year old. I think these are older merge system
tables that were used previously.
Anyone know how to correct this issue or is there a "safe" way to delete the
sytem tables for merge replication and push the subscription out again.
Also, which merge system tables should I delete.
I did add the two new columns to the table on the subscriber but then got
the error message that the publication was invalid. After removing the
columns things went back to the orriginal error message.
Any help is greatly appreciated!
Thanks
Jerry
Jerry,
please check that you have the latest service pack on each computer on your
replication setup.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

merge replication doesn't work properly

Hi,
I have a push replication for 4 quite simple databases. First problem was
that all of a sudden it did not work any more (after 1 month without
problems) - red crosses in the replication monitor. I finally found out that
this problem is solved by updating to SP4.
I did the update on the server, but did not succeed with the msde, so that
is still SP3. Now the users complain that some data sets disappear, others
appear only on the msde or on the server.
In the event.log there are no errors, according to the replication monitor
everything is stated to be ok - but I am getting really in trouble with the
replication not running reliably. Does anybody know that problem and its
solution.
Thanks a lot!
Susanne
Check the conflict viewer to see if the missing data is part of a conflict.
Also check to see if you are using join filters. If so a change to one of
the tables being filtered can results in data in other tables which are
reference by pk or fk relationships coming out of scope and being removed
from these tables.
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
"Susanne Senger" <susanne.senger@.web.de> wrote in message
news:eLwB1h5DGHA.2704@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have a push replication for 4 quite simple databases. First problem was
> that all of a sudden it did not work any more (after 1 month without
> problems) - red crosses in the replication monitor. I finally found out
> that this problem is solved by updating to SP4.
> I did the update on the server, but did not succeed with the msde, so that
> is still SP3. Now the users complain that some data sets disappear, others
> appear only on the msde or on the server.
> In the event.log there are no errors, according to the replication monitor
> everything is stated to be ok - but I am getting really in trouble with
> the replication not running reliably. Does anybody know that problem and
> its solution.
> Thanks a lot!
> Susanne
>
|||Hi, Hilary,
thank you for your quick infos. I am not using any filters or references in
the databases, so I 'd like to check the conflict viewer - only, my
enterprise manager is in German, so I don't have a glue where to find the
conflict viewer (nor what it is called in German), could you let me know
where I have to look for it - positions are the same in any language.
Thank you.
Susanne Senger
"Hilary Cotter" <hilary.cotter@.gmail.com> schrieb im Newsbeitrag
news:%23PWuc35DGHA.2036@.TK2MSFTNGP14.phx.gbl...
> Check the conflict viewer to see if the missing data is part of a
> conflict.
> Also check to see if you are using join filters. If so a change to one of
> the tables being filtered can results in data in other tables which are
> reference by pk or fk relationships coming out of scope and being removed
> from these tables.
> --
> 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
> "Susanne Senger" <susanne.senger@.web.de> wrote in message
> news:eLwB1h5DGHA.2704@.TK2MSFTNGP11.phx.gbl...
>
|||Open Enterprise Manager, and connect to your Publisher. expand the Databases
Folder, it will be the first folder in the tree. Locate your publication
database, it will have a hand folder icon under the icon of the database.
Expand that database node, and locate the Publications folder - it should be
the last icon in the publication database node. It might be called
Publikationen. Right click on your publication, the third menu item down
will be the view conflicts. It could be called Konfliktprojektor.
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
"Susanne Senger" <susanne.senger@.web.de> wrote in message
news:%23IwYiy9DGHA.516@.TK2MSFTNGP15.phx.gbl...
> Hi, Hilary,
> thank you for your quick infos. I am not using any filters or references
> in the databases, so I 'd like to check the conflict viewer - only, my
> enterprise manager is in German, so I don't have a glue where to find the
> conflict viewer (nor what it is called in German), could you let me know
> where I have to look for it - positions are the same in any language.
> Thank you.
> Susanne Senger
> "Hilary Cotter" <hilary.cotter@.gmail.com> schrieb im Newsbeitrag
> news:%23PWuc35DGHA.2036@.TK2MSFTNGP14.phx.gbl...
>
|||Good morning, Hilary,
thanks a lot for your infos, I could find it now. In German it is called
"Konflikte anzeigen". Now I will have to check my client's database. Do you
speak German (because of your ideas how the items could be called in German
;-))
Susanne

> database, it will have a hand folder icon under the icon of the database.
> Expand that database node, and locate the Publications folder - it should
> be the last icon in the publication database node. It might be called
> Publikationen. Right click on your publication, the third menu item down
> will be the view conflicts. It could be called Konfliktprojektor.
> --
> 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
> "Susanne Senger" <susanne.senger@.web.de> wrote in message
> news:%23IwYiy9DGHA.516@.TK2MSFTNGP15.phx.gbl...
>
|||No, but my wife speaks German; I on the other hand am fluent in slang. Paul
Ibison speaks Esperanto like a native.
I used the translate options in Google.com.
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
"Susanne Senger" <susanne.senger@.web.de> wrote in message
news:u$y$5HEEGHA.3820@.TK2MSFTNGP12.phx.gbl...
> Good morning, Hilary,
> thanks a lot for your infos, I could find it now. In German it is called
> "Konflikte anzeigen". Now I will have to check my client's database. Do
> you speak German (because of your ideas how the items could be called in
> German ;-))
> Susanne
>
>
|||Hi, Hilary,
the replicaton problems started with sp3 - on the microsoft page
http://support.microsoft.com/?scid=k...14032&x=7&y=11
I found the reason for it. After updating the server to SP4 the replication
seemed to work again. But on the other end there is a MSDE, which I did not
succeed to update. Apart from the problems with the merge replication, which
doesn't work properly, I found out that the databases on the MSDE seem to be
corrupt - it is no longer possible to insert data on the MSDE databases. Do
you have any experiences with such problens in the replication between SQL
server SP4 together with MSDE SP3?
Your Google-German sounded really convincing ;-))
Susanne
"Hilary Cotter" <hilary.cotter@.gmail.com> schrieb im Newsbeitrag
news:OzlKVfJEGHA.272@.TK2MSFTNGP10.phx.gbl...
> No, but my wife speaks German; I on the other hand am fluent in slang.
> Paul Ibison speaks Esperanto like a native.
> I used the translate options in Google.com.
> --
> 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
> "Susanne Senger" <susanne.senger@.web.de> wrote in message
> news:u$y$5HEEGHA.3820@.TK2MSFTNGP12.phx.gbl...
>
|||This shouldn't have happened. I would stop SQL Server/MSDE on the subscriber
through control panel and copy the mdf to your publisher and then do a
single file attachment there. See if you can access these databases there.
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
"Susanne Senger" <susanne.senger@.web.de> wrote in message
news:OginBVREGHA.828@.TK2MSFTNGP10.phx.gbl...
> Hi, Hilary,
> the replicaton problems started with sp3 - on the microsoft page
> http://support.microsoft.com/?scid=k...14032&x=7&y=11
> I found the reason for it. After updating the server to SP4 the
> replication seemed to work again. But on the other end there is a MSDE,
> which I did not succeed to update. Apart from the problems with the merge
> replication, which doesn't work properly, I found out that the databases
> on the MSDE seem to be corrupt - it is no longer possible to insert data
> on the MSDE databases. Do you have any experiences with such problens in
> the replication between SQL server SP4 together with MSDE SP3?
> Your Google-German sounded really convincing ;-))
> Susanne
> "Hilary Cotter" <hilary.cotter@.gmail.com> schrieb im Newsbeitrag
> news:OzlKVfJEGHA.272@.TK2MSFTNGP10.phx.gbl...
>