conflicts in data don't appear in conflicts for subscription

I have become aware that some database entries were not "syncd" from a
disconnected server when it came online. My only guess is that a conflict
resulted when the syncd finally happened. The problem is it was 5 days ago,
and when I look at the conflicts under the subscription, the box is empty.
How can I see conflicts from 5 days ago?
WB
Use the conflict viewer to view them. By default they are stored for 14
days or whatever you have set to be conflict_retention value to be in
sp_addmergepublication.
http://www.zetainteractive.com - Shift Happens!
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
"WB" <none> wrote in message news:OjAYszpQIHA.4440@.TK2MSFTNGP06.phx.gbl...
>I have become aware that some database entries were not "syncd" from a
> disconnected server when it came online. My only guess is that a conflict
> resulted when the syncd finally happened. The problem is it was 5 days
> ago,
> and when I look at the conflicts under the subscription, the box is empty.
> How can I see conflicts from 5 days ago?
> WB
>
|||I am not sure what you mean when you say "use the conflict viewer..." I
open Enterprise Manager, then replication and right click on the
publication. A popup menu appears and one of the options is to view
conflicts. Is that what you mean? Is there some way to view conflicts? I
will look at the properties of the publication to see if I can locate the
days for which conflicts are kept.
WB
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23nZH2nrQIHA.2396@.TK2MSFTNGP02.phx.gbl...
> Use the conflict viewer to view them. By default they are stored for 14
> days or whatever you have set to be conflict_retention value to be in
> sp_addmergepublication.
> --
> http://www.zetainteractive.com - Shift Happens!
> 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
> "WB" <none> wrote in message news:OjAYszpQIHA.4440@.TK2MSFTNGP06.phx.gbl...
>
|||That is exactly what I mean. Conflict retention is not exposed in the
publication properties dialog.
http://www.zetainteractive.com - Shift Happens!
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
"wb" <none> wrote in message news:ucqfHHyQIHA.2208@.TK2MSFTNGP06.phx.gbl...
>I am not sure what you mean when you say "use the conflict viewer..." I
>open Enterprise Manager, then replication and right click on the
>publication. A popup menu appears and one of the options is to view
>conflicts. Is that what you mean? Is there some way to view conflicts?
>I will look at the properties of the publication to see if I can locate the
>days for which conflicts are kept.
> WB
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23nZH2nrQIHA.2396@.TK2MSFTNGP02.phx.gbl...
>

Conflict Viewer included with MSDE 2000 Release A?

It seems that installing MSDE 2000 Release A does not install the conflict viewer, and therefore if a subscription is set to allow interactive conflict resolution at the client, it will not work...
Does anyone have the definitive answers to the following?
- Is Conflict Viewer supposed to be included with MSDE 2000 Rel A?
- Was it included in versions of MSDE prior to Rel A (my research has indicated that it was)?
- Is Conflict Viewer redistributable (hopefully there's a merge module somewhere?!)
- Does any other MS product apart from SQL Server install the Conflict Viewer (we have observed that certain machines that don't have SQL Server installed still have the conflict viewer...)?
Just for more information, our scenario is as follows:
- SQL Server 2000 database server, set with a publication allowing anonymous pull subscriptions, and articles set up to allow interactive conflict resolution.
- MSDE 2000 Rel A clients, with anonymous pull subscriptions to the server. When an on-demand synchronisation is attempted, we get the following message - "the process failed to
get information about the interactive resolver component from the
registry".
- If the files under Program Files\Common Files\Microsoft Shared\Database Replication are manually copied across and registered, it all works.
There's other posts asking similar questions in the replication discussion group, from Tanya Milanova and markeboy, but the answers given don't answer the question about redistribution of the component...
Cheers, Jim
Conflict Viewer as well as all the other tools for setting up and
maintaining replication on SQL Server 2000 are part of Enterprise Manager
and are not (and never have been) part of the MSDE distribution. The SQL
Server 2000 client tools (EM) cannot be legally redistributed.
Jim
"Jim Kirton" <JimKirton@.discussions.microsoft.com> wrote in message
news:EC5C41EB-AACB-4642-B57B-81C343DC8DE5@.microsoft.com...
> It seems that installing MSDE 2000 Release A does not install the conflict
viewer, and therefore if a subscription is set to allow interactive conflict
resolution at the client, it will not work...
> Does anyone have the definitive answers to the following?
> - Is Conflict Viewer supposed to be included with MSDE 2000 Rel A?
> - Was it included in versions of MSDE prior to Rel A (my research has
indicated that it was)?
> - Is Conflict Viewer redistributable (hopefully there's a merge module
somewhere?!)
> - Does any other MS product apart from SQL Server install the Conflict
Viewer (we have observed that certain machines that don't have SQL Server
installed still have the conflict viewer...)?
> Just for more information, our scenario is as follows:
> - SQL Server 2000 database server, set with a publication allowing
anonymous pull subscriptions, and articles set up to allow interactive
conflict resolution.
> - MSDE 2000 Rel A clients, with anonymous pull subscriptions to the
server. When an on-demand synchronisation is attempted, we get the following
message - "the process failed to
> get information about the interactive resolver component from the
> registry".
> - If the files under Program Files\Common Files\Microsoft Shared\Database
Replication are manually copied across and registered, it all works.
> There's other posts asking similar questions in the replication discussion
group, from Tanya Milanova and markeboy, but the answers given don't answer
the question about redistribution of the component...
> Cheers, Jim

Conflict Resolution: Is defining local subscription enough: How to get log of lost record.

Hello All,
I am very much thankful to you all for providing much needed help, and
once again I am at the group with my query. In my replication
implementation in which I have around 100 subscriber I need to decide
what conflict resolution policy should be employed.
We, in our implementation just want that publisher always wins in case
if there is any conflict. Is it enough to create a local subscription
to acheieve this.
Which will ensure that in case of any conflict with the publisher
publisher always wins the conflict.
Also we want that losing party should get log of inforamtion about the
lost record, is there any way to acheive this?
Can you define what you mean by a local subscription?
The best way to alert the user of conflicts is to use the com object
C:\Program Files\Common Files\Microsoft Shared\Database
Replication\WZCNF.DLL
This will display a list of the conflicts. You will then have to poll for
them and send out alerts.
Subscriptions managed by Windows Synchronization Manager using the
interactive resolved will allow the user to manage the conflict when WSM
runs.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501172243.6e17e067@.posting.google.c om...
> Hello All,
> I am very much thankful to you all for providing much needed help, and
> once again I am at the group with my query. In my replication
> implementation in which I have around 100 subscriber I need to decide
> what conflict resolution policy should be employed.
> We, in our implementation just want that publisher always wins in case
> if there is any conflict. Is it enough to create a local subscription
> to acheieve this.
> Which will ensure that in case of any conflict with the publisher
> publisher always wins the conflict.
> Also we want that losing party should get log of inforamtion about the
> lost record, is there any way to acheive this?

Conflict Resolution: Is defining local subscription enough: How to get log of lost record.

Publisher always wins is the default, so you don't need
to do anything to achieve this.
To get notification of a conflict, you could create a
polling routine (there's no alert that I know of).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
hi Paul,
Thanks for you reply, I have few more queries
1. Where is this conflict information specially the losing row information is stored, at the publisher side or at the subscriber side? if losing row information is maintained at the publisher side is there any way so that we can store this information at the publisher side.
2. As you talked about creating a polling routine to get notification of conflict, in my implementation I just want a log file which contain information about the losing row nothing else, will the polling routine you are referring to can do the same and alsoI have not much information about how to write polling routine can you throw some light on it?
regards.
Ruchir.

Quote:

Originally posted by Paul Ibison
Publisher always wins is the default, so you don't need
to do anything to achieve this.
To get notification of a conflict, you could create a
polling routine (there's no alert that I know of).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

|||Have a look at the tables
conflict_<PublicationName>_<ArticleName>_usertable name
and
MSmerge_delete_conflicts
at the publisher.
The polling routine would be not much more than a job
that runs regularly and does a select from this table,
then sends the results in an email as an attachment. The
origin_datasource column could be used to determine the
correct recipient.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Configuring subscription database as publication.

Hi, I need to configure this scenario
Part 1: Transactional publication configured in database A, the
subscriber is database B.
Part II: Configure a transactional publication in database B and send it
to database C and D.
I already configure the part 1 of the scenario. But when i try to
configure part B, i have the problem that the tables in database b Dont
have primary key, I try changing this option on each article:
"Delete all data in the the existing table". Assuming that if i already
create the tables with primary key, it will work, but it didnt.
Do somebody know how to configure it?
Thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Maria,
on the article properties, select to take the declarative referential
integrity. This'll ensure that PKs don't become just unique indexes on the
subscriber, and the PKs will be created there.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Configuring a remote server as a subscription server

I'm trying to do a merge replciation between two servers however the merge
agent fails announcing that: "The remote server is not defined as a
subscription server (The error number is 14010)".
Here are more details:
The first server (publisher & distributor) has SQL Server enterprise edition
installed using SQL Server authentication. The IP address for this server is
192.168.62.2 and the subnet mask is 255.255.255.0
The second server (subscriber) the same as the publisher however the IP
address is 192.168.64.2 with a subnet mask of 255.255.255.0.
Note that there is no domain connectiong the two server!
I have regisrtered the subscriber at the publisher and cretaed the merge
replciation successfully. However the merge agent fails as specified above!
Thanks in advance,
Shehab.
On the publisher go to Tools, Replication, Configure Publisher, Subscribers,
and Distribution, click on the Subscribers tab and add it 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
"Shehab Kamal" <ShehabKamal@.discussions.microsoft.com> wrote in message
news:1BB0A342-B704-4222-B617-B6F70638AC3C@.microsoft.com...
> I'm trying to do a merge replciation between two servers however the merge
> agent fails announcing that: "The remote server is not defined as a
> subscription server (The error number is 14010)".
> Here are more details:
> The first server (publisher & distributor) has SQL Server enterprise
> edition
> installed using SQL Server authentication. The IP address for this server
> is
> 192.168.62.2 and the subnet mask is 255.255.255.0
> The second server (subscriber) the same as the publisher however the IP
> address is 192.168.64.2 with a subnet mask of 255.255.255.0.
> Note that there is no domain connectiong the two server!
> I have regisrtered the subscriber at the publisher and cretaed the merge
> replciation successfully. However the merge agent fails as specified
> above!
> Thanks in advance,
> Shehab.

Configure Server for Email Delivery

I am having trouble getting a report emailed for the first time.
The timed subscription has been set. I have updated the ReportServer.config
file to include the ip of the exchange server along with port number although
im not sure where to enter a password. The IT guys are making sure that the
exchange server will accept smtp requests from other servers. My question is
what is the best method to troubleshoot & is there anything gleeming that i
am missing. ThanksI have noted that the sql server agent has a job logged & shows suceeded when
last run but I have recieved any emails. I have also noted a job in the
process info that has a status of sleeping. Event log shows nothing
"Tango" wrote:
> I am having trouble getting a report emailed for the first time.
> The timed subscription has been set. I have updated the ReportServer.config
> file to include the ip of the exchange server along with port number although
> im not sure where to enter a password. The IT guys are making sure that the
> exchange server will accept smtp requests from other servers. My question is
> what is the best method to troubleshoot & is there anything gleeming that i
> am missing. Thanks|||Can anyone help, please. Maybe a link to a ReportServer.config that is
successfully emailing reports might help.
Thankyou
"Tango" wrote:
> I have noted that the sql server agent has a job logged & shows suceeded when
> last run but I have recieved any emails. I have also noted a job in the
> process info that has a status of sleeping. Event log shows nothing
> "Tango" wrote:
> > I am having trouble getting a report emailed for the first time.
> > The timed subscription has been set. I have updated the ReportServer.config
> > file to include the ip of the exchange server along with port number although
> > im not sure where to enter a password. The IT guys are making sure that the
> > exchange server will accept smtp requests from other servers. My question is
> > what is the best method to troubleshoot & is there anything gleeming that i
> > am missing. Thanks|||Tango,
Did you ever find out an answer to this? If so could you please share it?
"Tango" wrote:
> Can anyone help, please. Maybe a link to a ReportServer.config that is
> successfully emailing reports might help.
> Thankyou
> "Tango" wrote:
> > I have noted that the sql server agent has a job logged & shows suceeded when
> > last run but I have recieved any emails. I have also noted a job in the
> > process info that has a status of sleeping. Event log shows nothing
> >
> > "Tango" wrote:
> >
> > > I am having trouble getting a report emailed for the first time.
> > > The timed subscription has been set. I have updated the ReportServer.config
> > > file to include the ip of the exchange server along with port number although
> > > im not sure where to enter a password. The IT guys are making sure that the
> > > exchange server will accept smtp requests from other servers. My question is
> > > what is the best method to troubleshoot & is there anything gleeming that i
> > > am missing. Thanks|||It is notoriously difficult to get the subscriptions to work, I spent a week
configuring a production server trying to do this and gave up, I have the
feeling you need to re-install RS using different accounts/settings, which in
my case wasn't an option. I ended up coding a small windows service that
downloaded the report through a crafted URL and emailed it based on a
schedule in a table. It actually took less to code that snippet than to
configure the much glorified data driven subscription feature of RS.
Microsoft shouldn't be in such a hurry to advertise features that won't even
work in plain vanilla, no frills install out of the box.
Regards,
Tzepesh
"Tango" wrote:
> Can anyone help, please. Maybe a link to a ReportServer.config that is
> successfully emailing reports might help.
> Thankyou
> "Tango" wrote:
> > I have noted that the sql server agent has a job logged & shows suceeded when
> > last run but I have recieved any emails. I have also noted a job in the
> > process info that has a status of sleeping. Event log shows nothing
> >
> > "Tango" wrote:
> >
> > > I am having trouble getting a report emailed for the first time.
> > > The timed subscription has been set. I have updated the ReportServer.config
> > > file to include the ip of the exchange server along with port number although
> > > im not sure where to enter a password. The IT guys are making sure that the
> > > exchange server will accept smtp requests from other servers. My question is
> > > what is the best method to troubleshoot & is there anything gleeming that i
> > > am missing. Thanks|||Report server will only work against an SMTP server that accepts anonymous
or NTLM authentication. The best solution for email is to use a local SMTP
server as a relay to your smtp server. Set the pickup directory element in
the RSReportServer.config file to the local SMTP servers pickup directory
and the SendUsing element to 1. Then configure your local SMTP server to
relay the email to your actual SMTP server.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tzepesh" <Tzepesh@.discussions.microsoft.com> wrote in message
news:547E777A-F7A3-4F9A-A7AA-236F22E04966@.microsoft.com...
> It is notoriously difficult to get the subscriptions to work, I spent a
> week
> configuring a production server trying to do this and gave up, I have the
> feeling you need to re-install RS using different accounts/settings, which
> in
> my case wasn't an option. I ended up coding a small windows service that
> downloaded the report through a crafted URL and emailed it based on a
> schedule in a table. It actually took less to code that snippet than to
> configure the much glorified data driven subscription feature of RS.
> Microsoft shouldn't be in such a hurry to advertise features that won't
> even
> work in plain vanilla, no frills install out of the box.
> Regards,
> Tzepesh
> "Tango" wrote:
>> Can anyone help, please. Maybe a link to a ReportServer.config that is
>> successfully emailing reports might help.
>> Thankyou
>> "Tango" wrote:
>> > I have noted that the sql server agent has a job logged & shows
>> > suceeded when
>> > last run but I have recieved any emails. I have also noted a job in the
>> > process info that has a status of sleeping. Event log shows nothing
>> >
>> > "Tango" wrote:
>> >
>> > > I am having trouble getting a report emailed for the first time.
>> > > The timed subscription has been set. I have updated the
>> > > ReportServer.config
>> > > file to include the ip of the exchange server along with port number
>> > > although
>> > > im not sure where to enter a password. The IT guys are making sure
>> > > that the
>> > > exchange server will accept smtp requests from other servers. My
>> > > question is
>> > > what is the best method to troubleshoot & is there anything gleeming
>> > > that i
>> > > am missing. Thanks