SqlServerWriter missing when VSSadmin list writers command is run


In this blog, I will discuss about what to do when :

1. we run Vssadmin list writers command and sqlserverwriter is missing and 

2. Also, there is no error message in Application event logs and

3. Also, SQLserver VSS writer service is running

Here are the steps you need to follow to resolve such issues.

1. First of all we need to check if there are any spaces in the databases names. please run the query :

select ‘#’ + name +’#’  from sys.databases 

if you notice any space in database names e.g. #test  # , we need to make sure we remove the space from the database name. 

Please follow this article to rename the database name : – http://msdn.microsoft.com/en-us/library/ms345378.aspx

once you remove the space in the database name, then issue vssadmin list writers command and check if the SQLwriter is there or not

2. If still SQLwriter is not there then: 

please check the service logon which is mostly Nt authority/system or any user which you have mentioned as service logon, is added in SQL server as sysadmin privileges or not. If it’s not there then please make it as syadmin. Run the VSSadmin list writers command. 

Please feel free to post a question if the issue still persists.

Comments (9)

  1. Austin Brogle says:

    when you say a space as in #test # is it any space at all or any space directly before a '#' because all of the user profile services that sharepoint creates have spaces but its like #User Profile Service Application_ProfileDB_insertrandomstringhere#

  2. Kenneth says:

    Just wanted to add my solution. This post is old (from 2011) but i had similar problem on Windows 2012 R2 Server. I tried all abowe + other suggestions from other sites, and none eowrked. Then i decided to try some changes regarding accounts to see if it matter. The solution was very simple – I changed log in account on the SQL Server Witer Service from Local Service to administrator account. Restarted the service and then vvssadmin lis writers finnaly show the SQlSrvWriter as it should. And i can connect succesfully to SQL from Backup software.

  3. RogerP says:

    Hi Kenneth

    your trick just saved me loads of time, had the same issue on windows 2012r2 and sql express

    thanks

    Rog

  4. Eugene says:

    Thank you very much for useful article!

  5. Daniel Cimon says:

    Kenneth's recommendation solved the issue, Also on Windows 2012 R2. Running service as Administrator instead of Local System resolved the issue.

  6. Kevin O says:

    Kenneth, a million times thank you. I have this error on Server 2012 r2 with SQL express and your trick saved the day!

  7. omprakash kumar says:

    How many type of SQL writer.

    is it any error related SQL. If yes than What? Explen it

    Writer name: 'SqlServerWriter'

      Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

      Writer Instance Id: {7377f6f7-cda9-4caa-b0fe-38c1ce196740}

      State: [5] Waiting for completion

      Last error: No error

    Writer name: 'System Writer'

      Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

      Writer Instance Id: {7999ba72-10b0-416d-a53c-3c9ef1231b6a}

      State: [5] Waiting for completion

      Last error: No error

    Writer name: 'MSDEWriter'

      Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}

      Writer Instance Id: {6043d425-e0d6-45fb-8c01-6d1836fd640d}

      State: [1] Stable

      Last error: No error

    Writer name: 'Registry Writer'

      Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

      Writer Instance Id: {239523fc-4769-4804-8ba9-008b190df958}

      State: [1] Stable

      Last error: No error

    Writer name: 'Event Log Writer'

      Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}

      Writer Instance Id: {4de9453d-a5e7-40af-94b1-3e07972086c7}

      State: [1] Stable

      Last error: No error

    Writer name: 'COM+ REGDB Writer'

      Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

      Writer Instance Id: {f7a28b08-1f3b-4f75-8a65-72459fb7e634}

      State: [1] Stable

      Last error: No error

    Writer name: 'BITS Writer'

      Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

      Writer Instance Id: {cf1e6802-95f1-4e07-acf8-5baba4851c29}

      State: [1] Stable

      Last error: No error

    Writer name: 'WMI Writer'

      Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

      Writer Instance Id: {7f320133-5e19-4bfd-8566-dda00cccb4da}

      State: [5] Waiting for completion

      Last error: No error

    Writer name: 'IIS Metabase Writer'

      Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

      Writer Instance Id: {086b1960-f387-4faa-87be-e789f23f4fa6}

      State: [5] Waiting for completion

      Last error: No error

  8. AjaxOfTheRockies says:

    Kenneth;

     Thank you.  your solution solved my backup failure as well.

    – a –

  9. AjaxOfTheRockies says:

    I should add, my server is 2008 R2 running SQL 2014 Express

    – a –

Skip to main content