Hello,
I'm relatively new to setting up Transactional Replication and I've been running into a bit of a problem that I was hoping someone could help with.
Essentially I have two different SQL instances with different names, but they contain databases that have the same name. One is a lab environment, the other a production environment. The production environment also has the ReportServer databases on it and already has transactional replication working on it (setup by my predecessor).
With the above in mind I'm trying to setup the lab environment to also use transactional replication using a copy of the production database on it, but when I get as far as creating a publisher and start up the replication jobs some really weird stuff happens. For one, some of the replication jobs on the production server (which jobs appears to be random) stop working and say they can not execute'sp_replcmds' on the instance the production DB's reside. Further, when anyone tries to run a report on SSRS they get an error stating that the report server cannot open a connection to the report server database.
If I delete the publication on the lab server and have the report server restarted, the issues go away. Replication starts working on the production sever again and people can access their reports.
Has anyone seen this before? My gut feeling is this is some sort of permissions or naming issue, but for the life of me I can't see why actions taken on a lab server would impact an entirely different SQL instance on the production server.
Thanks for any help.