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...
>