Hi Guys
I am experiencing the same issues mentioned in the above posts. I was able to stop my ops manager agents crashing out on my DPM servers by implementing the registry changes in Kevingreene's it blog.
After applying the reg changes the system center agents stabalised and the DPM servers appeared in my SCOM console in the DPM 2012 section however both had a red cross next to them, I cant remember the exact alarm but it was something like...
' could not verify DPM server running'. I looked at the two DPM servers and noticed that there identical events logged on each DPM server, pasted below, Looks like a discovery script is unable to run correctly.
The beta MP had previously worked for us with no such errors, I still have copy of the RC MP's which I used to replace the RTM MP's. The DPM servers now have no errors in there event log and discovery scripts appear to be running ok (no errors thrown)
however the DPM servers no longer appear in the ops console in the DPM 2012 section.
If anyone could shed some light on what's going on that would be great, pasted below is the eventlog that relates to the discovery script not running. (NB. '*' are were i've edited name of our kit)
Log Name: Operations Manager
Source: Health Service Modules
Date: 09/08/2012 12:54:22
Event ID: 22406
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: VPDPM**
Description:
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:52 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: PSDiscovery.ps1
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataProtectionManager.2011.Discovery.PSDiscovery
Instance name: VPDPM**
Instance ID: {1C220362-B6C2-A6AA-45DF-42E705AC98E4}
Management group: VPMG**
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Health Service Modules" />
<EventID Qualifiers="49152">22406</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-08-09T11:54:22.000000000Z" />
<EventRecordID>50250</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>VPDPM*.*.*</Computer>
<Security />
</System>
<EventData>
<Data>VPMG***</Data>
<Data>Microsoft.SystemCenter.DataProtectionManager.2011.Discovery.PSDiscovery</Data>
<Data>VPDPM3</Data>
<Data>{1C220362-B6C2-A6AA-45DF-42E705AC98E4}</Data>
<Data>PSDiscovery.ps1</Data>
<Data>7200</Data>
<Data>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:52 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)
</Data>
<Data>System.Management.Automation.RuntimeException</Data>
</EventData>
</Event>
SCOM R2 CU3 and DPM 2012 4.0.1800.0
Important
