We are using Transactional Replications with updatable subscriptions. 1 publisher, 1 subscriber.
SQL Replication started encountering a constraint error on 3/6 at 10AM because people at two different offices entered data that violated a unique constraint. Totally expected.
However, at 12:08PM on 3/6, SQL Replication stopped reporting that error and instead said:
"The initial snapshot for publication 'TheDB' is not yet available."
Why would it stop retrying replication and instead start throwing this error? Now we need to regenerate the snapshot.
- No DB backups or restores were performed at this time
- The snapshot was successfully applied at the subscriber months ago when replication was initially set up.
- There is a message in the log from 12:07 on 3/6 saying
 Request to run job COTOPSVR\TheDB-TheDB-COTCPSVR\DB-3 (from User CTOB\Administrator) refused because the job is already running from a request by User sa
- No one manually initiated any job or did anything at all at 12:06PM.
Any ideas? I know how to fix this...I want to prevent this from happening again.