Anonymous

My feedback

  1. 5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  System Center Data Protection Manager » SCDPM  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  System Center Data Protection Manager » SCDPM  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 15 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  System Center Data Protection Manager » SCDPM  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  System Center Data Protection Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  5. 13 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  System Center Data Protection Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  6. 104 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    58 comments  ·  System Center Data Protection Manager » SCDPM  ·  Flag idea as inappropriate…  ·  Admin →

    The error 40002 could be reported in multiple scenarios of VHD mount and unmount failure.
    Here are more details -

    WMI Out of memory (Fixed with UR7 for DPM 2016 and already part of DPM 2019 RTM):
    One of the top scenario where we observed the 40002 error is due to WMI out of memory. In a scenario, where you see 40002 error in DPM Console and at the same time you may see WMI-Activity error event ID 5858 logged with Result code 0×80041006. This code translates to “not enough memory for the operation’. To address this issue, with DPM 2016 UR 7 we increased the default WMI memory limit from 20MB to 60MB by adding registry keys (details below). This change is already part of DPM 2019 RTM.

    If you still see the same failure, the work around could be to increase this limit a bit…

    Anonymous supported this idea  · 
  7. 101 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous supported this idea  · 
  8. 128 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous supported this idea  · 

Feedback and Knowledge Base