none
DPM2010 - DPM could not enumerate application component ID:964 & ID:966 RRS feed

  • Question

  • Got a DPM2010 server and trying to protect my sql server with 4 instances. 3 Instances will get protected. One instance gives the following messages and isn't visible in the modifying or creating a protection group. Messages are listed below. Anyone have experience with this issue?

    DPM could not enumerate application component MER1-SRV025\SCCM\master on protected computer mer1-srv025.zorg.local. (ID: 964)

    DPM could not enumerate application component MER1-SRV025\SCCM\model on protected computer mer1-srv025.zorg.local. (ID: 964)

    DPM could not enumerate application component MER1-SRV025\SCCM\msdb on protected computer mer1-srv025.zorg.local. (ID: 964)

    DPM could not enumerate application component MER1-SRV025\SCCM\ReportServer$SCCM on protected computer mer1-srv025.zorg.local. (ID: 964)

    DPM could not enumerate application component MER1-SRV025\SCCM\ReportServer$SCCMTempDB on protected computer mer1-srv025.zorg.local. (ID: 964)

    DPM could not enumerate application component MER1-SRV025\SCCM\SMS_Z00 on protected computer mer1-srv025.zorg.local. (ID: 964)

    DPM could not connect to SQL server instance MER1-SRV025\SCCM on the protected computer mer1-srv025.zorg.local. (ID: 966)


    yours sincerly, Robin E. Turpijn Microsoft Manageabilty Specialist @ Wortell, Lijnden NL.
    • Moved by Praveen D [MSFT] Monday, July 19, 2010 9:03 AM Moving to DPM SQL Protection Forum (From:Data Protection Manager)
    Monday, July 5, 2010 2:40 PM

Answers

  • can you check if the output of<commandPrompt$>vssadmin list writers </end> list all the different writers and check that all the writers are in healthy state (specially for the above SQL instance)

     

    Also can you check by directly connecting to the SQL instance through SQL  Management Studio and check that the DBs are correctly listed. Just to make sure that the DB files (mdf/ldf) are present in their respective filesystem path/folder. 

     

    -Paggi

    This posting is provided "AS IS" with no warranties, and confers no rights.

     

    -

    Monday, July 5, 2010 3:35 PM

All replies

  • can you check if the output of<commandPrompt$>vssadmin list writers </end> list all the different writers and check that all the writers are in healthy state (specially for the above SQL instance)

     

    Also can you check by directly connecting to the SQL instance through SQL  Management Studio and check that the DBs are correctly listed. Just to make sure that the DB files (mdf/ldf) are present in their respective filesystem path/folder. 

     

    -Paggi

    This posting is provided "AS IS" with no warranties, and confers no rights.

     

    -

    Monday, July 5, 2010 3:35 PM
  • Hi,

    Please reopen this thread if this issue persists. For now I am closing this thread.


    Thanks Shyama Hembram[MSFT] This posting is provided AS IS, with no warranties, and confers no rights.
    Thursday, February 10, 2011 1:48 PM
    Moderator
  • Hello,

    I am having the same issue on one of my rebuild servers for past couple of weeks. Any idea how to resolve this issue? I check VSS writer for SQL and its fine with no errors

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {cfa684c9-fdba-47e5-be1e-5bb786d66d6f}
       State: [1] Stable
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {e46ff53b-ceaa-48bb-974a-bea8247dbcc6}
       State: [1] Stable
       Last error: No error

    I tried looking at Firewall, did ping test, re-installed the agent, attached DPM agent to other DPM server but still no luck. Any one know any idea about this issue?

    Thank You

    Rama

    Monday, March 26, 2012 9:03 PM
  • Hi Shyama

    I am new to this forum but i am getting this error with one of my 2008 R2 databases using DPM2012sp1.

    any advise?


    Sunday, February 17, 2013 1:09 PM