Recently we encounter some errors on the log reader agent job for all our publishers in our push replication setup. All publisher dbs are coming from the same db in the publishing server. Our distribution db is on its own physical box. We are using SQL 2008 r2. The first error is related to“The process could not execute 'sp_replcmds' . The second one is "Could not obtain information about Windows NT group/user 'domain\xxxxxx', error code 0x5”. The strange thing about the second error is that we don't use that account to set up the replication. I am using a totally different account for it. Just in case, I checked all log reader security set up for the publisher dbs and it is using the sql job agent account by impresonation and not using the said domain account in the error. Another interesting about this problem is that the problem would self-correct meaning after a few hours of giving out the errors, the log reader would function again and distributing the commands to the distrbution db.
I need to find out why the replication is giving out an error on a domain account that we don't use. A little bit of background info here. We did move all our servers to a different location and set up a new domain for everything. However, all replication setup started from scratch so there is no chance I would use the said account to set up my replication. the only thing that is coming from the old location (or old domain) is the databases. We did a backup and restore to bring the databases to the new location but we don't restore the original publisher settings during the restore.
Is it possible that somehow there is some old replication setting related to the said domain account somewhere in our current replication setup somewhere? Is there a command I can use to search for this domain account in our replication setup? Any ideas or thoughts are very much appreciated.
od
Ocean Deep