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.
The term 'Connect-DPMServer' is not recognized as the name of a cmdlet, function, script file, or operable program.
