From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of George Maloy
Sent: Tuesday, December 22, 2009 6:24 PM
To: msmom@lists.myitforum.com
Subject: RE: [msmom] Error on management server
I opened a case with MS Support as I was seeing this in Event ID 10860 on one of my management servers.
We found by querying for the entity ID what servers were causing these and repaired those server to resolve the issue.
I had a handful of agents that were not updated correctly with all the latest MP and configurations and thus causing this error.
1- First we stopped the Health service on the management server
2- Cleared all of the local cache files and folders on the management server that was having the error
3- Then cleared and flushed the cache on the offending agents
4- Then Ran a repair on each offending agent.
George Maloy
Sr. Systems Engineer | SMCE
601 108th Ave NE | Suite 900 |Bellevue, WA 98004
"Powering the Mobile Lifestyle"
www.motricity.com
(425) 638-8657 - Office
(206) 420-9334 - Mobile
(425) 957-6201 - Fax
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Kevin Holman
Sent: Monday, December 21, 2009 10:13 AM
To: msmom@lists.myitforum.com
Subject: RE: [msmom] Error on management server
Two things to check –
1. Make sure your Base OS MP’s are ALL the same version 6.0.6667.0 (ensuring you imported them all – and not just some of them.)
2. Make sure the Healthservice identified by the HealthServiceId inserting this data has proxy enabled.
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of George Maloy
Sent: Monday, December 21, 2009 11:53 AM
To: msmom@lists.myitforum.com
Subject: RE: [msmom] Error on management server
I am having this same issue. Did anyone respond to this issue?
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Nepal, Santosh
Sent: Wednesday, December 16, 2009 3:57 PM
To: msmom@lists.myitforum.com
Subject: [msmom] Error on management server
We started seeing this problem on our management server since this morning. Thought I would I ask the group if anyone see this before? Thank you.
A performance signature couldn't be inserted to the database. This could have happened because of one of the following reasons:
- Performance signature is stale. The performance signature is generated by an MP recently deleted.
- Database connectivity problems or database running out of space.
- Performance signature received is not valid.
The following details should help to further diagnose:
Details: RuleId:ddfa5fd4-8351-10e4-32d7-21f5ceeaf56c. HealthServiceId:4d66f9d1-16c5-3300-e70d-487ee34a4d36. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated.RuleId:1908ec9c-a5fd-dec0-9f31-bb1360d7e9ab. HealthServiceId:4d66f9d1-16c5-3300-e70d-487ee34a4d36. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated.RuleId:54642c8a-22ab-e5fe-573a-da25b43aa652. HealthServiceId:4d66f9d1-16c5-3300-e70d-487ee34a4d36. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated.RuleId:72f7ef34-9d3b-f56e-dabc-4650dad567dc. HealthServiceId:4d66f9d1-16c5-3300-e70d-487ee34a4d36. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated.RuleId:46a9a36c-5c5f-9392-1fa6-b449a7d5ab0f. HealthServiceId:4d66f9d1-16c5-3300-e70d-487ee34a4d36. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated.RuleId:3f401978-6b19-f56b-c7bb-91e9d6da4f27. HealthServiceId:4d66f9d1-16c5-3300-e70d-487ee34a4d36. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated.RuleId:60ab65a7-72dc-d9fc-5ec4-b70520fa633c. HealthServiceId:4d66f9d1-16c5-3300-e70d-487ee34a4d36. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated.RuleId:de5e6bc6-bcd5-e870-3716-1baad994e181. HealthServiceId:4d66f9d1-16c5-3300-e70d-487ee34a4d36. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated.RuleId:0de064e5-81fb-af07-529d-b471e314c6dc. HealthServiceId:4d66f9d1-16c5-3300-e70d-487ee34a4d36. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
The statement has been terminated..
Data Access Layer rejected retry on SqlError:
Request: p_PerformanceSignatureUpsert -- (ObjectName=ASP.NET Applications), (CounterName=Requests/Sec), (InstanceName=__Total__), (BaseManagedEntityId=04e25a35-a1cb-04be-70d1-f2836edf7a30), (LearningRuleId=0de064e5-81fb-af07-529d-b471e314c6dc), (BusinessCycleUnit=Week), (BusinessCycleUnitMultiplier=1), (BusinessCycleStartTime=12/13/2009 7:00:00 AM), (Sensitivity=2.81), (IsFrozen=False), (IsReset=False), (SignatureStartIndex=905), (Averages=0.118464256740279;), (Deviations=0.279737354477462;), (IsInitialized=1;), (TimeGenerated=12/16/2009 10:50:01 AM), (RETURN_VALUE=1)
Class: 16
Number: 547
Message: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PerformanceSignature_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/
