Hi all, I had configured SCOM and SCVMM integration a couple of years ago and it worked corretly. During the last year i have udgrade my servers to 2008 r2 sp1 and scvmm 2008 r2 to sp1 and harden the server. when i made this changes i checked everything else exept pro tips. Now after 4-5 months after the chages i have made, i notice that the pro tips is not working. Even in 2008 r2 virtual machines view ias not showing anyhtin in SCOM.MCSE, MCTS, VCP, AIS, MCITP

suppose you also need to update SCVMM management packs to SP1. they are located on SCVMM installation media.

i have already update the management pack from scvmm media. i also run this command 'set-vmmserver -opsmgrservername' and it looks like after this command work half of feature of pro-tips and then not worj, on virtual machine manager management pack view i see nothing . only on self-service view of vm management pack in scom i see my vmm server as healthy. i cannot find any errors in event logs of scom or vmm serverMCSE, MCTS, VCP, AIS, MCITP

i'm guessing, if you set blank RMS name in VMM console, and then check SCOM console->connectors. Do you see any connectors from VMM? if, yes, try to remove them http://support.microsoft.com/kb/2626670 and then set RMS name back in VMM console

Dear pavel, When i remove RMS server form vmm console i can see all connector disapearing from SCOM . When i set back i can see all connector comming back. I was wrong about the errors. I can see some warings in VMM server, the warnings are below event id:11807 Operations Manager discovery failed with error: "Invalid relationship source specified in the discovery data item. I think i am close to this situation here : http://social.technet.microsoft.com/Forums/en-US/operationsmanagerauthoring/thread/bb0f3dcd-d486-4689-b112-0bc29d12a515/ MCSE, MCTS, VCP, AIS, MCITP

Operations Manager discovery failed with error: "Invalid relationship source specified in the discovery data item. RelationshipSourceBaseManagedEntityId: ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd RuleId: 234146b5-80d5-4ff1-a53a-150b27cd03b4 Instance: <?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{6284518a-90cc-fadd-e56b-26669e2a0a8f}" SourceTypeId="{ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd}" TargetTypeId="{a73de8ad-2f02-a15c-52d9-da4fbb6cb8b3}"><Settings /><SourceRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting><Setting><Name>1fad4376-0d14-a50b-a0e8-5a96e97bc881</Name><Value>8b4c9dd0-24c2-4e89-ae95-0de299d25edc</Value></Setting></Settings></TargetRole></RelationshipInstance>". MCSE, MCTS, VCP, AIS, MCITP

interesting <RelationshipInstance TypeId="{6284518a-90cc-fadd-e56b-26669e2a0a8f}" SourceTypeId="{ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd}" TargetTypeId="{a73de8ad-2f02-a15c-52d9-da4fbb6cb8b3}"> <Settings /> <SourceRole> <Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting></Settings> </SourceRole> <TargetRole> <Settings> <Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting> <Setting><Name>1fad4376-0d14-a50b-a0e8-5a96e97bc881</Name><Value>8b4c9dd0-24c2-4e89-ae95-0de299d25edc</Value></Setting> </Settings> </TargetRole> </RelationshipInstance> Get-RelationshipClass -id 6284518a-90cc-fadd-e56b-26669e2a0a8f => Microsoft.Windows.ComputerHostsComputerRole Get-MonitoringClass -id ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd => Microsoft.Windows.Computer Get-MonitoringClass -id a73de8ad-2f02-a15c-52d9-da4fbb6cb8b3 =>Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.ManagedHost.HyperV (PRO Hyper-V Host Target) looking into xml, discovery tries to paste xml with Source=Target=5c324096-d928-76db-e9e7-e629dcc261b1 what is 5c324096-d928-76db-e9e7-e629dcc261b1? Get-MonitoringObject -id 5c324096-d928-76db-e9e7-e629dcc261b1 and what is discovery rule? Get-Rule -id 234146b5-80d5-4ff1-a53a-150b27cd03b4

i will run the commands tomorrow and paste it here. i think is vhd file in vmm library that does not exist.MCSE, MCTS, VCP, AIS, MCITP

Hi, Since the issue occurs after the VMM upgrading, please also see the following document: How to Update Your Operations Manager Integration After Upgrading to VMM 2008 R2 SP1 http://technet.microsoft.com/en-us/library/gg318083.aspx I also noticed the following thread which is about a similar error and would like to share it with you for your reference: Problem on integration VMM 2008 r2 with SCOM 2007 R2 http://social.technet.microsoft.com/Forums/en/virtualmachinemgrproscintegration/thread/3ebced61-c37a-494e-bc33-abd2862e3637 Hope this helps. Thanks.Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Since the issue occurs after the VMM upgrading, please also see the following document: How to Update Your Operations Manager Integration After Upgrading to VMM 2008 R2 SP1 http://technet.microsoft.com/en-us/library/gg318083.aspx I also noticed the following thread which is about a similar error and would like to share it with you for your reference: Problem on integration VMM 2008 r2 with SCOM 2007 R2 http://social.technet.microsoft.com/Forums/en/virtualmachinemgrproscintegration/thread/3ebced61-c37a-494e-bc33-abd2862e3637 Hope this helps. Thanks.Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks Nicolas i have already read these posts.MCSE, MCTS, VCP, AIS, MCITP

>Get-MonitoringObject -id 5c324096-d928-76db-e9e7-e629dcc261b1 Get-MonitoringObject : A MonitoringObject with an identifier matching the 'Id' para meter was not found. At line:1 char:21 + Get-MonitoringObject <<<< -id 5c324096-d928-76db-e9e7-e629dcc261b1 + CategoryInfo : InvalidArgument: (5c324096-d928-76db-e9e7-e629dcc261 b1:Guid) [Get-MonitoringObject], ObjectNotFoundException + FullyQualifiedErrorId : InvalidParameter,Microsoft.EnterpriseManagement.Oper ationsManager.ClientShell.GetMonitoringObjectCmdlet -Rule -id 234146b5-80d5-4ff1-a53a-150b27cd03b4 Rule : A Rule with an identifier matching the 'Id' parameter was not found. ine:1 char:9 t-Rule <<<< -id 234146b5-80d5-4ff1-a53a-150b27cd03b4 + CategoryInfo : InvalidArgument: (234146b5-80d5-4ff1-a53a-150b27cd03 4:Guid) [Get-Rule], ObjectNotFoundException + FullyQualifiedErrorId : InvalidParameter,Microsoft.EnterpriseManagement.Oper tionsManager.ClientShell.GetRuleCmdletMCSE, MCTS, VCP, AIS, MCITP

I also see this warning. but i do have this 2.0.4521.0 mp version installed Discovery of one or more Virtual Machine Manager objects monitored by Operations Manager 2007 failed. This might be caused by a missing or outdated version of the System Center Virtual Machine Manager 2008 R2 Management Pack in Operations Manager 2007. To download version 2.0.4521.0 of the management pack, open the System MCSE, MCTS, VCP, AIS, MCITP

phantom records generated by ghosts :) if you remove integration on VMM side, remove all VMM MPs do you still see these errors on SCOM side?

i CANNOT REMOVE ALL OF THEM AS IT HAS DEPENDECIES ON DEFAULT MANAGEMENT PACKMCSE, MCTS, VCP, AIS, MCITP

Ok i delete all vmm mp and import the vmm mp from vmm 2008 R2 SP1 cd again, and the same error again Operations Manager discovery failed with error: "Invalid relationship source specified in the discovery data item. RelationshipSourceBaseManagedEntityId: ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd RuleId: ab4a6ed4-3c54-4984-ac63-bc7c2ad6aa79 Instance: <?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{6284518a-90cc-fadd-e56b-26669e2a0a8f}" SourceTypeId="{ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd}" TargetTypeId="{a73de8ad-2f02-a15c-52d9-da4fbb6cb8b3}"><Settings /><SourceRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting><Setting><Name>1fad4376-0d14-a50b-a0e8-5a96e97bc881</Name><Value>8b4c9dd0-24c2-4e89-ae95-0de299d25edc</Value></Setting></Settings></TargetRole></RelationshipInstance>". MCSE, MCTS, VCP, AIS, MCITP

From SCOM server i see these events An exception was thrown while processing ProcessDiscoveryData for session id uuid:dde86de1-1df6-450c-abb0-652b2ec6b364;id=53. Exception Message: The creator of this fault did not specify a Reason. Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceException: Invalid relationship source specified in the discovery data item. RelationshipSourceBaseManagedEntityId: ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd RuleId: ab4a6ed4-3c54-4984-ac63-bc7c2ad6aa79 Instance: <?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{6284518a-90cc-fadd-e56b-26669e2a0a8f}" SourceTypeId="{ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd}" TargetTypeId="{a73de8ad-2f02-a15c-52d9-da4fbb6cb8b3}"><Settings /><SourceRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting><Setting><Name>1fad4376-0d14-a50b-a0e8-5a96e97bc881</Name><Value>8b4c9dd0-24c2-4e89-ae95-0de299d25edc</Value></Setting></Settings></TargetRole></RelationshipInstance> at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryDataProcessor.UpsertRelationshipInstance(DiscoveryDatabase...). MCSE, MCTS, VCP, AIS, MCITP

Data Access Layer rejected retry on SqlError: Request: p_RelationshipDiscovered -- (RelationshipId=3f0f0598-ea2e-4ea2-8cbc-1fd05a6bd50f), (SourceEntityId=ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd), (TargetEntityId=319679a5-fc8a-4142-46be-f6ee575db01f), (RelationshipTypeId=6284518a-90cc-fadd-e56b-26669e2a0a8f), (DiscoverySourceId=ab4a6ed4-3c54-4984-ac63-bc7c2ad6aa79), (HealthServiceEntityId=d2132ee8-3639-7a0b-36ad-1440d2066eb4), (PerformHealthServiceCheck=False), (TimeGenerated=16/11/2011 11:28:39 am), (RETURN_VALUE=1) Class: 16 Number: 777980002 Message: The specified relationship doesn't have a valid source. MCSE, MCTS, VCP, AIS, MCITP

dear pavel, i have finaly found that this id: 8b4c9dd0-24c2-4e89-ae95-0de299d25edc is a vhd file, and i removed from scvmm. After i remove i dont see those errors any more, i waited about 10 min and open scom console, i open scvmm view and again all views are empty, only on self service scvmm view i can se my scvmm server as healthy, it needs more for scvmm to publish the information to scom? I will check tomorrow againMCSE, MCTS, VCP, AIS, MCITP

dear pavel, i have finaly found that this id: 8b4c9dd0-24c2-4e89-ae95-0de299d25edc is a vhd file, and i removed from scvmm. After i remove i dont see those errors any more, i waited about 10 min and open scom console, i open scvmm view and again all views are empty, only on self service scvmm view i can se my scvmm server as healthy, it needs more time for scvmm to publish the information to scom? I will check tomorrow again MCSE, MCTS, VCP, AIS, MCITP

Ok i discover that if i remove some standalone hosts the pro tips start to work. tries to find on these stand alone host some vhd files that does not exist anymore. Do you have any sugestions?MCSE, MCTS, VCP, AIS, MCITP

i have not figure out how to fix the problem yet. scvmm or scom have some not correct id for some stand alone hyperv hosts.MCSE, MCTS, VCP, AIS, MCITP

thinking about ghost records (i'm not kidding) you may try as last option: remove integration remove SCVMM MPs wait two days for SCOM to groom marked for deletion objects revive integration

thanks, i will try it and post backMCSE, MCTS, VCP, AIS, MCITP

SAME ERROR AGAIN Operations Manager discovery failed with error: "Invalid relationship source specified in the discovery data item. RelationshipSourceBaseManagedEntityId: ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd RuleId: 9aa6f6bc-dc26-4b77-a6d2-bf7295cf7900 Instance: <?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{6284518a-90cc-fadd-e56b-26669e2a0a8f}" SourceTypeId="{ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd}" TargetTypeId="{a73de8ad-2f02-a15c-52d9-da4fbb6cb8b3}"><Settings /><SourceRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name></Setting><Setting><Name>1fad4376-0d14-a50b-a0e8-5a96e97bc881</Name><Value>f61ff6ce-120e-4c6a-bcbe-dcd5f75c4f84</Value></Setting></Settings></TargetRole></RelationshipInstance>". MCSE, MCTS, VCP, AIS, MCITP