During my Masterclass last monday I showcased the different integration possibilities between the different system center products. One of the integrations I showcased was the integrations between SCVMM 2012 to SCOM2012.

I followed all the different steps to get things up and running but when I wanted to test the actual PRO integration service I found I had an issue.

The connection details showed an error:

“Operations Manager discovery failed with error: “Exception of type ‘Microsoft.VirtualManager.EnterpriseManagement.common.discoverydatainvalidrelationshipsourceexceptionOM10’ was thrown.

 

SNAG-0001

Talking about a strange error message. I checked my SCVMM jobs but nothing was out of order.

Reboot of the machine also did not solve the issue. Well here is actually how I solved the issue by following a rather strange trick.

Solution:

Deselect both “Enable PRO” and “Enable Maintenance mode integration” and click refresh.

SNAG-0002

Now the connection is OK to my Opsmgr environment.

Well let’s continue with testing my PRO by enabling it and refreshing.

SNAG-0003

Error 25922 “PRO Diagnostics Target cannot be found” was thrown. A refresh of the connection once more and this was solved.

SNAG-0004

Error 25923 “PRO Diagnostics Target is not monitored” was thrown. Apparently there was still no SCOM 2012 agent on the SCVMM server due to the fact that it was not yet switched over to the new SCOM2012 environment. So pushed the agent.

SNAG-0003

After the SCOM agent was pushed another try was successful to initiate a test PRO towards scom and the message appeared in the console:

SNAG-0005SNAG-0006 

A good resource to troubleshoot the error messages can be found here:

http://social.technet.microsoft.com/wiki/contents/articles/4929.system-center-2012-virtual-machine-manager-vmm-error-codes-25000-25999.aspx

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.