First time running a replication on SQL Server 2008. "The process could not connect to subscriber 'SERVER2'" I've set up Replication between two remote servers, Using Peer to Peer &amp; Transactional updates. The subscription is all set, but the actual replication doesn't take place.

When viewing the Synchronization Status of the subscription, i get an error, saying "The process could not connect to Subscriber 'SERVER2\DBINSTANCE'."

Clicking on start, this is the error message I get:



TITLE: View Synchronization Status

The agent could not be started.

For help, click: go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&amp;ProdVer=10.50.1600.1&amp;EvtSrc=Microsoft.SqlServer.Management.UI.ReplUtilitiesErrorSR&amp;EvtID=CantStartAgent&amp;LinkId=20476



ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)



SQLServerAgent Error: Request to run job SERVER\DBINSTANCE-DBNAME-DBPUBLICATION-SERVER2\DBNAME-3 (from User sa) refused because the job is already running from a request by Start Sequence 0.
Changed database context to 'DBNAME'. (Microsoft SQL Server, Error: 22022)

For help, click: go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&amp;ProdVer=10.50.1600&amp;EvtSrc=MSSQLServer&amp;EvtID=22022&amp;LinkId=20476



Viewing the Agent History, trying to get more specific into the error, i get the following Error:



Error messages:
The process could not execute 'sp_replcmds' on 'SERVER\DBNAME'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: help/MSSQL_REPL20011
Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission. (Source: MSSQLServer, Error number: 15517)
Get help: help/15517
The process could not execute 'sp_replcmds' on 'SERVER\DBNAME'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: help/MSSQL_REPL22037



I have looked each and every one of the errors online, went through all this kind of explanations and changes, and nothing worked.
Many thanks to anyone who can pour some light on the issue.
This is likely a permissions issue.

Verify that your replication agent accounts have the necessary permissions listed in the section Permissions That Are Required by Agents in Replication Agent Security Model.