Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Replication: Publication error Expand / Collapse
Author
Message
Posted Tuesday, September 18, 2012 9:01 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, June 2, 2014 7:24 PM
Points: 286, Visits: 572
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?
Post #1361111
Posted Tuesday, September 18, 2012 9:29 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, June 16, 2014 10:44 AM
Points: 153, Visits: 583
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.
Post #1361119
Posted Tuesday, September 18, 2012 10:40 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, June 2, 2014 7:24 PM
Points: 286, Visits: 572
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?
Post #1361129
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse