Thank you very much!

all your assumptions are correct. I agree, it doesn't make any sense. I tried to run t-sql code from my SP manually and this error occurs after it...

Nothing. I didn't call it. This is the error my SP finishes with.

I would really appreciate any suggestions.

All subscribers are listening through the standard port 1433

all old subscriptions are working, just the added one shoes agent failure when we try to initialize it.

we tried to restart job which failed. No luck, the same error messages

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...

True. Each job (for publication we are trying to add subscriptions) gives the same error

yes. When we setup everything first time with n number of subscribers it went through without problems. Replication is working perfectly. When later on we tried to...

this is exactly where I took a look:

-Publisher [ASH2VCL05INST4\CLSAVCL05INST4] -PublisherDB [VS_VALIDATION] -Distributor [ASH2VCL05INST3\CLSAVCL05INST3] -Publication [VS_VALIDATION] -DistributorSecurityMode 1 -Continuous

The replication agent encountered an error and is set to restart within...

The problem is that there is no previous message at all. In replication monitor it says - check the job.

I tried it with nolock and without, but it didn't have any impact on a bad query plan 🙁 the only improvement I saw when i put the table...

I tried it with nolock and without, but it didn't have any impact on a bad query plan 🙁 the only improvement I saw when i put the table...

Just tried it with and without (nolock) option - doesn't make any difference. The problem in my eyes that SQL Server is trying to join #temp table with one...