I am starting to get the following errors in my MS server. Log Name: Operations Manager Source: DataAccessLayer Date: 6/4/2013 11:10:02 AM Event ID: 33333 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: ms1.mtsallstream.com Description: Data Access Layer rejected retry on SqlError: Request: p_RelationshipDiscovered -- (RelationshipId=06ba2731-bae8-4565-08c6-32399973114e), (SourceEntityId=1044a599-635b-0816-9b22-f97111026d35), (TargetEntityId=513b6f03-cf20-98e6-3d8b-5417e7890bb7), (RelationshipTypeId=0c18d101-8d27-4333-6d54-682fe19a5896), (DiscoverySourceId=40455d17-52b3-9fe5-588e-df368451a907), (HealthServiceEntityId=3c6c0d7a-c2a9-ab48-450b-dd43f9093ba9), (PerformHealthServiceCheck=True), (TimeGenerated=6/4/2013 4:09:34 PM), (RETURN_VALUE=1) Class: 16 Number: 777980002 Message: The specified relationship doesn't have a valid source. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="DataAccessLayer" /> <EventID Qualifiers="32768">33333</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2013-06-04T16:10:02.000000000Z" /> <EventRecordID>302182</EventRecordID> <Channel>Operations Manager</Channel> <Computer>crdmt011.mtsallstream.com</Computer> <Security /> </System> <EventData> <Data>p_RelationshipDiscovered -- (RelationshipId=06ba2731-bae8-4565-08c6-32399973114e), (SourceEntityId=1044a599-635b-0816-9b22-f97111026d35), (TargetEntityId=513b6f03-cf20-98e6-3d8b-5417e7890bb7), (RelationshipTypeId=0c18d101-8d27-4333-6d54-682fe19a5896), (DiscoverySourceId=40455d17-52b3-9fe5-588e-df368451a907), (HealthServiceEntityId=3c6c0d7a-c2a9-ab48-450b-dd43f9093ba9), (PerformHealthServiceCheck=True), (TimeGenerated=6/4/2013 4:09:34 PM), (RETURN_VALUE=1)</Data> <Data>16</Data> <Data>777980002</Data> <Data>The specified relationship doesn't have a valid source.</Data> </EventData> </Event> Log Name: Operations Manager Source: Health Service Modules Date: 6/4/2013 11:10:02 AM Event ID: 10801 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ms1.mtsallstream.com Description: Discovery data couldn't be inserted to the database. This could have happened because of one of the following reasons: - Discovery data is stale. The discovery data is generated by an MP recently deleted. - Database connectivity problems or database running out of space. - Discovery data received is not valid. The following details should help to further diagnose: DiscoveryId: a344fd27-6d81-6a3b-7b9f-e9e55778465e HealthServiceId: 3c6c0d7a-c2a9-ab48-450b-dd43f9093ba9 Invalid relationship source specified in the discovery data item. RelationshipSourceBaseManagedEntityId: 1044a599-635b-0816-9b22-f97111026d35 RuleId: a344fd27-6d81-6a3b-7b9f-e9e55778465e Instance: <?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{0c18d101-8d27-4333-6d54-682fe19a5896}" SourceTypeId="{387eadfe-1fde-623d-015a-cd39a8b40d55}" TargetTypeId="{02c5162c-b89f-1d61-349a-9b0667fbd60e}"><Settings /><SourceRole><Settings><Setting><Name>f0721862-8f99-78b7-6ede-936326423438</Name><Value>MTSAEXN.COM</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>f0721862-8f99-78b7-6ede-936326423438</Name><Value>MTSAEXN.COM</Value></Setting><Setting><Name>7a7a1247-5661-8a5f-4262-dc42bbdcf5b9</Name><Value>MTSAEXN\TJ1EXNDC01</Value></Setting></Settings></TargetRole></RelationshipInstance>. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Health Service Modules" /> <EventID Qualifiers="0">10801</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2013-06-04T16:10:02.000000000Z" /> <EventRecordID>302183</EventRecordID> <Channel>Operations Manager</Channel> <Computer>crdmt011.mtsallstream.com</Computer> <Security /> </System> <EventData> <Data>a344fd27-6d81-6a3b-7b9f-e9e55778465e</Data> <Data>3c6c0d7a-c2a9-ab48-450b-dd43f9093ba9</Data> <Data>Invalid relationship source specified in the discovery data item. RelationshipSourceBaseManagedEntityId: 1044a599-635b-0816-9b22-f97111026d35 RuleId: a344fd27-6d81-6a3b-7b9f-e9e55778465e Instance: &lt;?xml version="1.0" encoding="utf-16"?&gt;&lt;RelationshipInstance TypeId="{0c18d101-8d27-4333-6d54-682fe19a5896}" SourceTypeId="{387eadfe-1fde-623d-015a-cd39a8b40d55}" TargetTypeId="{02c5162c-b89f-1d61-349a-9b0667fbd60e}"&gt;&lt;Settings /&gt;&lt;SourceRole&gt;&lt;Settings&gt;&lt;Setting&gt;&lt;Name&gt;f0721862-8f99-78b7-6ede-936326423438&lt;/Name&gt;&lt;Value&gt;MTSAEXN.COM&lt;/Value&gt;&lt;/Setting&gt;&lt;/Settings&gt;&lt;/SourceRole&gt;&lt;TargetRole&gt;&lt;Settings&gt;&lt;Setting&gt;&lt;Name&gt;f0721862-8f99-78b7-6ede-936326423438&lt;/Name&gt;&lt;Value&gt;MTSAEXN.COM&lt;/Value&gt;&lt;/Setting&gt;&lt;Setting&gt;&lt;Name&gt;7a7a1247-5661-8a5f-4262-dc42bbdcf5b9&lt;/Name&gt;&lt;Value&gt;MTSAEXN\TJ1EXNDC01&lt;/Value&gt;&lt;/Setting&gt;&lt;/Settings&gt;&lt;/TargetRole&gt;&lt;/RelationshipInstance&gt;</Data> </EventData> </Event> they are coming from domain controllers in another domain through a gateway. All DC's are proxy enabled. Broker is enabled on the opsmgr database. I have made quite a few changes in my environment recently as i am prepping for scom 2012 upgrade. Changes that have been made are: - gateway is now pointing to MS that is getting the errors instead of RMS. - Operations database moved to it's own physical server. - cu7 applied to all management server. SQL scripts have been run - scom 2012 agents have been manually installed on all servers in the external domain. Any ideas lars

Proxy has been enabled on all clusters and exchange servers toolars

"The specified relationship doesn't have a valid source." means the source entity of the relationship is not there when the relationship is being inserted. You can use the following query to find if the relationship and source entity of the relationship is there now: select * from relationship where relationshipid = '06ba2731-bae8-4565-08c6-32399973114e' select * from basemanagedentity where basemanagedentityid = '1044a599-635b-0816-9b22-f97111026d35' If it is still not there, use the following query to find out which MP and rule sent the data, you will have to ask that MP's expert to find out more. select d.DiscoveryName, b.FullName, mp.MPName from discoverysource ds inner join discovery d on ds.DiscoveryRuleId = d.DiscoveryId inner join BaseManagedEntity b on ds.BoundManagedEntityId = b.BaseManagedEntityId inner join ManagementPack mp on d.ManagementPackId = mp.ManagementPackId and DiscoverySourceId like '40455d17-52b3-9fe5-588e-df368451a907'

Just a thought.....Is the performance of your Management servers OK, or do they max out? Had a similar issue recently that was eventually solved by redistributing the agents to the Management Servers in the group. JB

In many situations this error is caused by the fact that proxying is not enabled for a particular agent. You can figure out using powershell the name of the agent that requires proxying to be enabled using the following command: Get-MonitoringObject -id:'2090A6E7-27D2-425F-5617-6EE7B2291970' | ft DisplayName This will provide the name of the agent that needs to have proxying enabled. Note: You will need to replace the GUID that you use as the parameter to the cmdlet with the first GUID that you see in the alert." Roger

In many situations this error is caused by the fact that proxying is not enabled for a particular agent. You can figure out using powershell the name of the agent that requires proxying to be enabled using the following command: Get-MonitoringObject -id:'2090A6E7-27D2-425F-5617-6EE7B2291970' | ft DisplayName This will provide the name of the agent that needs to have proxying enabled. Note: You will need to replace the GUID that you use as the parameter to the cmdlet with the first GUID that you see in the alert." Roger

All servers have proxy enabled, RMS and MS have lot of cpu\memory. I eventually just turned off the 2008 domain controller discovery policy for the servers exhibiting the problem and the errors disapeared. Thanks for your helplars