none
DPM 1801 - Protection group creation failed. RRS feed

  • Question

  • Brand new installation of DPM 1801 with a SQL 2014 installation on the same box (Physical box - win 2016 - HP DL380p Gen8, 48GB ram and  2 x Xeon E5-2640) Previously supported DPM 2010). All looks fine but when I'm creating a new protection group it always fails with

    Create Protection group: test  failed:

    Error 33507: DPM Could Not execute a WMI query. The query returned an error or an empty result. Recommended action: retry the operation.

    and

    Allocate Replica for d:\ failed.

    Error 33507: DPM Could Not execute a WMI query. The query returned an error or an empty result. Recommended action: retry the operation.

    Cant find anything wrong in th elogs but cant currently protect anything.

    Regards

    Richard


    Monday, August 5, 2019 7:04 AM

Answers

  • Hi sorry got dragged away.

    No still no good.

    SQL has correct collation.

    All SQL services are running fine

    No SQL events recorded other than this

    SQL Server Scheduled Job '2c6f6db6-2a69-412e-82dc-26e886f61afb' (0x3F74F1E4488E09459B827467E5AECD8F) - Status: Failed - Invoked on: 2019-08-07 13:00:00 - Message: The job failed.  The Job was invoked by Schedule 23644 (Schedule 1).  The last step to run was step 1 (Default JobStep).

    Asking the client if I can wipe the server and start again.

    Wednesday, August 7, 2019 12:10 PM

All replies

  • Hello Richard,

    What workloads are you trying to add in the protection group?

    When using a DPM version that uses Modern Backup Storage (MBS), DPM only allocates the space needed to protect the size of the data being protected.


    Note:
    The support for DPM 1801 ends on August 8, 2019, I would highly recommend upgrading to DPM 2019, since the Semi-Annual Channe (SAC) release has been discontinued.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:



    • Edited by Leon Laude Monday, August 5, 2019 7:55 AM
    Monday, August 5, 2019 7:53 AM
  • Thanks Leon

    Ive just moved to 1807, its a customer so need to look at their licensing for 2019. 

    I cant add any protection groups (this is a fresh installation) - even if I choose a single folder.  I have loads of storage space.

    d: 99% free 18,629.68GB

    e: 99% free 7,451.68GB

    Rich

    Monday, August 5, 2019 8:10 AM
  • Do you have any antivirus/anti-malware software installed on the DPM server?

    This can be caused by an antivirus/anti-malware software, if you have any installed please try disabling it or make sure you have the appropriate antivirus exclusions in place.

    Run antivirus software on the DPM server


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, August 5, 2019 8:14 AM
  • it had windows defender on, ive turned it off and still have the same issue.

    Monday, August 5, 2019 9:15 AM
  • You mentioned that you've moved to DPM 1807, so that's the version you're currently using?

    One thing that hit me is that you're using SQL Server 2014, this is not officially supported by DPM 1801 / DPM 1807, you'll find the supported SQL Server versions over here:
    Preparing your environment for System Center Data Protection Manager

    I would suggest using SQL Server 2016 (if using DPM 1801) or SQL Server 2016/2017 (if using DPM 1807).


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, August 5, 2019 9:58 AM
  • you can try disable calculation storage

    The corresponding registry key is "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Configuration\DiskStorage" with the Key, "EnableCustomAllocationOnReFSStorage" as a String set to 1 to enable custom size allocation, set to 0 for default size allocation with DPM." and than try add data to PG.

    https://social.technet.microsoft.com/Forums/en-US/9f2fd9b8-2397-4872-b292-b29210102ae0/registry-key-to-disable-data-size-calculation?forum=dataprotectionmanager



    • Edited by Aleks__ Monday, August 5, 2019 10:37 AM
    Monday, August 5, 2019 10:29 AM
  • I also suggest checking the DPM logs for more clues:

    Event Viewer > Applications and Service Logs > DPM Alerts

    And the DPM activity log on the DPM server, which is located at:

    %ProgramFiles%\Microsoft System Center\DPM\DPM\Temp\MSDPMCurr.errlog 


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, August 5, 2019 10:46 AM
  • ok so ive installed 2019 DPM and have installed sql 2017.

    Still get the same error, fails on creating protection groups

    No error in DPM Alerts

    and for curr.err.log:  

    I get this: state=Failed, result=AMAgentAccessDenied; -2147024891; WindowsHResult

    Monday, August 5, 2019 1:38 PM
  • Do you have any hardenings? Like GPOs, third party software?

    Is your user local administrator and have permissions to the DPM database?

    Tell us about your DPM setup:

    • DPM server
    • DPM Disks
    • Network
    • Protected server(s) (domain/workgroup? physical/virtual?)
    • Are the DPM agents green?

    Also check your Application log for any errors related to DPM.


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Monday, August 5, 2019 1:57 PM
    Monday, August 5, 2019 1:50 PM
  • DPM is a physical server - HP blade - 2x Xeon and 48GB Ram -

    2 locally attached disks for backup - D (14Tb) and E (10TB) - Basic, GPT and ReFS

    Storage pool created of 25TB

    Running DPM 2019 (10.19.58.0)

    SQL 2017 (on same box)

    2 x 4Gb network ports (one for man, 1 for iSCSI)

    All on the same domain - using a domain admin account

    Mixture of physical and virtual servers im trying to back up

    Can communicate with the agents without an issue and they are green.

    Monday, August 5, 2019 2:06 PM
  • This is a strange one..

    So you've previously ran DPM 2010 on this server? Did you reinstall the server from scratch?

    Have you tried rebooting?

    Make sure the Windows Management Instrumentation (WMI) service is running.

    What other applications are installed on the DPM server?

    Did you check if you have any Group Policy Objects (GPOs) that may be interfering?

    Does the Application log say anything?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, August 5, 2019 2:32 PM
  • Yeh is strange.. driving me crazy..

    yep, long story, dpm 2010 got corrupted and couldn't connect to any backups, the decision was to try and do an upgrade that failed, so I took over and reinstalled it all. but now we get the wmi error.

    Rebooted yep lots of times, wmi is running fine.

    Not looked at gpos but as it was running before?

    App log only shows this error:

    Log Name:      Application
    Source:        SQLAgent$xxxx
    Date:          05/08/2019 15:30:01
    Event ID:      208
    Task Category: Job Engine
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      xxxx
    Description:
    SQL Server Scheduled Job '2c6f6db6-2a69-412e-82dc-26e886f61afb' (0x3F74F1E4488E09459B827467E5AECD8F) - Status: Failed - Invoked on: 2019-08-05 15:30:00 - Message: The job failed.  The Job was invoked by Schedule 23644 (Schedule 1).  The last step to run was step 1 (Default JobStep).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLAgent$MSDPM**" />
        <EventID Qualifiers="16384">208</EventID>
        <Level>3</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2019-08-05T14:30:01.602171600Z" />
        <EventRecordID>34126</EventRecordID>
        <Channel>Application</Channel>
        <Computer>xxxxx</Computer>
        <Security />
      </System>
      <EventData>
        <Data>2c6f6db6-2a69-412e-82dc-26e886f61afb</Data>
        <Data>0x3F74F1E4488E09459B827467E5AECD8F</Data>
        <Data>Failed</Data>
        <Data>2019-08-05 15:30:00</Data>
        <Data>The job failed.  The Job was invoked by Schedule 23644 (Schedule 1).  The last step to run was step 1 (Default JobStep).</Data>
      </EventData>
    </Event>

    Monday, August 5, 2019 2:56 PM
  • Ok thanks for clearing that up.

    Does the SQL Server have the correct collation? (SQL_Latin1_General_CP1_CI_AS)

    Are all the SQL Server services running?

    Check the SQL Server logs if there are any clues there.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, August 5, 2019 3:14 PM
  • Any update on your issue?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, August 7, 2019 7:40 AM
  • Hi sorry got dragged away.

    No still no good.

    SQL has correct collation.

    All SQL services are running fine

    No SQL events recorded other than this

    SQL Server Scheduled Job '2c6f6db6-2a69-412e-82dc-26e886f61afb' (0x3F74F1E4488E09459B827467E5AECD8F) - Status: Failed - Invoked on: 2019-08-07 13:00:00 - Message: The job failed.  The Job was invoked by Schedule 23644 (Schedule 1).  The last step to run was step 1 (Default JobStep).

    Asking the client if I can wipe the server and start again.

    Wednesday, August 7, 2019 12:10 PM