Opsmgr/SCOM 2007 R2 – BUG DPM 2010 MP – Discovery failed – Eventid 21406

This entry was posted by on Friday, 22 April, 2011 at

When you use Opsmgr to Monitor Data Protection Manager, and you find out that Opsmgr don’t discovery all the data from de DPM server.

The first thing you should notice is that you don’t get any alerts or warnings from the DPM server.

Issue: The DPM Discovery Failed.

First always check if Opsmgr discover all the data from the DPM servers. You can see all dicoverd information if you go to monitoring and expand the Management Pack “Data Protection Manager”.
By selecting “DPM Server State” you must see all the data from you DPM servers. If Discovery Fails you don’t see de DPM Servion, Number of protection Groups, ect.
When you monitor the Operation Manager eventlog on the DPM Servers you will see Eventid 21406.

Eventid 21406

The process started at 13:03:17 failed to create System.Discovery.Data. Errors found in output:
 
C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\8332\DPMDataDiscovery.vbs(274, 1) Microsoft VBScript runtime error: Object required: ‘root’
Command executed: “C:\Windows\system32\cscript.exe” /nologo “DPMDataDiscovery.vbs” 0 {E776E9E1-CAAE-A72D-350D-C65CABF15D80} {28275A4B-D281-0E8B-C594-250955B2928B} “dpm servername”
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\8332\
One or more workflows were affected by this.
 
Workflow name: Microsoft.Windows.SystemCenterDPM2010.DPMDataDiscovery
Instance name: “dpm servername”
Instance ID: {28275A4B-D281-0E8B-C594-250955B2928B}
 

The Problem is that you use an “&” string in a name of one of the protection Groups.
Change the name of the protection Group where you have used an “&” symbol . Restart the “System Center Management” and you should see that the discovery success.


Leave a Reply

You must be logged in to post a comment.