Quantcast
Channel: Operations Manager - General forum
Viewing all articles
Browse latest Browse all 11941

Event 2115 and 31551 generated

$
0
0

Hi All

I know there is much information relating to the two event IDs above, mainly relating to performance issues.

Essentially, I am seeing the above Event ID for the following Workflows:

  • Microsoft.SystemCenter.DataWarehouse.CollectEventData
  • Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData
  • Microsoft.SystemCenter.DataWarehouse.Synchronization.ManagedEntity
  • Microsoft.SystemCenter.DataWarehouse.Synchronization.DomainSnapshot 

There are others, but these are the main ones.  However it is the content of the message that is interesting.  E.g.

Log Name:      Operations Manager
Source:        Health Service Modules
Date:          22/01/2014 13:14:50
Event ID:      31551
Task Category: Data Warehouse
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <SERVER>
Description:
Failed to store data in the Data Warehouse. The operation will be retried.
Exception 'SqlException': Sql execution failed. Error 6602, Level 16, State 2, Procedure sp_xml_preparedocument, Line 1, Message: The error description is 'End tag 'ResolutionStateId' does not match the start tag 'nStateId'.'.
The XML parse error 0xc00ce56d occurred on line number 1, near the XML text "<Root><Item><DomainName>ResolutionState</DomainName><DomainContentXml><Root><ResolutionState><ResolutionStateId>254</ResolutionStateId><ResolutionStateGuid>497186A1-5606-4B0C-91C1-30BA37232A82</ResolutionStateGuid><ResolutionStateName>Resolved</ResolutionStateName><PredefinedInd>1</PredefinedInd><CreatedDateTime>2013-10-09T16:43:58.353</CreatedDateTime><LastModifiedDateTime>2013-10-09T16:43:58.353</LastModifiedDateTime></ResolutionState><ResolutionState><ResolutionStateId>247</ResolutionStateId><ResolutionStateGuid>F791ED45-DCB4-475F-8A36-539A9CA8E495</ResolutionStateGuid><ResolutionStateName>Awaiting Evidence</ResolutionStateName><PredefinedInd>1</PredefinedInd><CreatedDateTime>2013-10-09T16:43:58.353</CreatedDateTime><LastModifiedDateTime>2013-10-09T16:43:58.353</LastModifiedDateTime></ResolutionState><ResolutionState><nStateId>254</ResolutionStateId><ResolutionStateGuid>497186A1-5606-4B0C-91C1-30BA37232A82</ResolutionStateGuid><ResolutionStateName>Resolved</ResolutionStateName><PredefinedInd>1</PredefinedI". 

One or more workflows were affected by this.  

Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.DomainSnapshot 
Instance name: eb249cfa-4f62-4bd9-a181-a6641d78ebd9 
Instance ID: {1600518F-0CD5-5385-5C79-AABC665ED81B} 
Management group: <MG>

Log Name:      Operations Manager
Source:        Health Service Modules
Date:          22/01/2014 13:14:43
Event ID:      31551
Task Category: Data Warehouse
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <SERVER>
Description:
Failed to store data in the Data Warehouse. The operation will be retried.
Exception 'SqlException': XML parsing: line 1, character 108, illegal xml character 

One or more workflows were affected by this.  

Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectEventData 
Instance name: <SERVER>
Instance ID: {4629E455-0F9F-6EF9-4761-6D8BC5F0DCCA} 
Management group: <MG>

Log Name:      Operations Manager
Source:        Health Service Modules
Date:          22/01/2014 13:14:23
Event ID:      31551
Task Category: Data Warehouse
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     <SERVER>
Description:
Failed to store data in the Data Warehouse. The operation will be retried.
Exception 'SqlException': OLE DB provider 'STREAM' for linked server '(null)' returned invalid data for column '[!BulkInsert].DateTime'. 

One or more workflows were affected by this.  

Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData 
Instance name: <SERVER>
Instance ID: {4629E455-0F9F-6EF9-4761-6D8BC5F0DCCA} 
Management group: <MG>

I have looked at the relevent performance stats on the SQL Server hosting the DW Database.  I can confirm that Disk queues are consistently zero, and that idletime never drops below 98%.

It's probably worth noting that the above started happening following the DW database running out of space.  More space was allocate to the disk and the database files were expanded.  However, the above is now occurring.

Anyone have any idea what might be the cause?

Cheers

Shaun


Viewing all articles
Browse latest Browse all 11941

Trending Articles