Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Replication: Publication error


Replication: Publication error

Author
Message
MissTippsInOz
MissTippsInOz
SSC Veteran
SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)

Group: General Forum Members
Points: 289 Visits: 597
A red cross against a Publisher is an indication that there is a problem with the replication. If you drill down into it, what do you see?

Clare
_________________________________________________________________________________________________________________
Measure twice; cut once (and have a good saw)

Hey, just a thought.....did you check Books Online yet?
anzz
anzz
SSC-Enthusiastic
SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)

Group: General Forum Members
Points: 171 Visits: 690
My findings are:

1)Job on DBSTU server: Agent history clean up: distribution is failing.
From the Job error I figured out was Table [dbo].[MSmerge_history] on distribution was missing.
This is causing issue? I am not sure...


2)I did a test for small database, it works fine.
The REPL_snapshot, REPL_logreader and REPL_dist are running fine.
MissTippsInOz
MissTippsInOz
SSC Veteran
SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)SSC Veteran (289 reputation)

Group: General Forum Members
Points: 289 Visits: 597
Danzz (9/18/2012)
My findings are:

1)Job on DBSTU server: Agent history clean up: distribution is failing.
From the Job error I figured out was Table [dbo].[MSmerge_history] on distribution was missing.
This is causing issue? I am not sure...


2)I did a test for small database, it works fine.
The REPL_snapshot, REPL_logreader and REPL_dist are running fine.


The fact that the Agent history cleanup job is failing will not, in itself be the reason you're seeing an error in Replication Monitor. However I'd certainly be very concerned if that table is not there. It should always exist the distribution database, as far as I know, and suggests that you have deeper issues.

Possibly a silly question but it is merge replication you have configured right?

Clare
_________________________________________________________________________________________________________________
Measure twice; cut once (and have a good saw)

Hey, just a thought.....did you check Books Online yet?
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search