• Hey Guys so it sounds like solution for creating publication with the same name and deleting it works great for everyone. I just wanted to mention that I too had this issue with Replication Monitor not clearing up errors in 2014. I used sp_removedbreplication and confirmed all replication was gone ( i even dropped databases to make sure) and still got the same error. I realized that the agent jobs for replication for the old publication was still there and re-trying. I ended the job, disabled the jobs and in the next cycle of refresh Replication monitor cleaned up. I the method mentioned above is the cleanest way to do it because if you hand pick internal tables you will not know which ones are clean and left over.

    I vote for creating a publication with the same exact name and deleting it to ensure all the internals are cleaned.

    Hope this feedback helps.