Stop the replication server's SQL Server service (or Pause it, I don't know if that would work) and then restart it after? It's kind of a sledgehammer fix, but it's pretty simple.