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

Transactional replication problem Expand / Collapse
Author
Message
Posted Wednesday, March 20, 2013 9:36 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 4:13 PM
Points: 285, Visits: 897
What happens if you restart one of the existing Distribution jobs.
You may get cleaner errors in the job history.
Post #1433313
Posted Thursday, March 21, 2013 8:33 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, February 19, 2014 3:34 PM
Points: 24, Visits: 177
Still experiencing a problem. Maybe someone can give us any directions.
All I found online was about some user/persmissions issues. We dropped everything and re-created from the scratch publisher-distributor-subscriber using 1 user with DBA role.
Adding several subscriptions went well and everything is working. The minute we add another subscription we have a problem.
We have 10 publications with 12 subscribers to each running successfully. Adding new subscribers is an issue.
Is it any capacity problem? Should we modify any parameters?

Any input will be welcome.

Thanks.
Post #1433814
Posted Thursday, March 21, 2013 9:37 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, February 19, 2014 3:34 PM
Points: 24, Visits: 177
we tried to restart job which failed. No luck, the same error messages
Post #1433870
Posted Thursday, March 21, 2013 10:33 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 4:13 PM
Points: 285, Visits: 897
Do all the subscriptions fail, or only the new ones you add?
Post #1433902
Posted Thursday, March 21, 2013 12:40 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, February 19, 2014 3:34 PM
Points: 24, Visits: 177
all old subscriptions are working, just the added one shoes agent failure when we try to initialize it.
Post #1433967
Posted Thursday, March 21, 2013 12:41 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 4:13 PM
Points: 285, Visits: 897
Any errors in the error log on the instance that is the subscriber?
Post #1433969
Posted Thursday, March 21, 2013 12:44 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 4:13 PM
Points: 285, Visits: 897
You can test logging into one of the new subscriber instances with the Distributor agent credentials.
Do this from the publisher machine.

If you can log in, then try to create a new bogus object in the subscriber database.
Post #1433973
Posted Thursday, March 21, 2013 12:47 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 4:13 PM
Points: 285, Visits: 897
Are the new subscribers listening on the default port 1433.
If not you will need to create an alias via the SQL configuration manager
Post #1433975
Posted Thursday, March 21, 2013 1:09 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, February 19, 2014 3:34 PM
Points: 24, Visits: 177
All subscribers are listening through the standard port 1433
Post #1433991
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse