Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Publisher is not replication

Folks,

I have a cluser that is composed of 1 pub and 3 subs. I have installed DBLHelper utility and it is showing me that the pub is red in color(out of sync), i tried republishing a couple of times but i get the same thing, anything else i can do to fix the problem?

6 REPLIES
Green

Re: Publisher is not replication

DBL Monitor, MSSQLServer and SQLserver agent services running under SQLSVC?

No NIC missmatch?

Using Adminutility passwords are synch ?

All servers running same version?

CCMAdmin | Help | Component Versions | Out of synch

LMhosts and Hosts files are ok in ALL servers?

Servers meet Network and BW requirements?

Community Member

Re: Publisher is not replication

DBL Monitor, MSSQLServer and SQLserver agent

Yes

services running under SQLSVC?

Yes

No NIC missmatch?

Yes

Using Adminutility passwords are synch ?

Yes

All servers running same version?

Yes

CCMAdmin | Help | Component Versions | Out of synch

LMhosts and Hosts files are ok in ALL servers?

Yes

Servers meet Network and BW requirements?

Yes

But still the Pub shows up as red when i run dblhelper?

Green

Re: Publisher is not replication

If all is good,

Try to recreate the subscription manually.

Otherwise open a TAC Case-

Community Member

Re: Publisher is not replication

How do I do that?

I have one open already.

I will surely rate this post.

Thanks for the help.

Community Member

Re: Publisher is not replication

Parwal you must try Manual Subscription below is link just follow n i think it should work for u

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801d11a6.shtml

Silver

Re: Publisher is not replication

Are you sure yo are not hitting Bug CSCsa98895??

Symptom:

DBLHelper may incorrectly report that SQL replication is broken. DBLHelper will show a red frowny face

on the publisher giving an indication that SQL replication is broken.

Condition:

This problem may occur with DBLHelper 4.1(0.20) and earlier when the only SQLAgent job which is failing

is the Expired Subscription Clean Up job.

Workaround:

From MSSQL Enterprise Manager connect to the publisher SQL server and make sure that the Expired

Subscription Clean Up job runs successful.

126
Views
0
Helpful
6
Replies
CreatePlease to create content