locked
Server backup failing because SPSearch4 VSS Writer RRS feed

  • Question

  • I have just installed Small Business Server 2011 and I installed SP1 for 2008 R2 today. I cannot succeed with Windows Server Backup Backup Once operation. This is the first time I am trying to run Server Backup.

     

    I get following error message:

     

    ------

    The backup operation that started at '‎2011‎-‎07‎-‎12T14:13:04.651000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    ------

     

    When I check from Application logs, I find following error message timestamped the same as above error message:

     

    ------

    Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.

    Operation:
       PostSnapshot Event

    Context:
       Execution Context: Writer
       Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Name: ASR Writer
       Writer Instance ID: {96058494-f42f-4134-a338-ad329f548a87}

    Error-specific details:
       Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist.
    ------

     

    When I check from Active Directory Administrative Center, I can see that account spsearch does exist. All services are up and running.

     

    When I restart server and run "vssadmin list writers" in PowerShell, there is no errors but after failed backup attempt I get error for 'SPSearch4 VSS Writer' below

     

    ------

    Writer name: 'SPSearch4 VSS Writer'
       Writer Id: {35500004-0201-0000-0000-0
       Writer Instance Id: {6d7435c2-c142-48
       State: [8] Failed
       Last error: Inconsistent shadow copy

    ------

     

    After installation of server software I havent done nothing that would influence SharePoint but that seems to be the fault why backup is not succeeding. Any help would be appreciated!!

     

    I also can see following related errors in Application log after "Search service started" Informational for SharePoint:

     

    ------

    Event 70, SharePoint Foundation Search

    The mount operation for the gatherer application 672cd3b8-3348-4f10-bc99-3a01d930e5aa has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.

    ------

    ------

    Event 6398, SharePoint Foundation

    The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID 81ad802c-2132-43d9-8ab1-1a66d3fe941e) threw an exception. More information is included below.

    The device is not ready. 

    ------

    Tuesday, July 12, 2011 4:46 PM

Answers

  • I found a similar case is our database and please have a try on steps below:

    1. Open the command prompt as administrator.
    2. Go  to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    3. Execute the following command:

    PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    After completing the above command restart the server and try to perform the backup operation again.


    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.
    • Proposed as answer by RickRoepke Tuesday, July 19, 2011 12:32 AM
    • Marked as answer by Junkelo Tuesday, July 19, 2011 8:21 PM
    Friday, July 15, 2011 9:04 AM
  • Shaon Shan got it right. Here is a link to blog post about this issue. Worked for me.

     

    http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx

    • Marked as answer by Junkelo Tuesday, July 19, 2011 8:21 PM
    Tuesday, July 19, 2011 8:21 PM
  • Hi,

    Check out this MS Article: http://technet.microsoft.com/en-us/library/ee692290(WS.10).aspx

    It addresses the same issues you are experiencing!

    Best of luck!

    Martin


    If you find my information useful, please rate it. :-)
    • Proposed as answer by Martin G. Evans Thursday, July 14, 2011 8:10 PM
    • Marked as answer by Junkelo Tuesday, July 19, 2011 8:21 PM
    Thursday, July 14, 2011 8:10 PM

All replies

  • Hi,

    Check out this MS Article: http://technet.microsoft.com/en-us/library/ee692290(WS.10).aspx

    It addresses the same issues you are experiencing!

    Best of luck!

    Martin


    If you find my information useful, please rate it. :-)
    • Proposed as answer by Martin G. Evans Thursday, July 14, 2011 8:10 PM
    • Marked as answer by Junkelo Tuesday, July 19, 2011 8:21 PM
    Thursday, July 14, 2011 8:10 PM
  • I found a similar case is our database and please have a try on steps below:

    1. Open the command prompt as administrator.
    2. Go  to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    3. Execute the following command:

    PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    After completing the above command restart the server and try to perform the backup operation again.


    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.
    • Proposed as answer by RickRoepke Tuesday, July 19, 2011 12:32 AM
    • Marked as answer by Junkelo Tuesday, July 19, 2011 8:21 PM
    Friday, July 15, 2011 9:04 AM
  • Thanks Shaon Shan!

    Worked for me!

    Monday, July 18, 2011 11:24 AM
  • SOLVED!!!!  I took Shaon Shan's suggestion after every other page had solutions cover the gauntlet of registry hacks and database checks.  This fix was easy, harmless and got my volume shadow copies running so my backups are running again.

    This fix covers the issue where "vssadmin list writers" reports Writer name: 'SPSearch4 VSS Writer' has "Last error: Inconsistent shadow copy"

    Thanks.

    Tuesday, July 19, 2011 12:35 AM
  • Shaon Shan got it right. Here is a link to blog post about this issue. Worked for me.

     

    http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx

    • Marked as answer by Junkelo Tuesday, July 19, 2011 8:21 PM
    Tuesday, July 19, 2011 8:21 PM
  • Worked for me! i´ve spended hours looking, many thanks!!
    Wednesday, September 28, 2011 5:00 PM
  • Thank you so much Shaon I spent two days with agony trying to resolve this problem. Your input is the solution. It worked for me.

    Thank you once again.

    Monday, December 5, 2011 12:09 AM
  • thx!! it works!!
    Friday, January 13, 2012 8:36 AM
  • THANK YOU! Had the same problem with DPM 2010 backups of a Sharepoint Foundation 2010 server failing..that single command did the trick!


    Keep the Funk alive!
    Saturday, January 21, 2012 1:48 PM
  • I have the same trouble-problem in SBS 2011 when performing backup to iSCSI conected disk.

     I my trying to apply Shaon Shan advice and ... Work for me. Thank you.

    Tuesday, March 20, 2012 12:14 PM
  • Shaon Shan, thank you!

    Saturday, September 15, 2012 7:53 AM
  • I am having a similar problem but i don't have the same server extension version, misne is 12

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN

    Can it be resolved with the same solution

    Thursday, November 22, 2012 7:28 PM
  • I have been fighting this error for the past 2 months!  I just posted our solution (mix of others) athttp://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/94a8bb64-e0ea-493f-8e29-01347b1fc6c7/:

    • Initially I triedhttp://support.microsoft.com/kb/2009272 but it did not help (I re-implemented later).
    • I re-registered the DLL’s as perhttp://social.technet.microsoft.com/Forums/da/winservergen/thread/b4bd0deb-45d0-4661-8c50-a2b45db41103 from NareshD. I do not believe this is necessary unless there is a corruption in the system but I am noting here just in case.
    • I tried to run The PSConfig but it was failing:I had to do the following in order to make it finish successfully:
      1. (from same page athttp://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/94a8bb64-e0ea-493f-8e29-01347b1fc6c7/) :
        On the migrated SBS2011 PSCDiagnostic Log I found no entry to detect or start the services SPWriterServiceInstance and SPTimerServiceInstance.
      2. I run once again the command „PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures“ in the “Bin” Folder as an administrator console session.
      3. In the moment I saw the status “Configuration task 5 of 6 is executed” I start to run the command “net start SPTraceV4 & net start SPWriterV4 & net start SPAdminV4 & net start SPSearch4 & net start SPTimerV4” ina parallel administrator console sessionand after that, the configuration task finished successfully.  (I just opened another cmd window and copy/paste the sequence below when I saw the status “Configuration Task x of y” on the screen:
        net start SPTraceV4
        net start SPWriterV4
        net start SPAdminV4
        net start SPSearch4
        net start SPTimerV4
        -Note SPSearch4 is disabled in our system…
        Very awkward but it worked…
    • I implementedhttp://support.microsoft.com/kb/2009272 again.
    • Backup started working with no errors.

    Constantine

    • Proposed as answer by DinoAIM Monday, May 20, 2013 12:07 AM
    Saturday, December 15, 2012 4:59 PM
  • I applied this command and the upgrade fails. Any ideas?

    PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    Saturday, May 3, 2014 12:47 AM
  • did you try the above solution?  It still works for me... 

    Open a CMD window as an administrator

    run the command "PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures“ in the “Bin” Folder.

    • Open a second CMD window as an administrator.
    • In the moment you see the status “Configuration task 5 of 6 is executed” start to run the command (on the 2nd CMD window, just copy / Paste the below commands)
    • net start SPTraceV4
    • net start SPWriterV4
    • net start SPAdminV4
    • net start SPSearch4
    • net start SPTimerV4
    • After that, the configuration task finishes successfully. 

    • Very awkward but it works for me…  I have to do this every time my backup fails and then the backup finishes successfully...


    Constantine

    Saturday, May 3, 2014 1:10 AM
  • I faced a similar issue where the output of the command: 'vssadmin list writers' displayed the following output:

    Writer name: 'OSearch14 VSS Writer'

    Last error: Inconsistent shadow copy

    The SharePoint server was a VMware VM with the SharePoint search component running, and whenever we attempted to take a snapshot of the VM with the 'Quiesce' option selected , the snapshot operation would fail, and the event log would display the following error in the 'Application' event log:

    VMware Tools Warning "[ warning] [vmvss:vmvss] CVmSnapshotRequestor::CheckWriterStatus():1536: writer OSearch14 VSS Writer in failed state: res = 0x800423f0, err = 0x1, error =

    It looks like the error occurred when the 'OSearch14 VSS Writer' was attempting to quiesce the search-related files prior to the snapshot being taken. It turns out that the search files were being stored on an iSCSI LUN on our SAN, and apparently the snapshot operation fails because the OSearch VSS Writer cannot create a shadow copy on the remote LUN. Also, per VMware's documentation, we found that snapshots are not supported for VMs that contain iSCSI LUNs : http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc_50%2FGUID-53F65726-A23B-4CF0-A7D5-48E584B88613.html

    Quote from above link : "VMware does not support snapshots of raw disks, RDM physical mode disks, or guest operating systems that use an iSCSI initiator in the guest."

    As a workaround, we disabled the 'OSearch VSS Writer' in the VM using these instructions, and then the error went away: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031200


    Monday, September 8, 2014 4:58 PM