Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Host <host>: error while processing organization <organization>.
Exception: Microsoft.Crm.Metadata.EntityMetadataNotFoundException: The entity with ObjectTypeCode = 0 was not found in the MetadataCache.
at Microsoft.Crm.Metadata.DynamicMetadataCache.GetEntity(Int32 entityCode)
at Microsoft.Crm.Asynchronous.QueueDataAccess.GetEntityLogicalNameFromObjectTypeCode(Int32 objectTypeCode)
at Microsoft.Crm.Asynchronous.QueueDataAccess.GetLookup(Object objectId, String objectIdName, Int32 objectDsc, Int32 objectTypeCode)
at Microsoft.Crm.Asynchronous.QueueDataAccess.<>c__DisplayClass2.<SelectEvents>b__0(Object values)
at Microsoft.Crm.Asynchronous.DataAccessBase.ExecuteSqlCommandAndProcessRecords(IDbCommand command, RecordProcessor recordProcessor)
at Microsoft.Crm.Asynchronous.QueueDataAccess.SelectEvents(Int32 numberOfEvents).
|English: Request a translation of the event description in plain English.|
This event can be recorded in various conditions. Attention should be paid to the actual "Exception" error message which indicates the actual problem:
Exception: System.Data.SqlClient.SqlException: Transaction (Process ID ..) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. - According to ME975490, this problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. Some support forum posts indicate that this might be a transitory error that can be expected from time to time (but the server should record another event saying that the deadlock has been resolved).
See EV100308 (CRM Trace File Viewer) for a tool that can help with the CRM troubleshooting. ME907490 provides information on how to enable tracing in Microsoft Dynamics CRM.
Exception: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) - According to a support forum: Check if you don't have any problems with network layer. You may increase in Dynamics CRM timeout based on the instructions described on EV100309 (Timeout during heavy loaded tasks on CRM 4) but I suggest to check connectivity with sql server - ping time, network configuration etc.
Exception: Microsoft.Crm.Metadata.EntityMetadataNotFoundException: The entity with ObjectTypeCode = 0 was not found in the MetadataCache. - This was reported as being recorded after a failed upgraded from 3.0 to 4.0. The suggested solution was to restore the CRM 3.0 server and reattempt to upgrade.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated