/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Backup Configure

SQL VSS Writer Not Listed, Backups Failing

SUMMARY

ISSUE

Applies To

SQL Server and MSDE

If the database names are fine, check that SYSADMIN is a member of NT AUTHORITY\SYSTEM. If not, add SYSADMIN to SYSTEM, and restart the SQL Server VSS Writer Service. The SqlServerWriter should now be listed in Stable/No-Error in vssadmin list writers. Run a test backup to make sure everything is functioning.

Source: http://blogs.msdn.com/b/batala/archive/2011/08/01/sqlserverwriter-missing-when-vssadmin-list-writers-command-is-run.aspx

SQL server will fail with error 0x08000ffff or an unknown error. Typically SQL was working before and it will happen all of the sudden.

RESOLUTION

To Resolve the SQL VSS writer from disappearing you would have to remove or rename the database to something without spaces understand if you have do not remove the “ “(space) the VSS writer will stay in a hidden and failed state Until otherwise.

This query may help find databases with the leading or trailing “ “ white space.

select '#' + name +'#' from sys.databases

Third-Party Sources

http://support.microsoft.com/kb/919023/en-us

CAUSE

SQL database do not work with a trailing “ “ space or with a space in conjunction with a “ “ space for example if I had a database named “My Big Database” or “MYBIGDATABASE “ the SQL VSS writer would not be there.

NOTES

For more detailed information on backup failures and performance issues see Unitrends KB 5062 - Backup Failures and Performance Issues