none
DPM2010+SharePoint2010: DPM is unable to enumerate Virtual SSP Writer on computer [computer name]. (ID: 3005)

    Question

  • Unable to Protect SharePoint 2010 after in-place upgrade from MOSS 2007 on DPM 2010

    Running DPM 2010 x64.  DPM was upgraded from 2007 prior to the SharePoint upgrade from MOSS 2007 to SharePoint 2010.  When DPM was upgraded, MOSS 2007 was still being protected properly with DPM.   After upgrading SharePoint (in-place), the backups no longer worked.

    *I do have an open case with Microsoft's DPM Team, but my team has gotten absolutely nowhere with them for over 2 weeks !

    I have uninstalled the DPM agent on all servers in the farm including the SQL server and reinstalled manually with all the proper steps including the ConfigureSharePoint and related switches.  I have ensured that Windows firewall are not blocking (turned them off) and have looked at event logs and network packets for clues. 

    The only error I get is when we attempt to add a WFE to a new protection group.  When the protected server components are enumerated, the following error appears (this happens for every SP Server WFE).

    DPM is unable to enumerate Virtual SSP Writer on computer spapp1.domain.com. (ID: 3055) Please ensure that Virtual SSP Writer is accessible to protection agent.

    I have verified that MOSS 2007 was uninstalled on all server (this was done manually b/c the MOSS 2007 -> 2010 upgraded failed to do so)

    I have verified that WSS 3.0 was uninstalled on all server (this was done manually b/c the MOSS 2007 -> 2010 upgraded failed to do so)

    I am able to backup other components from the WFE that are not SharePoint related (files, system state)

    Currently, none of the nodes are being protected in any fashion.   Anyone out there have any suggestions?

    Thanks in advance!

     

    Could there be something with the SharePoint SPN (Service Principal Name) that could cause an issue like this?  Shooting in the dark...

     

    Here are the logs specific to an attempt to enumerate in the MSDPMCurr.errlog

    ervices.cpp(218) DCE684B2-4874-432B-BDED-801E99B1B243 NORMAL CJobManagerServices::AddJobDefinition()
    1668 28C8 06/30 05:59:19.350 16 Task.cs(235) NORMAL Changing task state from 'Invalid' -> 'Start' (dc9561f6-1457-4516-a75f-95c03185824f)
    1668 20E8 06/30 05:59:19.449 16 ActiveJob.cs(524) NORMAL Begin GenerateWorkplan:JobID=9da3ba66-6633-4025-9b83-d7ac6d6be853, ItemID=dc9561f6-1457-4516-a75f-95c03185824f
    1668 20E8 06/30 05:59:19.449 01 TaskExecutor.cs(81) DC9561F6-1457-4516-A75F-95C03185824F NORMAL GenerateWorkplan(job=9da3ba66-6633-4025-9b83-d7ac6d6be853) - Entering
    1668 20E8 06/30 05:59:19.489 02 EventManager.cs(88) NORMAL Publishing event from TaskExecutor.cs(107): TaskCreated, [TaskID=dc9561f6-1457-4516-a75f-95c03185824f]
    1668 20E8 06/30 05:59:19.495 01 TaskExecutor.cs(127) DC9561F6-1457-4516-A75F-95C03185824F NORMAL GenerateWorkplan(job=9da3ba66-6633-4025-9b83-d7ac6d6be853) - Finished (error=False), executing GenerateWorkplanCallback
    1668 20E8 06/30 05:59:19.495 16 Task.cs(235) NORMAL Changing task state from 'Start' -> 'GenerateWorkplan' (dc9561f6-1457-4516-a75f-95c03185824f)
    1668 20E8 06/30 05:59:19.500 16 ActiveJob.cs(774) NORMAL Begin new execution batch at task:(False)-dc9561f6-1457-4516-a75f-95c03185824f
    1668 20E8 06/30 05:59:19.501 16 ActiveJob.cs(794) NORMAL Dispatching task for execution:False-dc9561f6-1457-4516-a75f-95c03185824f
    1668 10A8 06/30 05:59:19.502 16 ActiveJob.cs(524) NORMAL Begin ExecuteTask:JobID=9da3ba66-6633-4025-9b83-d7ac6d6be853, ItemID=dc9561f6-1457-4516-a75f-95c03185824f
    1668 10A8 06/30 05:59:19.503 01 TaskExecutor.cs(692) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Setting up Fsm: verb[9c494a3e-9680-4dc4-8e3a-885f9959c2e4]
    1668 10A8 06/30 05:59:19.503 01 TaskExecutor.cs(489) DC9561F6-1457-4516-A75F-95C03185824F NORMAL ExecuteTask(job=9da3ba66-6633-4025-9b83-d7ac6d6be853) - Starting task instance
    1668 20E8 06/30 05:59:19.504 02 EventManager.cs(88) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Publishing event from TaskInstance.cs(407): TaskStart, [TaskID=dc9561f6-1457-4516-a75f-95c03185824f]
    1668 20E8 06/30 05:59:19.507 01 TaskInstance.cs(444) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Task: Initial transition enqueued, startState='Init State'
    1668 143C 06/30 05:59:19.512 08 BranchedVolumeInquiry.cs(67) DC9561F6-1457-4516-A75F-95C03185824F NORMAL BranchedVolumeInquiry::TriggerVolumeInquiry:: CMTE triggered Volume Inquiry on server [spapp1.domain.com]
    1668 20E8 06/30 05:59:19.515 08 RunInquiryCommonTypes.cs(1306) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Adding inquiry workitem dc9561f6-1457-4516-a75f-95c03185824f of server spapp1.domain.com to RunningAcInquiries HashTable
    1668 20E8 06/30 05:59:23.271 08 RunInquiry.cs(468) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Agent Inquiry started on server spapp1.domain.com
    1668 2578 06/30 05:59:23.403 08 ProcessDelegate.cs(104) DC9561F6-1457-4516-A75F-95C03185824F NORMAL ==>UpdateIntentWithInquiryResults
    1668 2578 06/30 05:59:23.403 08 InquiryManager.cs(52) DC9561F6-1457-4516-A75F-95C03185824F NORMAL ==>UpdateDataSourceFromInquiryResult
    1668 2578 06/30 05:59:23.464 17 InquiryManager.cs(205) DC9561F6-1457-4516-A75F-95C03185824F NORMAL IntentManager::UpdateDataSourceFromInquiryResult:: Updating File System Datasources completed
    1668 2578 06/30 05:59:23.464 17 InquiryManager.cs(213) DC9561F6-1457-4516-A75F-95C03185824F NORMAL IntentManager::UpdateDataSourceFromInquiryResult:: Updating Application Datasources completed
    1668 2578 06/30 05:59:23.465 08 InquiryManager.cs(52) DC9561F6-1457-4516-A75F-95C03185824F NORMAL <--UpdateDataSourceFromInquiryResult
    1668 2578 06/30 05:59:23.465 08 ProcessDelegate.cs(104) DC9561F6-1457-4516-A75F-95C03185824F NORMAL <--UpdateIntentWithInquiryResults
    1668 2578 06/30 05:59:23.474 08 RunInquiry.cs(493) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Agent Inquiry Finished on server spapp1.domain.com
    1668 2578 06/30 05:59:23.474 08 RunInquiryCommonTypes.cs(1313) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Deleting inquiry workitem dc9561f6-1457-4516-a75f-95c03185824f from RunningAcInquiries HashTable
    1668 20E8 06/30 05:59:23.474 08 BranchedVolumeInquiry.cs(136) DC9561F6-1457-4516-A75F-95C03185824F NORMAL BranchedVolumeInquiry::VolumeInquirySuccess:: CMTE finished Volume Inquiry on server [spapp1.domain.com]
    1668 1BDC 06/30 05:59:23.571 08 RunInquiryCommonTypes.cs(1306) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Adding inquiry workitem dc9561f6-1457-4516-a75f-95c03185824f of server spapp1.domain.com to RunningAcInquiries HashTable
    1668 240C 06/30 05:59:23.704 08 RunInquiry.cs(468) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Agent Inquiry started on server spapp1.domain.com
    1668 143C 06/30 05:59:23.829 08 ProcessDelegate.cs(268) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Enterring ProcessDelegate::ProcessShares. 
    1668 143C 06/30 05:59:23.829 08 ProcessDelegate.cs(268) DC9561F6-1457-4516-A75F-95C03185824F NORMAL             Current server context = StartNodeServer = spapp1.domain.com | ActiveNode = spapp1.domain.com | Cluster =  | PhysicalNodeCount = 0
    1668 240C 06/30 05:59:23.886 08 RunInquiry.cs(493) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Agent Inquiry Finished on server spapp1.domain.com
    1668 240C 06/30 05:59:23.886 08 RunInquiryCommonTypes.cs(1313) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Deleting inquiry workitem dc9561f6-1457-4516-a75f-95c03185824f from RunningAcInquiries HashTable
    1668 143C 06/30 05:59:23.888 08 ApplicationInquiryBlock.cs(83) DC9561F6-1457-4516-A75F-95C03185824F NORMAL ApplicationInquiry::StartApplicationInquiry::Entering CMTE triggered Application Inquiry on server [spapp1.domain.com]
    1668 15EC 06/30 05:59:23.893 08 RunInquiryCommonTypes.cs(1306) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Adding inquiry workitem dc9561f6-1457-4516-a75f-95c03185824f of server spapp1.domain.com to RunningAcInquiries HashTable
    1668 2578 06/30 05:59:24.025 08 RunInquiry.cs(468) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Agent Inquiry started on server spapp1.domain.com
    1668 1BDC 06/30 05:59:28.897 08 InquiryContext.cs(415) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Adding recoverable error 3055,Not implemented (0x80004001) to recoverable errors list
    1668 1BDC 06/30 05:59:28.948 08 RunInquiry.cs(493) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Agent Inquiry Finished on server spapp1.domain.com
    1668 1BDC 06/30 05:59:28.948 08 RunInquiryCommonTypes.cs(1313) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Deleting inquiry workitem dc9561f6-1457-4516-a75f-95c03185824f from RunningAcInquiries HashTable
    1668 240C 06/30 05:59:28.949 08 ApplicationInquiryBlock.cs(166) DC9561F6-1457-4516-A75F-95C03185824F NORMAL ApplicationInquiry::ApplicationInquirySuccess::Application Inquiry completed for server [spapp1.domain.com]
    1668 240C 06/30 05:59:28.950 08 InquiryHelper.cs(172) DC9561F6-1457-4516-A75F-95C03185824F NORMAL ==>FilterValidDataSources
    1668 240C 06/30 05:59:28.950 08 InquiryHelper.cs(172) DC9561F6-1457-4516-A75F-95C03185824F NORMAL <--FilterValidDataSources
    1668 240C 06/30 05:59:28.962 08 ProcessDelegate.cs(104) DC9561F6-1457-4516-A75F-95C03185824F NORMAL ==>UpdateIntentWithInquiryResults
    1668 240C 06/30 05:59:28.963 08 InquiryManager.cs(52) DC9561F6-1457-4516-A75F-95C03185824F NORMAL ==>UpdateDataSourceFromInquiryResult
    1668 240C 06/30 05:59:29.013 17 InquiryManager.cs(205) DC9561F6-1457-4516-A75F-95C03185824F NORMAL IntentManager::UpdateDataSourceFromInquiryResult:: Updating File System Datasources completed
    1668 240C 06/30 05:59:29.045 17 InquiryManager.cs(213) DC9561F6-1457-4516-A75F-95C03185824F NORMAL IntentManager::UpdateDataSourceFromInquiryResult:: Updating Application Datasources completed
    1668 240C 06/30 05:59:29.048 08 InquiryManager.cs(52) DC9561F6-1457-4516-A75F-95C03185824F NORMAL <--UpdateDataSourceFromInquiryResult
    1668 240C 06/30 05:59:29.048 08 ProcessDelegate.cs(104) DC9561F6-1457-4516-A75F-95C03185824F NORMAL <--UpdateIntentWithInquiryResults
    1668 240C 06/30 05:59:29.048 02 EventManager.cs(88) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Publishing event from ApplicationInquiryBlock.cs(201): InquiryResult, [TaskID=dc9561f6-1457-4516-a75f-95c03185824f]
    1668 240C 06/30 05:59:29.053 08 FindDataSourceMachine.cs(302) DC9561F6-1457-4516-A75F-95C03185824F NORMAL ==>ResolveReferentialDependencyInDataSources
    1668 240C 06/30 05:59:29.055 08 FindDataSourceMachine.cs(326) DC9561F6-1457-4516-A75F-95C03185824F NORMAL FindDataSourceMachine::ResolveReferentialDependencyInDataSources::Skipping ResolveReferentialDependencyInDataSources
    1668 240C 06/30 05:59:29.055 08 FindDataSourceMachine.cs(302) DC9561F6-1457-4516-A75F-95C03185824F NORMAL <--ResolveReferentialDependencyInDataSources
    1668 1BDC 06/30 05:59:29.103 02 EventManager.cs(88) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Publishing event from FindDataSourceMachine.cs(537): InquiryResult, [TaskID=dc9561f6-1457-4516-a75f-95c03185824f]
    1668 1BDC 06/30 05:59:29.109 02 EventManager.cs(88) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Publishing event from TaskInstance.cs(825): TaskStop, [TaskID=dc9561f6-1457-4516-a75f-95c03185824f]
    1668 1BDC 06/30 05:59:29.114 01 TaskExecutor.cs(849) DC9561F6-1457-4516-A75F-95C03185824F NORMAL Task stopped (state=Completed, error=Success; 0; None)
    1668 1BDC 06/30 05:59:29.114 16 Task.cs(235) NORMAL Changing task state from 'GenerateWorkplan' -> 'Execute' (dc9561f6-1457-4516-a75f-95c03185824f)
    1668 15EC 06/30 05:59:29.122 16 Task.cs(235) NORMAL Changing task state from 'Execute' -> 'Retire' (dc9561f6-1457-4516-a75f-95c03185824f)
    1668 15EC 06/30 05:59:29.123 01 TaskExecutor.cs(179) DC9561F6-1457-4516-A75F-95C03185824F NORMAL RetireWorkplan(job=9da3ba66-6633-4025-9b83-d7ac6d6be853) - Calling derived RetireWorkplan
    1668 15EC 06/30 05:59:29.123 01 TaskExecutor.cs(227) DC9561F6-1457-4516-A75F-95C03185824F ACTIVITY RetireWorkplan(job=9da3ba66-6633-4025-9b83-d7ac6d6be853) - Retiring task: Completed
    1668 15EC 06/30 05:59:29.125 16 ActiveJob.cs(1167) NORMAL Final task state=Retire(dc9561f6-1457-4516-a75f-95c03185824f)
    1668 15EC 06/30 05:59:29.125 16 Task.cs(235) NORMAL Changing task state from 'Retire' -> 'Succeeded' (dc9561f6-1457-4516-a75f-95c03185824f)
    1668 0754 06/30 05:59:32.254 08 configmanagerservices.cpp(35) DC9561F6-1457-4516-A75F-95C03185824F NORMAL CConfigurationManagerServices::DeleteInquiryResultTables(). guidTaskID={DC9561F6-1457-4516-A75F-95C03185824F}

     

     

    • Moved by Praveen D [MSFT] Monday, July 19, 2010 7:05 AM Moving to DPM SharePoint Protection Forum (From:Data Protection Manager)
    Wednesday, June 30, 2010 6:25 AM

Answers

  • This issue has been resolved with the assistance of the SharePoint and DPM teams.

    Basically, the error was related to the inability to enumerate all resources defined in the farm's configuration.  What the actual issue was turned out to be a missing database for one of the search services that was configured.

    A similar internal MS bug was found that referenced issues with the Search services.  This led us to look at restarting our Search services on all of the servers in the farm.  Even though all of the search services were "running", one of them would not restart and asked to reprovide the credentials and database names, etc.  Before I submitted the restart, I verified on the SQL Server that the database that was referenced, did not exist !  You may ask, "How was SharePoint stating that the service was running if indeed it was not?"  I'm not sure, but after restarting the particular search service, the database was recreated and the VSS enumeration by DPM worked!

    So a possible solution (one that worked for me) is to restart all of your search services and ensure that all 'referenced' databases actually exist.

     

    • Marked as answer by millertime78 Monday, August 9, 2010 4:05 PM
    Monday, August 9, 2010 4:05 PM
  • Hi,

    I know this is an old thread, but I've had exactly the same issue. After trying everything in this thread without any luck I opened a case with Microsoft support. 

    The first fix they suggested worked and is very simple, so I thought I'd share it.

    Have you enabled SP Search for the sharepoint? 

    If yes…. 

    Try to delete the below key from the registry on the sharepoint server and then check 

    HKLM\Software\Microsoft\Microsoft Data Protction manager\agent\2.0

    DWORD Value: SharePointSearchEnumerationEnabled

    Tim

    Tuesday, April 23, 2013 3:23 PM

All replies

  • Hey,

    I'm not sure if I can do better then the DPM team, and if you already did these things, then forgive me ;-)

    1. Is the SPWriter service running on the WFE servers?

    2. If they are running, use the following to register the writer: (http://technet.microsoft.com/en-us/library/cc287616(office.12).aspx)

    Or in short: stsadm -o registerwsswriter if you don't want to go trough the article

    3. Do a vssadmin list writers to see if there are errors with the vss writers

    4. Run the configuresharepoint again with a farm administrator account

    5. Try again

    Just my 2 cents

    Cheers,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Wednesday, June 30, 2010 7:04 AM
    Moderator
  • Interesting....

    I ran the "vssadmin list writers" command and received the list below.  Notice there are no errors but there is not a SharePoint writer.

    C:\Program Files\Microsoft Data Protection Manager\DPM\bin>vssadmin list writers

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Waiting for responses.
    These may be delayed if a shadow copy is being prepared.

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {6660ab78-6c79-4fb4-9838-69cea04d4be6}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {27c6a62f-25a4-4263-ab24-bd649fcf69d3}
       State: [1] Stable
       Last error: No error

    Writer name: 'FSCVSSWriter'
       Writer Id: {68124191-7787-401a-8afa-12d9d7ccc6ee}
       Writer Instance Id: {e5843d88-1501-44d3-a8d1-a3388657088e}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {6332d6a3-ccdf-41d3-b811-91eb5e0a0e93}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {0ecf3649-9ea2-4689-885b-5dda76548d86}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {f700d1e6-59b1-42b5-b7c8-614b6057d3e6}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {35aa494b-100d-45a2-a9da-584ecc7b6269}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {ab24d3f4-2f48-4997-84cf-7d20885a443f}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {4f4fe7cc-62b7-4254-abf1-725e7021eae1}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {ea7c409b-e06f-4b73-a517-debd04db16f9}
       State: [1] Stable
       Last error: No error

    Writer name: 'SPSearch4 VSS Writer'
       Writer Id: {35500004-0201-0000-0000-000000000000}
       Writer Instance Id: {27df6071-de78-49fb-93a8-3bac41475481}
       State: [1] Stable
       Last error: No error

     

     

    Wednesday, June 30, 2010 4:21 PM
  • FYI: Scott Herrick is a team member helping to respond to this thread.

    Running the same command on a different (our test) SharePoint server/farm that does enumerate the SharePoint components in DPM, the following is returned:

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {7f836000-e37f-4fad-9ba5-0e020174f4e9}
       State: [1] Stable
       Last error: No error

    Writer name: 'SharePoint Services Writer'
       Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
       Writer Instance Id: {127783ca-549e-40ed-9f38-bea14d410d66}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {96031587-5374-40d1-b81a-fb639e19a9b4}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {4bc1dc9a-7eeb-4783-b045-ce3fd17c9e3b}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {ac6d25a5-2218-43f7-9bd1-d3d3cd0252d5}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {df2057c9-4cda-411f-91cc-b322333119a6}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {08ebf1d9-9cae-45ee-a828-6afe6118aa56}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {35723f42-6b38-4dcb-9f9f-82ef42b7f70b}
       State: [1] Stable
       Last error: No error

    Writer name: 'SPSearch4 VSS Writer'
       Writer Id: {35500004-0201-0000-0000-000000000000}
       Writer Instance Id: {ab1efb1a-6984-4956-a42c-07bb9bd36182}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {ed95d9d1-197a-4923-b181-ef6f1c3dbd4b}
       State: [1] Stable
       Last error: No error

    Writer name: 'OSearch14 VSS Writer'
       Writer Id: {0ff1ce14-0201-0000-0000-000000000000}
       Writer Instance Id: {faa2d976-0839-4016-8880-4d3ab166c100}
       State: [1] Stable
       Last error: No error

    It appears that the server/farm that is having the issue doesn not have the "OSearch14 VSS Writer" and the "SharePoint Services Writer".  I did try to run the stsadm -o registerwsswriter on the server (and it did successfully), but the writer still doesn't show in the vssadmin command results.

     

    Wednesday, June 30, 2010 5:04 PM
  • Does this mean that you see the Windows SharePoint Services VSS Writer running in the services.msc?

    Last time I had this issue was because the service wasn't running.

    Just my 2 cents

    Cheers,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Wednesday, June 30, 2010 5:52 PM
    Moderator
  • Does this mean that you see the Windows SharePoint Services VSS Writer running in the services.msc?

    Last time I had this issue was because the service wasn't running.

    Just my 2 cents

    Cheers,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm

     

    The "Windows SharePoint Services  VSS Writer" referes to the 12 hive which is MOSS 2007 and not SHarePoint 2010.

    On these servers, the above mentioned service does not exist.  I expect this to be by design as WSS 3.0 was replaced with SharePoint Foundation Services (v4 in the 14 hive).

    I did confirm the "SPWriterV4" aka "SharePoint 2010 VSS Writer" exists and is started.  It's exe path is "c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\SPWRITER.EXE".  It is configured to run as a Farm Adminstrator account which is also a local admin account.

    Thursday, July 1, 2010 4:31 AM
  • Does this mean that you see the Windows SharePoint Services VSS Writer running in the services.msc?

    Last time I had this issue was because the service wasn't running.

    Just my 2 cents

    Cheers,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm

     

    The service "Windows SharePoint Services VSS Writer" doesn't exist b/c that was MOSS 2007's name.  The service "SharePoint 2010 VSS Writer" does exist and is started (aka, SPWriterV4).

     

    Thursday, July 1, 2010 4:33 AM
  • Is there something that can be done for SharePoint 2010 relative to this post?

    http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/f7cc877e-0f5d-42c6-8a98-caab26e55ca1/

    Thursday, July 1, 2010 4:51 AM
  • Hey,

    I'm afraid this is out of my league :-(

    Maybe you could ask this question on the sharepoint forum or ask the guys from Microsoft where you have the call to transfer it to the sharepoint guru's

    Sorry mate

    Cheers

    Mike


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Thursday, July 1, 2010 6:38 AM
    Moderator
  • Hi Millertime,

    Any hopes with this? In my environment it vssadmin lists all the 12 writers but i still get the DPM is unable to enumerate Virtual SSP Writer and virtual sp search writer. My case is similar to yours where an inplace upgrade was carried out and the issue has remained even though i re-installed the agent.

    Kindly update if there is any progress with ms support.

    Thanks.


    Damilola Osude, MCITP
    Friday, July 30, 2010 7:02 AM
  • This issue has been resolved with the assistance of the SharePoint and DPM teams.

    Basically, the error was related to the inability to enumerate all resources defined in the farm's configuration.  What the actual issue was turned out to be a missing database for one of the search services that was configured.

    A similar internal MS bug was found that referenced issues with the Search services.  This led us to look at restarting our Search services on all of the servers in the farm.  Even though all of the search services were "running", one of them would not restart and asked to reprovide the credentials and database names, etc.  Before I submitted the restart, I verified on the SQL Server that the database that was referenced, did not exist !  You may ask, "How was SharePoint stating that the service was running if indeed it was not?"  I'm not sure, but after restarting the particular search service, the database was recreated and the VSS enumeration by DPM worked!

    So a possible solution (one that worked for me) is to restart all of your search services and ensure that all 'referenced' databases actually exist.

     

    • Marked as answer by millertime78 Monday, August 9, 2010 4:05 PM
    Monday, August 9, 2010 4:05 PM
  • So a possible solution (one that worked for me) is to restart all of your search services and ensure that all 'referenced' databases actually exist.

     


    Good for you Miller, but may i ask if the search services to be restarted is through sharepoint central administration or windows services? Because i restarted through the windows services and both search services sharepoint foundation search and sharepoint search server reatsrt without errors, however when i view manage services on this server through central admin, the status for the sharepoint foundation search service states starting. Any clues please?

    Thanks.


    Damilola Osude, MCITP
    • Edited by Damilola Osude Monday, August 30, 2010 11:37 AM update on issue
    Friday, August 27, 2010 2:05 PM
  • Hi,

    The issue has been resolved with the help of microsoft partner support. The issue was related to the upgrading of SharePoint Server. DPM looks in the registry under HKLM\Software\Microsoft\Shared Tools\Web Server Extensions. I was asked to check for a 12.0 key, export and remove it. Because dpm assumes SharePoint 3.0 even if a 14.0 key for SharePoint 2010 exists. I simply followed the instruction and the warnings in the dpm console disappeared.

    Hope this helps anyone else.


    Damilola Osude Business card
    Wednesday, September 15, 2010 12:35 PM
  • Hi,

    I know this is an old thread, but I've had exactly the same issue. After trying everything in this thread without any luck I opened a case with Microsoft support. 

    The first fix they suggested worked and is very simple, so I thought I'd share it.

    Have you enabled SP Search for the sharepoint? 

    If yes…. 

    Try to delete the below key from the registry on the sharepoint server and then check 

    HKLM\Software\Microsoft\Microsoft Data Protction manager\agent\2.0

    DWORD Value: SharePointSearchEnumerationEnabled

    Tim

    Tuesday, April 23, 2013 3:23 PM
  • Hi I have exactly the same issue described here. I have tried all the fixes provided but no joy. Does anyone have any other ideas?
    Wednesday, April 24, 2013 11:13 AM