After looking around further, I found a 'REPL-Distribution' job on a different instance that related to the database in the error and it seems this was the source of the problem. I have stopped that now and the errors have ceased. Phew.
Viewing post 1 (of 2 total)
You must be logged in to reply to this topic. Login to reply