none
SBS 2011: VSS 8230 errors relating to Sharepoint search

    Question

  • Hi all,

    Anyone else seen errors in their event log relating to VSS and the Sharepoint search user?  I was getting these errors before installing the Sharepoint 2010 updates, although I did get hit by the incorrect perms on the Sharepoint logs folder as well.

    Here is the error I am getting quite frequently in the log:

    Log Name:      Application
    Source:        VSS
    Date:          09/01/2011 23:51:48
    Event ID:      8230
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      ELROND.hodgsonfamily.org
    Description:
    Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.

    Operation:
       Initializing Writer

    Context:
       Writer Class Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Name: BITS Writer

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

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="VSS" />
        <EventID Qualifiers="0">8230</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-01-09T23:51:48.000000000Z" />
        <EventRecordID>5183</EventRecordID>
        <Channel>Application</Channel>
        <Computer>MACHINE.domain.org</Computer>
        <Security />
      </System>
      <EventData>
        <Data>spsearch</Data>
        <Data>1376</Data>
        <Data>

    Operation:
       Initializing Writer

    Context:
       Writer Class Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Name: BITS Writer

    Error-specific details:
       Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist.
    </Data>
        <Binary>2D20436F64653A20534543534543524330303030313937322D2043616C6C3A20534543534543524330303030313735362D205049443A202030303030303930382D205449443A202030303030363439362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B206E6574737663732020202020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
      </EventData>
    </Event>

    Thanks.

    Andrew.

    Sunday, January 9, 2011 11:59 PM

Answers

  • not yet published:
     2483007             Windows SBS 2011 Known Post Installation Event Log
    Errors and Warnings
     
     
    SUMMARY
     
    This article lists the known Post Installation Event Errors that may
    occur on Windows Small Business Server 2011.
     
    MORE INFORMATION
     
    Known Post Installation Errors and Warnings
     
    Problem: The following errors may be reported in the application event log:
     
    Source: Microsoft-SharePoint Products-SharePoint Foundation
    EventID: 6772
    Message: There was an internal error invoking the timer job
    '{6486B72C-3B64-44D3-8117-1E48A4A1E4B8}' for service
    '{3099C545-3246-44A6-A610-C95D350C64D3}
     
    Source: Microsoft-SharePoint Products-SharePoint Foundation
    EventID: 6398
    Message: The Execute method of job definition
    Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID
    67371ad5-7be6-42ba-8b9b-30ae9c54d935) threw an exception. More
    information is included below. Timeout expired. The timeout period
    elapsed prior to completion of the operation or the server is not responding
     
    Resolution: The errors are benign and may be safely ignored.
     
    Problem: The following error may be reported in the system event log:
     
    Source: Microsoft-Windows-DistributedCOM
    EventID: 10016
    Message: The application-specific permission settings do not grant Local
    Activation permission for the COM Server application with CLSID
    {61738644-F196-11D0-9953-00C04FD919C1} and APPID
    {61738644-F196-11D0-9953-00C04FD919C1} to the user CONTOSO\spfarm SID
    (S-1-5-21-1860903272-1458820992-1399837422-1157) from address LocalHost
    (Using LRPC). This security permission can be modified using the
    Component Services administrative tool.
     Cause: This issue occurs because the account that is configured as the
    Windows SharePoint Services service account does not have the Local
    Activation permission to the IIS Wamreg Admin Service. The event ID
    error message 10016 does not affect the functionality of Windows
    SharePoint Services.
     
    Resolution: You can safely ignore the event ID error message 10016 that
    is logged in the System log. If you want to prevent the event ID error
    message from being logged in the System log, use the Component Services
    snap-in to enable the Local Activation permission to the IIS Wamreg
    Admin Service for the spfarm account. On Windows Small Business Server
    2011, the administrator account doesn't have permissions by default to
    modify the IIS Wamreg Admin Service.
     
    You must first use the following steps to modify the permissions:
     Important This article contains information about how to modify the
    registry. Make sure that you back up the registry before you modify it.
    Make sure that you know how to restore the registry if a problem occurs.
    For more information about how to back up, restore, and modify the
    registry, click the following article number to view the article in the
    Microsoft Knowledge Base:
     
    322756 How to back up and restore the registry in Windows
     
    1.
     
    Click Start , click Run , type Regedit on the Open box, and then click OK .
     
    2.
     
    Navigate to the following registry key:
    HKEY_CLASSES_ROOT\AppID\{61738644-F196-11D0-9953-00C04FD919C1}
     
    3.
     
    Right click on the key {61738644-F196-11D0-9953-00C04FD919C1} and choose
    permissions
     
    4.
     
    Grant the Administrators group Full Control
     
    5.
     
    Close Regedit
     
    Use the following steps to grant the SPFARM account the local activation
    right.
     
    1.
     
    Click  Start , click  Run , type dcomcnfg in the  Open  box, and then
    click  OK .
     
    2.
     
    Expand  Component Services , expand  Computers , expand  My Computer ,
    and then click  DCOM Config .
     
    3.
     
    Right-click  IIS WAMREG admin Service , and then click  Properties .
     
    4.
     
    Click the  Security  tab.
     
    5.
     
    Under  Launch and Activation Permissions , click  Edit .
     
    6.
     
    Click on the SharePoint Farm Account and check the box for Local
    Activation .
     
    7.
     
    Click OK and close out of the Component Services Utility.
     Problem: The following error may be recorded in the MSExchange
    Management event log every 30 minutes
     
    Log Name:      MSExchange Management
    Source:        MSExchange CmdletLogs
    Date:          12/22/2010 8:00:13 AM
    Event ID:      6
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      CONTOSOSERVER.contoso.local
    Description:
    Cmdlet failed. Cmdlet Get-User, parameters {Identity=NT AUTHORITY\SYSTEM}.
     
    Cause: The error is generated by the Small Business Server
    datacollectorservice. When the datacollectorservice runs Exchange
    related tasks a check is performed to determine whether or not the
    current user is an Exchange admin and mail-enabled. The
    datacollectorservice runs under the context of the local system check so
    the check fails and the error is generated.
     
    Resolution: The error is benign and may be safely ignored.
     
    Problem: The following warnings may be reported in the application event
    log.
     
    Log Name:      Application
    Source:        VSS
    Date:          12/22/2010 9:00:03 AM
    Event ID:      8230
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      CONTOSOSERVER.contoso.local
    Description:
    Volume Shadow Copy Service error: Failed resolving account spsearch with
    status 1376. Check connection to domain controller and VssAccessControl
    registry key. Error-specific details:
       Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified
    local group does not exist.
     
    Log Name:      Application
    Source:        VSS
    Date:          12/22/2010 9:00:03 AM
    Event ID:      8230
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      CONTOSOSERVER.contoso.local
    Description:
    Volume Shadow Copy Service error: Failed resolving account spsearch with
    status 1376. Check connection to domain controller and VssAccessControl
    registry key. Operation:
       Gathering Writer Data
       Executing Asynchronous OperationContext:
       Execution Context: Requestor
       Current State: GatherWriterMetadataError-specific details:
       Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified
    local group does not exist.
     
    Cause: The warnings occur because the Sharepoint VSS writer and search
    services run under the context of a domain user account.
     
    Resolution: The warnings are benign and can be safely ignored.
     
    On 1/9/2011 3:59 PM, adhodgson wrote:
    > Hi all,
    >
    > Anyone else seen errors in their event log relating to VSS and the
    > Sharepoint search user? I was getting these errors before installing the
    > Sharepoint 2010 updates, although I did get hit by the incorrect perms
    > on the Sharepoint logs folder as well.
    >
    > Here is the error I am getting quite frequently in the log:
    >
    > Log Name: Application
    > Source: VSS
    > Date: 09/01/2011 23:51:48
    > Event ID: 8230
    > Task Category: None
    > Level: Warning
    > Keywords: Classic
    > User: N/A
    > Computer: ELROND.hodgsonfamily.org
    > Description:
    > Volume Shadow Copy Service error: Failed resolving account spsearch with
    > status 1376. Check connection to domain controller and VssAccessControl
    > registry key.
    >
    > Operation:
    > Initializing Writer
    >
    > Context:
    > Writer Class Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    > Writer Name: BITS Writer
    >
    > Error-specific details:
    > Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified
    > local group does not exist.
    >
    > Event Xml:
    > <System>
    > <Provider Name="VSS" />
    > <EventID Qualifiers="0">8230</EventID>
    > <Level>3</Level>
    > <Task>0</Task>
    > <Keywords>0x80000000000000</Keywords>
    > <TimeCreated SystemTime="2011-01-09T23:51:48.000000000Z" />
    > <EventRecordID>5183</EventRecordID>
    > <Channel>Application</Channel>
    > <Computer>MACHINE.domain.org</Computer>
    > <Security />
    > </System>
    > <EventData>
    > <Data>spsearch</Data>
    > <Data>1376</Data>
    > <Data>
    >
    > Operation:
    > Initializing Writer
    >
    > Context:
    > Writer Class Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    > Writer Name: BITS Writer
    >
    > Error-specific details:
    > Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified
    > local group does not exist.
    > </Data>
    > <Binary>2D20436F64653A20534543534543524330303030313937322D2043616C6C3A20534543534543524330303030313735362D205049443A202030303030303930382D205449443A202030303030363439362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B206E6574737663732020202020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
    > </EventData>
    > </Event>
    >
    > Thanks.
    >
    > Andrew.
    >
     
     
    Monday, January 10, 2011 5:01 AM
    Moderator

All replies

  • not yet published:
     2483007             Windows SBS 2011 Known Post Installation Event Log
    Errors and Warnings
     
     
    SUMMARY
     
    This article lists the known Post Installation Event Errors that may
    occur on Windows Small Business Server 2011.
     
    MORE INFORMATION
     
    Known Post Installation Errors and Warnings
     
    Problem: The following errors may be reported in the application event log:
     
    Source: Microsoft-SharePoint Products-SharePoint Foundation
    EventID: 6772
    Message: There was an internal error invoking the timer job
    '{6486B72C-3B64-44D3-8117-1E48A4A1E4B8}' for service
    '{3099C545-3246-44A6-A610-C95D350C64D3}
     
    Source: Microsoft-SharePoint Products-SharePoint Foundation
    EventID: 6398
    Message: The Execute method of job definition
    Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID
    67371ad5-7be6-42ba-8b9b-30ae9c54d935) threw an exception. More
    information is included below. Timeout expired. The timeout period
    elapsed prior to completion of the operation or the server is not responding
     
    Resolution: The errors are benign and may be safely ignored.
     
    Problem: The following error may be reported in the system event log:
     
    Source: Microsoft-Windows-DistributedCOM
    EventID: 10016
    Message: The application-specific permission settings do not grant Local
    Activation permission for the COM Server application with CLSID
    {61738644-F196-11D0-9953-00C04FD919C1} and APPID
    {61738644-F196-11D0-9953-00C04FD919C1} to the user CONTOSO\spfarm SID
    (S-1-5-21-1860903272-1458820992-1399837422-1157) from address LocalHost
    (Using LRPC). This security permission can be modified using the
    Component Services administrative tool.
     Cause: This issue occurs because the account that is configured as the
    Windows SharePoint Services service account does not have the Local
    Activation permission to the IIS Wamreg Admin Service. The event ID
    error message 10016 does not affect the functionality of Windows
    SharePoint Services.
     
    Resolution: You can safely ignore the event ID error message 10016 that
    is logged in the System log. If you want to prevent the event ID error
    message from being logged in the System log, use the Component Services
    snap-in to enable the Local Activation permission to the IIS Wamreg
    Admin Service for the spfarm account. On Windows Small Business Server
    2011, the administrator account doesn't have permissions by default to
    modify the IIS Wamreg Admin Service.
     
    You must first use the following steps to modify the permissions:
     Important This article contains information about how to modify the
    registry. Make sure that you back up the registry before you modify it.
    Make sure that you know how to restore the registry if a problem occurs.
    For more information about how to back up, restore, and modify the
    registry, click the following article number to view the article in the
    Microsoft Knowledge Base:
     
    322756 How to back up and restore the registry in Windows
     
    1.
     
    Click Start , click Run , type Regedit on the Open box, and then click OK .
     
    2.
     
    Navigate to the following registry key:
    HKEY_CLASSES_ROOT\AppID\{61738644-F196-11D0-9953-00C04FD919C1}
     
    3.
     
    Right click on the key {61738644-F196-11D0-9953-00C04FD919C1} and choose
    permissions
     
    4.
     
    Grant the Administrators group Full Control
     
    5.
     
    Close Regedit
     
    Use the following steps to grant the SPFARM account the local activation
    right.
     
    1.
     
    Click  Start , click  Run , type dcomcnfg in the  Open  box, and then
    click  OK .
     
    2.
     
    Expand  Component Services , expand  Computers , expand  My Computer ,
    and then click  DCOM Config .
     
    3.
     
    Right-click  IIS WAMREG admin Service , and then click  Properties .
     
    4.
     
    Click the  Security  tab.
     
    5.
     
    Under  Launch and Activation Permissions , click  Edit .
     
    6.
     
    Click on the SharePoint Farm Account and check the box for Local
    Activation .
     
    7.
     
    Click OK and close out of the Component Services Utility.
     Problem: The following error may be recorded in the MSExchange
    Management event log every 30 minutes
     
    Log Name:      MSExchange Management
    Source:        MSExchange CmdletLogs
    Date:          12/22/2010 8:00:13 AM
    Event ID:      6
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      CONTOSOSERVER.contoso.local
    Description:
    Cmdlet failed. Cmdlet Get-User, parameters {Identity=NT AUTHORITY\SYSTEM}.
     
    Cause: The error is generated by the Small Business Server
    datacollectorservice. When the datacollectorservice runs Exchange
    related tasks a check is performed to determine whether or not the
    current user is an Exchange admin and mail-enabled. The
    datacollectorservice runs under the context of the local system check so
    the check fails and the error is generated.
     
    Resolution: The error is benign and may be safely ignored.
     
    Problem: The following warnings may be reported in the application event
    log.
     
    Log Name:      Application
    Source:        VSS
    Date:          12/22/2010 9:00:03 AM
    Event ID:      8230
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      CONTOSOSERVER.contoso.local
    Description:
    Volume Shadow Copy Service error: Failed resolving account spsearch with
    status 1376. Check connection to domain controller and VssAccessControl
    registry key. Error-specific details:
       Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified
    local group does not exist.
     
    Log Name:      Application
    Source:        VSS
    Date:          12/22/2010 9:00:03 AM
    Event ID:      8230
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      CONTOSOSERVER.contoso.local
    Description:
    Volume Shadow Copy Service error: Failed resolving account spsearch with
    status 1376. Check connection to domain controller and VssAccessControl
    registry key. Operation:
       Gathering Writer Data
       Executing Asynchronous OperationContext:
       Execution Context: Requestor
       Current State: GatherWriterMetadataError-specific details:
       Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified
    local group does not exist.
     
    Cause: The warnings occur because the Sharepoint VSS writer and search
    services run under the context of a domain user account.
     
    Resolution: The warnings are benign and can be safely ignored.
     
    On 1/9/2011 3:59 PM, adhodgson wrote:
    > Hi all,
    >
    > Anyone else seen errors in their event log relating to VSS and the
    > Sharepoint search user? I was getting these errors before installing the
    > Sharepoint 2010 updates, although I did get hit by the incorrect perms
    > on the Sharepoint logs folder as well.
    >
    > Here is the error I am getting quite frequently in the log:
    >
    > Log Name: Application
    > Source: VSS
    > Date: 09/01/2011 23:51:48
    > Event ID: 8230
    > Task Category: None
    > Level: Warning
    > Keywords: Classic
    > User: N/A
    > Computer: ELROND.hodgsonfamily.org
    > Description:
    > Volume Shadow Copy Service error: Failed resolving account spsearch with
    > status 1376. Check connection to domain controller and VssAccessControl
    > registry key.
    >
    > Operation:
    > Initializing Writer
    >
    > Context:
    > Writer Class Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    > Writer Name: BITS Writer
    >
    > Error-specific details:
    > Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified
    > local group does not exist.
    >
    > Event Xml:
    > <System>
    > <Provider Name="VSS" />
    > <EventID Qualifiers="0">8230</EventID>
    > <Level>3</Level>
    > <Task>0</Task>
    > <Keywords>0x80000000000000</Keywords>
    > <TimeCreated SystemTime="2011-01-09T23:51:48.000000000Z" />
    > <EventRecordID>5183</EventRecordID>
    > <Channel>Application</Channel>
    > <Computer>MACHINE.domain.org</Computer>
    > <Security />
    > </System>
    > <EventData>
    > <Data>spsearch</Data>
    > <Data>1376</Data>
    > <Data>
    >
    > Operation:
    > Initializing Writer
    >
    > Context:
    > Writer Class Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    > Writer Name: BITS Writer
    >
    > Error-specific details:
    > Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified
    > local group does not exist.
    > </Data>
    > <Binary>2D20436F64653A20534543534543524330303030313937322D2043616C6C3A20534543534543524330303030313735362D205049443A202030303030303930382D205449443A202030303030363439362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B206E6574737663732020202020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
    > </EventData>
    > </Event>
    >
    > Thanks.
    >
    > Andrew.
    >
     
     
    Monday, January 10, 2011 5:01 AM
    Moderator
  • I'm receiving an error on applying the registry security setting, it tells me the I do not have the rights to do so

    (using domain admin rights)

    Wednesday, March 2, 2011 5:20 PM
  • Did you run regedit with elevated rights according to UAC ?

    -- Hrvoje Kusulja

     

    edit:

    same thing, i have checked with UAC.

    Same for me: SBS 2011, with server 2008 R2 SP1 and all updates till today 2011/03/03 .

    I am logged as network administrator (part of enterprise admins, domain admins, administrators...) account with elevated privileges.

    And i can not modify permissions to {61738644-F196-11D0-9953-00C04FD919C

     

    how to accomplish this?

    Thank you

    Thursday, March 3, 2011 4:11 PM
  • after modifying registry as suggested now i get:

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

    {61738644-F196-11D0-9953-00C04FD919C1}

    and APPID

    {61738644-F196-11D0-9953-00C04FD919C1}

    to the user REACHMEDIAGROUP\spfarm SID (S-1-5-21-3959586900-1704243720-3424344761-1157) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

     

    Also i have always:

    The Execute method of job definition Microsoft.SharePoint.Administration.SPUsageImportJobDefinition (ID 966c360d-0944-4b7c-9377-8c9c292f18b6) threw an exception. More information is included below.

    Access to the path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS' is denied.

     


    -- Hrvoje Kusulja
    Tuesday, March 22, 2011 10:28 AM
  • Hello,

    I also have several of the listed error messages in my newly installed SBS2011.

    The hint under most of them that they are "benign" is a bit strange I think.

    If everything really is fine, then why do all these pop up?

    Does anyone know, if MS planes to publish some fixes to reach a more or less "clean" eventlog?

     

    Regards

    Stefan

     

    Monday, June 13, 2011 9:28 PM
  • I am having the problem too,  and it seems that every fix causes another problem, very frustrated.  Is there a definitive answer because I need the multiple backups so I can have one offsite.  (The VSS issue causes problems with Server Backup)
    Monday, August 29, 2011 4:27 PM
  • Is there any resolution for this problem.  It's very frustrating cause my log is littered with this warning and I am not comfortable with just leaving it as is
    Thursday, September 8, 2011 2:22 PM
  • Same situation here. Don't have permission to edit the specified registry key
    Wednesday, September 28, 2011 2:43 AM
  • Read the underlying KB

    1. Click Start, click Run, type Regedit on the Open box, and then click OK.
    2. Navigate to the following registry key: HKEY_CLASSES_ROOT\AppID\{61738644-F196-11D0-9953-00C04FD919C1}
    3. Right click on the key {61738644-F196-11D0-9953-00C04FD919C1} and choose permissions
    4. Click Advanced button
    5. Change to the Owner Tab
    6. Change the Owner to the Administrators Group be sure to check the box labeled “Replace owner on subcontainers and objects
    7. Once the Owner is changed, go back to the security tab and Grant the Administrators group Full Control
    8. Close Regedit
    • Proposed as answer by Codewize Wednesday, September 28, 2011 5:08 AM
    Wednesday, September 28, 2011 2:52 AM
    Moderator
  • Thank you, that worked, of course. I saw the owner was set to the user Administrator, which we know goes away after the first login.

     

    You know, I've been experiencing these types of bogus permission issues with SharePoint updates since early releases of SBS 2008. You'd think by now, we could run a SharePoint update without breaking things.

    • Edited by Codewize Wednesday, September 28, 2011 5:08 AM
    Wednesday, September 28, 2011 4:59 AM
  • Nope, mine was already set to Administrators, and the warnings are popping like crazy, any other suggestions
    Tuesday, October 4, 2011 1:42 AM
  • Nope, mine was already set to Administrators, and the warnings are popping like crazy, any other suggestions

    So yours is set to the Administrators Group, Full Control and the Administrators Group is the owner of the key? Please double check that, and remove Administrator from the securities listings.
    • Edited by Codewize Tuesday, October 4, 2011 4:11 AM
    Tuesday, October 4, 2011 4:10 AM
  • Thursday, October 6, 2011 10:34 PM
  • Thursday, October 6, 2011 10:39 PM
  • no change, and if i try to add an additional backup drive to the backup schedule, I will get an error on configuration.  And it's all leading back to these sharepoint accounts that have been inserted by Microsoft and don't have the appropriate permissions assigned to them.  Very Frustrating and the client is frustrated.
    Thursday, October 6, 2011 10:42 PM
  • The additional backup drive is not related to this and is a native to Server 2008 r2 backup.

    http://blog.mpecsinc.ca/2011/06/sbs-2011-backup-error-add-destination.html

    Thursday, October 6, 2011 10:44 PM
    Moderator
  • Once the Owner is changed, go back to the security tab and Grant the Administrators group Full Control

    Go back to those steps and redo that setting.  Take it out, put it back in.

    Then did you do the second part?

    Use the following steps to grant the SPFARM account the local activation right.

    1. Click Start, click Run, type dcomcnfg in the Open box, and then click OK.
    2. Expand Component Services, expand Computers, expand My Computer, and then click DCOM Config.
    3. Right-click IIS WAMREG admin Service, and then click Properties.
    4. Click the Security tab.
    5. Under Launch and Activation Permissions, click Edit.
    6. Click on the SharePoint Farm Account and check the box for Local Activation.
    7. Click OK and close out of the Component Services Utility.
    Thursday, October 6, 2011 10:46 PM
    Moderator
  • Did anyone happen to notice that the command NetLocalGroupGetMemebers(spsearch) has been misspelled. it should read NetLocalGroupGetMembers(spsearch).

    Might that be the reason the call fails rather than the password or the security settings????

    Friday, October 28, 2011 4:11 PM
  • No, (as I understand it) as there's no code triggering that, it's the account in the registry.  You can see that mispelling in other events.   

    Friday, October 28, 2011 4:20 PM
    Moderator
  • I applied the registry and DCOM config changes referenced here, but I still can't run a Windows backup job successfully. Before the job fails, it's preceded with several VSS 8230 app errors:

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

    Error-specific details:

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

    Here's the specific backup job event log failure:

    The backup operation that started at '‎2011‎-‎10‎-‎30T18:18:18.170815800Z' has failed with following error code '2155348010' (One of the backup files could not be created.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    I've run psconfig ... twice ... once before applying these changes and once after.

    It's a new server install I did this weekend for a client. Everything works great except the built-in Windows image backup job. It's my first SBS11 install, so I thought I'd post something. I've probably done 50-60 SBS installs over the years, so I'm sure I'm not the only one who will run into this problem.

    If you have any suggestions, feel free to post them here. In the mean time, I'll read through the full SBS11 post install KB article while I'm on hold with MS opening a support case.

    Thanks,

    JD

    Sunday, October 30, 2011 6:57 PM
  • It looks like the ext HDDs are my problem. Even though Windows 08 R2 successfully recognizes and can write manual system state backups to them, I can't run a full backup of both server volumes. The client had a pair of 3TB ext HDDs onsite, so I'll replace them with 2TB devices that meet the hardware requirements in the following KB article. I suspected the ext HDD size may have been a factor, since I went through something like this (imaging servers) about six months ago with Acronis -- which also doesn't support ext HDDs larger than 2TB.

    In my case the ext HDDs reported the following: Bytes Per Sector = 4096, Bytes per Physical Sector = 4096

    Anyway, if you're having problems running SBS11 Windows backups on ext HDDs make sure the following doesn't apply.

    http://support.microsoft.com/kb/2510009

    JD

     

    Sunday, October 30, 2011 9:35 PM
  • I tried the above fixes with Registry.   Want not able to change permission.   What I Did was update the share point and that fixed the problem with my backup that was not working.   Shadow drive issue.
    Tuesday, May 22, 2012 7:13 AM
  • We get the same errors, on our Windows server 2008 R2 Datacenter when backing up...

    We dont have Sharepoint, and it is not a Domain controler.

    Thursday, August 30, 2012 10:07 AM
  • We get the same errors, on our Windows server 2008 R2 Datacenter when backing up...

    We dont have Sharepoint, and it is not a Domain controler.


    Check the sector size on your backup hard drive.  Server 2008 backup does not work with the newer advanced format drives with the 4096 sized sectors.  If you have a drive that let's you format to 512 sectors, then it can be made to work.  Otherwise, you will have to find a different external hard drive!
    Saturday, October 13, 2012 6:28 AM
  • Bit rum that they can't fix misspellings if they do exist....
    Tuesday, June 10, 2014 12:07 PM
  • I tried the above fixes with Registry.   Want not able to change permission.   What I Did was update the share point and that fixed the problem with my backup that was not working.   Shadow drive issue.
    Which update did you install for SharePoint? We have that issue on a SBS 2011. The Backup is reporting not enough disk space but we have around 650GB to backup to a empty 1TB USB drive...
    Wednesday, June 24, 2015 9:05 PM
  • We get the same errors, on our Windows server 2008 R2 Datacenter when backing up...

    We dont have Sharepoint, and it is not a Domain controler.


    Check the sector size on your backup hard drive.  Server 2008 backup does not work with the newer advanced format drives with the 4096 sized sectors.  If you have a drive that let's you format to 512 sectors, then it can be made to work.  Otherwise, you will have to find a different external hard drive!

    Resolution 

    1. Go to Event Viewer
    2. Filter Application logs by Backup category
    3. If you see a recent entry showing Error 521 - The backup operation that started at '‎2014‎-‎04‎-‎29T00:00:11.180000000Z' 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.  continue the following steps
    4. Launch an elevated SharePoint 2010 Management shell
    5. Run (get-spserver $env:computername).NeedsUpgrade
    6. If the above returns True continue the following steps
    7. Launch an elevated cmd prompt
    8. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    9. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
    10. Ensure all stages complete successfully
    11. Launch an elevated SharePoint 2010 Management shell (or use current open window)
    12. Run (get-spserver $env:computername).NeedsUpgrade
    13. If command returns False, continue the following steps
    14. Reboot server
    15. Run backup

    Further notes

    1. If you receive an error stating Backup unsuccessful. A Volume Shadow Copy Service operation failed. Unknown error (0x800423f0), OK the message and check status of backup - if "In progress" allow to complete and re-check results.

    Wednesday, June 24, 2015 9:19 PM