It looks like this problem occurs when your database maintenance plan is trying to create a transaction log backup of a database which is Off-line or when a database is using the Simple Recovery model.I solved the problem by creating 2 maintenance plans. One for all the Simple Recory model databases with no transactionlog backup and one for all the Full Recovery databases with a transactionlog backup.
The same error is also generated when your disk is full.
2 commenti:
Would like to say that, i believe this is correct. I found both situations happing on a server i've just taken over maintaining. Freed up some space and moved the transaction log backup time to a more suitable one, boom no problem.
Many Thanks
Post a Comment