This is just really a note to the other DBAs out there since I spent half an hour on this issue only to find it was an illogical random problem, but if you can't be bothered reading my story the short hand version is If you are having issues with replication and getting errors concerning snapshot being out of date or not available before you try to go on the wild goose chase, try restarting the SQL Agent service first.
Anywho back to what happened, got a call from a client that the server had stopped replicating between London and Basra, so I got into the server and check the replication monitor, under the subscription it stated You must rerun snapshot because current snapshot files are obsolete. OK I thought and started the snapshot agent, off it went and came back a few seconds later stating A snapshot of 94 articles has been generated. Now this is a 27GB database so I know for a fact that it takes ages for the snapshot to come around, I messed around with folder permissions on the snapshot directory, all seemed fine, I delete the current snapshot and tried the agent again. A snapshot of 94 articles has been generated... LIES!
At this point I went into the Job Manager and ran the merge replication job to see what errors would come up in the history.. The Job failed. The owner of job() ..... does not have server access and that was what made me finally figure what it was. A while back I had the same issue after a power cut, for some reason if there is network failure the Agent has a heart attack and just stops working. Restarting the service fixes the problem.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment