none
DPM 2010 SharePoint 2010 farm level backup error with event id 32008 RRS feed

  • Question

  • Hi to everyone;

    I'm newbie in DPM . We want to take backup Sharepoint 2010 with DPM 2010 but we take event id 32008. Our sharepoint farm is distributed on front-end,backend they are in virtual machine and their databases located on SQL 2008 R2 on a physical server.

    First of all I installed agent all of the machine in our farm successfully.Then I apply  

    •        ConfigureSharepoint.exe –enableSharepointProtection
    •        ConfigureSharepoint.exe EnableSPSearchProtection  

    When creating protection group on DPM it saw SharePoint as a Role but when I extend the schema it shows

     

    "dpm cannot protect this sharepoint farm as it cannot detect the configuration of the dependent SQL databases"

    I looked at VSS service on front-end server is automatically started and log on account is a local administrator, SQL VSS service also started

    Unfortunately I dont solve this problem.

     

    Best regards ;

    Friday, December 23, 2011 3:17 PM

All replies

  • Hi Natralli,

    Did you run the ConfigureSharePoint on all Front End Servers or in only one?

    Which SharePoint version (build) are you running (example: 14.0.5128.5000)


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, December 28, 2011 7:59 AM
    Moderator
  • Hi Natralli,

    Did you run the ConfigureSharePoint on all Front End Servers or in only one?

    Which SharePoint version (build) are you running (example: 14.0.5128.5000)


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights

    I got the same problem,

    Has anyone a solution?

    Tnx

    Wednesday, December 28, 2011 3:23 PM
  • Hi Vally,

    Which SharePoint Version are you running?

    Did you run Configuresharepoint -enablesharepoint protection on all WFE server?

    Are you using SQL alias From your SharePoint to connect to the backend SQL server?

    Do you have any SharePoint database being already protected by DPM as SQL Data sources?


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, December 28, 2011 5:46 PM
    Moderator
  • Hi Vally,

    Which SharePoint Version are you running?

    Did you run Configuresharepoint -enablesharepoint protection on all WFE server?

    Are you using SQL alias From your SharePoint to connect to the backend SQL server?

    Do you have any SharePoint database being already protected by DPM as SQL Data sources?


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights

    Hi Wilson We use Sharepoint 2010 our farm has one WFE server we dont use sql alias and does not configure any protection on DPM for SQL databases.I think we resolve this problem by applying this step.First SQL name has to be fqdn second for dpm agent installation by logging farm admin account and run configuresharepoint.exe commands.I made this step in test environment and successfully seen sharepoint role in dpm.

    But we encountered another problem.At first we run configuresharepoint.exe commands and installation successfully,sometimes later try to resolve above problem our sharepoint vss writer service has not seen anymore when execute vss admin list writers command I try everything to register to vss admin list but I failed.Is there anyway to register it by stsadm -o unregister

     

    Thanks.

    Thursday, January 12, 2012 12:40 PM
  • So the Sharepoint VSS Writer isn't showing up?

    What is the current state of SharePoint 2010 VSS Writer service (disabled/automatic) and it is set to run with which account?


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Friday, January 13, 2012 12:42 AM
    Moderator
  • So the Sharepoint VSS Writer isn't showing up?

    What is the current state of SharePoint 2010 VSS Writer service (disabled/automatic) and it is set to run with which account?


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Hi Wilson;Sharepoint 2010 VSS writer service is automatic and is using farm admin account.
    Monday, January 16, 2012 2:47 PM
  • Which SharePoint build are you using?
    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Monday, January 16, 2012 7:28 PM
    Moderator
  • Which SharePoint build are you using?
    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Sharepoint 2010
    Tuesday, January 17, 2012 11:08 AM
  • I am looking for the SharePoint update level

    http://todd-carter.com/page/SharePointVersions.aspx


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, January 17, 2012 11:12 AM
    Moderator
  • I am looking for the SharePoint update level

    http://todd-carter.com/page/SharePointVersions.aspx


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights

    Our sharepoint product version is SP1 (14.0.6029.1000)

     

    Thanks for your help

    Tuesday, January 17, 2012 2:32 PM
  • Thanks for the update.

    So currently you are still not able to create protection. The error you are getting still the same as you posted when first opened this thread, correct?

    What happens if you try to protect all SharePoint DBs as a SQL datasource (this isn't a workaround/resolution) but just to check if all SharePoint DBs can be protected.


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, January 17, 2012 6:45 PM
    Moderator
  • Thanks for the update.

    So currently you are still not able to create protection. The error you are getting still the same as you posted when first opened this thread, correct?

    What happens if you try to protect all SharePoint DBs as a SQL datasource (this isn't a workaround/resolution) but just to check if all SharePoint DBs can be protected.


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights

    Hi again;

    In my first post we saw protection group with Sharepoint role but when choosing Sharepoint role it gave error with id 32008.Then we changed Sharepoint 2010 vss service account from farm admin account to local System.After that we realized this is not a true case so we change the service account to farm admin account.At now sharepoint vss writer has not been listed when execute vss admin list writer so that in dpm console we cant see Sharepoint role even sharepoint 2010 Vss writer service is started and automatic status and log on account is farm admin account.

    At now we protect Sql data with database protection and it works but still sharepoint role protection doesnt work.

     

    Best Regards...

    Wednesday, January 18, 2012 9:21 AM
  • This can happen if the user account you are using doesn't have permission on the SQL Server or if the SQL Server is unaccessible from that server.

    After you run stsadm -o unregisterwsswriter, go to Application log and see if there is any SharePoint error event there.

     


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, January 18, 2012 6:24 PM
    Moderator
  • Hi Wilson as you say some error log in front end web server in below

     

    Log Name:      Application
    Source:        VSS
    Date:         /////////
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ***************
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine RegSetValueExW(0x00000104,SYSTEM\CurrentControlSet\Services\VSS\Diag\SharePoint Services Writer,0,REG_BINARY,00000000223ECE10.72).  hr = 0x800703fa, Illegal operation attempted on a registry key that has been marked for deletion.
    .

    Operation:
       Gathering Writer Data

    Context:
       Writer Class Id: {*******-*****-**-***-******}
       Writer Name: SharePoint Services Writer
       Writer Instance ID: *******-*****-**-***-******}
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="VSS" />
        <EventID Qualifiers="0">8193</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="//////////////" />
        <EventRecordID>38864</EventRecordID>
        <Channel>Application</Channel>
        <Computer>**************</Computer>
        <Security />
      </System>
      <EventData>
        <Data>RegSetValueExW(0x00000104,SYSTEM\CurrentControlSet\Services\VSS\Diag\SharePoint Services Writer,0,REG_BINARY,00000000223ECE10.72)</Data>
        <Data>0x800703fa, Illegal operation attempted on a registry key that has been marked for deletion.
    </Data>
        <Data>

    Operation:
       Gathering Writer Data

    Context:
       Writer Class Id: {*******-*****-**-***-******}
       Writer Name: SharePoint Services Writer
       Writer Instance ID: {*******-*****-**-***-******}</Data>
        <Binary>2D20436F64653A20524547524547534330303030303338332D2043616C6C3A20524547524547534330303030303336342D205049443A202030303030333037362D205449443A202030303030323538342D20434D443A202022433A5C50726F6772616D2046696C65735C436F6D6D6F6E2046696C65735C4D6963726F736F6674205368617265645C5765622053657276657220457874656E73696F6E735C31345C42494E5C53505752495445522E455845222020202020202D20557365723A204E616D653A20494E5452414E45545C73705F6661726D2C205349443A532D312D352D32312D333634343430393732372D333938373136333338352D323737373037333132372D31393332353220202020</Binary>
      </EventData>
    </Event>

    ****************************************************

    Log Name:      Application
    Source:        VSS
    Date:          12.01.2012 13:36:02
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      *************
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine RegSetValueExW(0x000003ac,SYSTEM\CurrentControlSet\Services\VSS\Diag\OSearch14 VSS Writer,0,REG_BINARY,0000000002CFCE50.72).  hr = 0x800703fa, Illegal operation attempted on a registry key that has been marked for deletion.
    .

    Operation:
       Gather writers' status

    Context:
       Writer Class Id: {0*******-*****-**-***-******}
       Writer Name: OSearch14 VSS Writer
       Writer Instance ID: {*******-*****-**-***-******}
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="VSS" />
        <EventID Qualifiers="0">8193</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-01-12T11:36:02.000000000Z" />
        <EventRecordID>38868</EventRecordID>
        <Channel>Application</Channel>
        <Computer>***************</Computer>
        <Security />
      </System>
      <EventData>
        <Data>RegSetValueExW(0x000003ac,SYSTEM\CurrentControlSet\Services\VSS\Diag\OSearch14 VSS Writer,0,REG_BINARY,0000000002CFCE50.72)</Data>
        <Data>0x800703fa, Illegal operation attempted on a registry key that has been marked for deletion.
    </Data>
        <Data>

    Operation:
       Gather writers' status

    Context:
       Writer Class Id: {*******-*****-**-***-******}
       Writer Name: OSearch14 VSS Writer
       Writer Instance ID: {*******-*****-**-***-******}</Data>
        <Binary>2D20436F64653A20524547524547534330303030303338332D2043616C6C3A20524547524547534330303030303336342D205049443A202030303030333332382D205449443A202030303030323635362D20434D443A202022433A5C50726F6772616D2046696C65735C4D6963726F736F6674204F666669636520536572766572735C31342E305C42696E5C6D737365617263682E65786522202020202020202D20557365723A204E616D653A20494E5452414E45545C53505F5365617263682C205349443A532D312D352D32312D333634343430393732372D333938373136333338352D323737373037333132372D3139333235362020</Binary>
      </EventData>
    </Event>

    ***************

    I checked the sql account farm admin account is sysadmin,dbowner but I dont understand what do you want to say about unaccesible if you ask about access from WFE to SQL yes it pings eachother.

     

    Friday, January 20, 2012 7:30 AM
  • Thanks... that information is useful.

    For whatever reason that key was marked for deletion so any operation on that key can't be completed.

    To leave from that situation you will need to reboot the WFE and then re-register the SharePoint VSS Writer by running ConfigureSharePoint.....


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Friday, January 20, 2012 7:33 AM
    Moderator
  • Thanks... that information is useful.

    For whatever reason that key was marked for deletion so any operation on that key can't be completed.

    To leave from that situation you will need to reboot the WFE and then re-register the SharePoint VSS Writer by running ConfigureSharePoint.....


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights

    Hi Wilson again;

    We tried this option but in our case even restart WFE server and reregister it does not give an error but also sharepoint vss writer doesnt seen in vss admin list writer

    Saturday, January 21, 2012 1:28 AM
  • So after the reboot you are no longer seeing those VSS errors in application log, correct?
    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Saturday, January 21, 2012 1:30 AM
    Moderator