none
Windows Server 2012 Backup stops working on Virtual Machine with SharePoint 2013 after SQL Server 2012 is installed.

    Question

  • I have a virtual machine running Windows Server 2012 and installed Windows Server Backup.  My daily backups were working without any problems for several days.

    I then installed SharePoint 2013 and my backups continued to work without any problems for several more days.

    I then installed SQL Server 2012 and my backups immediately started failing with the error message saying:

    Detailed error: The system writer is not found in the backup.

    I then uninstalled SQL Server 2012, but I continue to get the same error.

    Any help on how I can get my backups to work again would be greatly appreciated ... Especially if this help includes figuring out a way for Windows Server 2012, SharePoint 2013 and SQL Server 2012 to work together.

    Thanks, Dean
    Thursday, September 26, 2013 10:33 PM

Answers

  • Hi,

    Please continue verify and modify any inconsistent access to the VSS registry key to see if permission settings are all correct:

    [HKLM\System\CurrentControlSet\Services\EventLog\Application\VSS]

    TrustedInstaller = FullControl
    Admin, System, Users = Read

    If any permission is edited, reboot and test backup again.

    If issue persists, in "Start search here" or in "run" type without the qoutes "dcomcnfg" and press ENTER.

    You should see the COM+ MMC after a while. Navigate to "Component Services > Computer > My computer". Right click my computer and select properties.

    In the tab "Deafult Properties" make sure that "Default authentication level" is at least set to "Connect" and "Default impersonation level" is set to at least "Identify".

    Under "COM Security" tab in "Local Launch and Activation Permissions" on you may edit the Default and Limits to allow NETWORK SERVICE and LOCAL SERVICE to allow "Local Activation" as the error messages indicates it do not have today.

    Recommend that you restart the server after modifying the access, then test Windows Server Backup.


    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

    Wednesday, October 02, 2013 8:00 AM

All replies

  • Hi,

    Copy below into a batch file and run from an elevated command prompt (or execute every line manually). 

    Takeown /f %windir%\winsxs\temp\PendingRenames /a 
    icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\temp\PendingRenames /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\temp\PendingRenames /grant BUILTIN\Users:(RX)
    Takeown /f %windir%\winsxs\filemaps\* /a 
    icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)
    icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)

    net stop cryptsvc
    net start cryptsvc

    Type the following command to verify that the system writer is now listed:
    vssadmin list writers

    If we have system writer and other listed test running a backup again using Windows Server Backup.


    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

    Friday, September 27, 2013 3:33 AM
  • Hi Shaon,

    After I execute the list of commands you noted above and then run the 'vssadmin list writers', I get the following results:

    c:\>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'SharePoint Services Writer'
       Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
       Writer Instance Id: {e9e399ca-b6b1-424c-9b53-446997d898b2}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {f96fb119-4309-4f9b-b5a4-1b95886d07d7}
       State: [1] Stable
       Last error: No error

    Writer name: 'OSearch15 VSS Writer'
       Writer Id: {0ff1ce15-0201-0000-0000-000000000000}
       Writer Instance Id: {c8ffb145-ebc9-4a41-98b9-0a0dbd73f2d2}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {333180f7-c8ff-4b3e-82f8-ae43a2972ed7}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {d81f5a9b-f810-4926-8469-5ed874bf9299}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {73a79679-54ba-43ca-9119-7b47fe47f235}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {ddfa89ed-4338-4ba2-8ff6-b8319e020f94}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {5a7668fc-d1ab-4d21-95df-267d85cd9e6a}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {0529d67e-1690-4775-a7c1-6455b6ef1bf0}
       State: [1] Stable
       Last error: No error

    The list does not show the system writer and my Backups continue to fail reporting 'The system writer is not found in the backup' ... The Event Log does not have VSS Event ID 8213.

    When the Backup fails, the Event Log has a CAPI2 Event ID 513 error reporting the following:

    Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

    Details:
    TraverseDir : Unable to push subdirectory.

    System Error:
    Unspecified error
    .


    Friday, September 27, 2013 6:09 AM
  • Hi Dean,

    were you able to fix the issue? I am having the same issue and would like to understand how I can back-up... I am kinda in trouble if I cannot:)

    Monday, September 30, 2013 10:03 PM
  • Hi,

    Please continue verify and modify any inconsistent access to the VSS registry key to see if permission settings are all correct:

    [HKLM\System\CurrentControlSet\Services\EventLog\Application\VSS]

    TrustedInstaller = FullControl
    Admin, System, Users = Read

    If any permission is edited, reboot and test backup again.

    If issue persists, in "Start search here" or in "run" type without the qoutes "dcomcnfg" and press ENTER.

    You should see the COM+ MMC after a while. Navigate to "Component Services > Computer > My computer". Right click my computer and select properties.

    In the tab "Deafult Properties" make sure that "Default authentication level" is at least set to "Connect" and "Default impersonation level" is set to at least "Identify".

    Under "COM Security" tab in "Local Launch and Activation Permissions" on you may edit the Default and Limits to allow NETWORK SERVICE and LOCAL SERVICE to allow "Local Activation" as the error messages indicates it do not have today.

    Recommend that you restart the server after modifying the access, then test Windows Server Backup.


    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

    Wednesday, October 02, 2013 8:00 AM