I recently had to completely drop replication and rebuild everything. I ran the sp_removedbreplication stored procedure at the publisher and at every subscriber server to clean everything up. I recreated the publication and attempted to add
subscribers back, but two particular subscribers keep running into issues. In SSMS it says the subscription was completed successfully and if i expand my publication in SSMS is see the subscription, but if i login to my subscriber and navigate to local
subscriptions i don't see anything created there. If i look at sysmergesubscriptions for that subscriber the application_name is null but for all my other subscribers this column has the merge agent job name. I've dropped replication a couple times
now but still this issue persists. Any ideas why i can't get the subscription to create? If i let the job run it just says can't connect to subscriber. The acct running the job has permissions to the subscriber server. I know there's
a login timeout. If the login timeout gets exceeded when creating the subscription could this result in what im seeing? A subscription at the publisher but not at the subscriber?
↧