I have this setup, server A is the distributor/Subscriber and server B is the publisher, SQL agent account is different in each server and they are domain accounts. Each server has an application ID, a domain account as well, say user A for server A and User B for Server B. User A and User B are both member of Admin group of both server and both are sysadmin in SQL instances in both servers. I setup a replication using the procedure by the vendor.(they have the tool to do the setup for replication for their application. just input informations and let the tool do it(in other words, a wizard. ;-)) I used User B as log reader agent(that's the only account/ID required by the tool aside from the repldata folder of subscriber and the server names). The tool said the replication is setup properly but there's error in the replication.
Date 7/05/2013 12:18:29 PM
Log Job History (<<jobname>>
Step ID 2
Job Name <<jobname>>
Step Name Run agent.
Sql Severity 0
Sql Message ID 0
Operator Net sent
Retries Attempted 27
Unable to start execution of step 2 (reason: Error authenticating proxy <<UserB>>, system error: Logon failure: user not allowed to log on to this computer.)
What I did was to change the credentials of the proxy(in the subscriber) to use User A instead of User B and the replication worked. I have no idea how the vendor tool setup the replication but I am guessing that the log reader agent which the one I inputted as User B are the one used by the tool to set as proxy account. but the thing is, both users are admin and sysadmin on both boxes, i wonder why i got this error. when I tried to connect via RDC using those user A to server B, i've got the error saying not allowed to use the computer. same goes with User B connecting to server A. could this be an issue? but they able to connect to the instances.
both SQLs are Enterprise, build 11.0.2325
can someone shed some light?:-)