SQL Replication Error: Fixing 'Remote Server Does Not Exist' with a Permissions Check

Don’t Forget to Check Permissions

Here’s a quick post to remind myself and others to check all the permissions when working with replication — especially ones that are easy to miss when you’re setting it up across multiple servers.

For the past couple of days, I’ve been working on getting transactional replication set up between a couple of servers while juggling other projects. For the last day I kept running into the following error:

1
"The remote server <server name> does not exist, or has not been designated as a valid Publisher, or you may not have permissions to see available Publishers."

That error message is misleading — it sounds like a network or configuration problem, but in this case it was a permissions issue.

The Fix

Make sure the Log Reader Agent account has db_owner role membership on the distribution database. That’s the one I missed — our other replication setup uses a dedicated Distribution server where this was already in place, so I hadn’t thought to check it here.

To grant it:

1
USE distribution;
2
GO
3
EXEC sp_addrolemember 'db_owner', 'DOMAIN\log_reader_account';

Replace DOMAIN\log_reader_account with your actual Log Reader Agent account. You can verify current role memberships in the distribution database with:

1
USE distribution;
2
GO
3
SELECT dp.name AS principal, dr.name AS role
4
FROM sys.database_role_members drm
5
JOIN sys.database_principals dp ON drm.member_principal_id = dp.principal_id
6
JOIN sys.database_principals dr ON drm.role_principal_id = dr.principal_id
7
ORDER BY dr.name, dp.name;

Why This Is Easy to Miss

When you set up transactional replication, the wizard handles a lot of permissions automatically — but not all of them, and the defaults depend heavily on how your distribution database is configured. If you’re reusing an existing distributor or migrating replication between environments, it’s easy for this grant to get lost.

The error message doesn’t help. “Remote server does not exist” points you toward DNS, linked servers, or publisher registration — not permissions on the distribution database.

Key Takeaways

The “remote server does not exist” replication error often means a permissions problem, not an actual connectivity issue.
The Log Reader Agent account needs db_owner membership on the distribution database.
When setting up replication, audit permissions on the distributor explicitly — don’t assume the wizard covered everything.