Hi,

As far I know distribution agent ONLY accessing distributor and distribution db. Only logreader and snapshot agents are accessing publisher. Unless you setup local distribution then distribution agent...

I got this error in two cases.

1. Db ownership (as other people said sp_changedbowner 'sa' - do not use GUI to do this).

2. Permission issues

Please check first what user...

Correct me if Im wrong there are more than one subscriptions going into same database? One is pull and second push?

The only big difference between these two is the location...

doesnt seem like it is issue with Distribution Agent profile as it got the values for the given profile:

2016-12-05 00:41:46.179 Parameter values obtained from agent profile:

-bcpbatchsize 2147473647

-commitbatchsize 100

-commitbatchthreshold 1000

-historyverboselevel 2

-keepalivemessageinterval...

HI,

Yes we did upgrade subscribers before and we did not stop activity on publisher. Either u can stop logreader or distribution agent before doing an upgrade on subscriber.

Could u check logreader and Snapshot? Any of these is failing or giving some error?

dwilliscp (10/29/2016)

---

Replication has been running for about the last 9 months and now we have had two day's where ever time "EXEC dbo.sp_MSdistribution_cleanup @min_distretention = 0, @max_distretention = 36" runs...

Im assuming u want to use transactional replication and have date in real time on subscribers?

If yes, then it is one of the best solutions to offload data for reading...

SQL-DBA-01 (11/4/2016)

---

Publisher to Distributor History and in Distributor to Subscriber History I can see -

1 transaction(s) with 1 command(s) were delivered.

How to validate what was the change been applied to...

Seems like problem with updating distributor. Is it accessible?

Try add parameter

@ignore_distributor = 1