none
The term 'Connect-DPMServer' is not recognized as the name of a cmdlet, function, script file, or operable program. RRS feed

  • Question

  • Hi,

    We're having issues monitoring DPM2012 after upgrading both DPM and SCOM to R2. We receive a critical alert from DPM:DPM server availability monitor.

    Operations Manager eventlog on the DPM server shows following error:

    The PowerShell script failed with below exception
    System.Management.Automation.RuntimeException: The term 'Connect-DPMServer' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At line:51 char:42
    +   $err = $($dpmServer = Connect-DPMServer <<<<  $dpmServerName) 2>&1
       at System.Management.Automation.FlowControlNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
       at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
       at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
    Script Name:	PGDiscovery.ps1 
    One or more workflows were affected by this. 

    Connect-DPMServer on the DPM server works in the Management Shell as well as in a regular Powershell session.

    On the Scom Management server the Cmdlet works in the DPM Management Shell but not in a regular Powershell session. Error message:

    Connect-DPMServer : The DPM Administrator Console version 4.1.3313.0 is incompatible with the DPM server version. (ID: 939) Ensure that the version is between 4.2.1100.0 and 4.2.1205.0. At line:1 char:1 + Connect-DPMServer dp01 + ~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Connect-DPMServer], DlsExcept ion + FullyQualifiedErrorId : UIVersionInCompatible,Microsoft.Internal.Enterpr iseStorage.Dls.UI.Cmdlet.Common.ConnectDpmServer

    This happens only after I install the DPM central console... with only DPM Remote Administration installed the Cmdlet works fine in a regular Powershell session. I'm not sure if this has anything to do with not being able to monitor DPM.

    I was also wondering if the script is run on the SCOM server or by the agent on the DPM server?

    I followed all steps in Kevin's blog... I also tried reintalling DPM central console and the DPM Remote Administration to no avail.

    Anyone any idea on how to further troubleshoot this?

    Grts.

    Tuesday, November 12, 2013 2:07 PM

Answers

  • is your DPM installed on a Windows Server 2008R2 server?

    Please read this:

    Centralized monitoring of DPM is not supported on Windows Server 2008 R2

    Description: The DPM Management Pack for System Center 2012 R2 cannot monitor instances of DPM for System Center 2012 R2 installed on Windows Server 2008 R2.

    Workaround: Upgrade the operating system on the DPM server to Windows Server 2012.

    • Marked as answer by BallieWallie Tuesday, November 26, 2013 11:41 AM
    Tuesday, November 26, 2013 11:04 AM

All replies

  • Update:

    Repaired the Microsoft System Center 2012 R2 DPM Remote Administration installation... now the Connect-DPM cmdlet works in a regular Powershell session. The SCOM action account is able to connect to the DPM server as well. Unfortunately monitoring DPMR2 still doesn't work.

    Grts.


    • Edited by BallieWallie Wednesday, November 13, 2013 10:22 AM incomplete
    Wednesday, November 13, 2013 10:21 AM
  • Can you delete the MP's from SCOM 2012, and wait for 2-3 days until importing them back into SCOM.

    Data will be groomed out from the Database then.

    Hope this helps you out ;-)


    Friday, November 15, 2013 1:56 PM
  • Hi,

    It seems you need to update your DPM Administrator Console.

    http://technet.microsoft.com/en-us/library/hh859552.aspx


    Niki Han
    TechNet Community Support

    Saturday, November 16, 2013 1:44 PM
    Moderator
  • Hi Gerry,

    Thanks for your suggestion... unfortunately it didn't work.

    Any other suggestions?

    Grts! 

    Thursday, November 21, 2013 8:27 AM
  • Hi Niki Han,

    DPM Server as well as client versions are R2.

    Grts.

    Thursday, November 21, 2013 8:29 AM
  • Open DPM Administrator Console, click Help and check ensure the version is between 4.2.1100.0 and 4.2.1205.0.


    Niki Han

    TechNet Community Support

    Monday, November 25, 2013 7:30 AM
    Moderator
  • is your DPM installed on a Windows Server 2008R2 server?

    Please read this:

    Centralized monitoring of DPM is not supported on Windows Server 2008 R2

    Description: The DPM Management Pack for System Center 2012 R2 cannot monitor instances of DPM for System Center 2012 R2 installed on Windows Server 2008 R2.

    Workaround: Upgrade the operating system on the DPM server to Windows Server 2012.

    • Marked as answer by BallieWallie Tuesday, November 26, 2013 11:41 AM
    Tuesday, November 26, 2013 11:04 AM
  • Hi Gerry,

    Yes it is... I guess we have to upgrade the DPM's OS to Server 2012 then!

    Thanks for looking into this... your the best ;-)

    Grts.



    • Edited by BallieWallie Tuesday, November 26, 2013 11:42 AM Edit
    Tuesday, November 26, 2013 11:41 AM