1

Here is the error message in its entirety:

Failed:(-1073548784) Executing the query "BACKUP DATABASE [MCM] TO DISK = N'F:\Backup\MCM\M..." failed with the following error: "BACKUP DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

There is no further information. No backups for any database on the server are working right now, but they did succeed the day before. There is plenty of backup space. One thing to note, though I'm not sure if it's relevant, is that there was a transaction stuck in a Killed/Rollback state the day before; it was blocking on a remote procedure call to a Sybase database. The service was restarted to try to "fix" this stuck transaction (by someone I warned beforehand against doing such a thing).

What do I need to do to fix this situation so that I can get the backups working again?

migrated from serverfault.com Sep 22 '14 at 20:40

This question came from our site for system and network administrators.

  • There's enough information here to say. Check your windows event logs. – Katherine Villyard Sep 19 '14 at 23:35
  • The error given is the only thing in the event logs. There is no more information in any other log I've checked. – reasonet Sep 19 '14 at 23:44
  • Then all I've got is a wild guess: check your storage integrity. – Katherine Villyard Sep 19 '14 at 23:46
  • Does the same error occur if the backup is run manually through SSMS? – dartonw Sep 20 '14 at 12:28
  • Have you ensured that there is enough room on that drive/mount point/share? – Sean Gallardy Sep 22 '14 at 0:38
1

I should have written this long ago, but better late than never.

How did I resolve the issue? Each backup attempt created a dump file which I analyzed using WinDbg. These files indicated that the error originated in the sqlmin.dll assembly. I did a search for hotfixes for that assembly, found some, applied them, and after a reboot, the backups started working again.

For anyone who comes across weird SQL Server bugs like this, try looking at the dump files for clues.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.