Hey everyone...

I'm getting this wierd error message in the application log of my crm server:

Event Type: Error
Event Source: MSCRMAsyncService
Event Category: None
Event ID: 17415
Date: 2/4/2008
Time: 12:01:47 PM
User: N/A
Computer: MyCrmServer
Description:
Host MyCrmServer: error while processing organization
c6633e81-f7c9-dc11-89d1-0003fff66785. Exception:
Microsoft.Crm.Metadata.EntityMetadataNotFoundExcep tion: The entity with
ObjectTypeCode = 0 was not found in the MetadataCache.
at Microsoft.Crm.Metadata.DynamicMetadataCache.GetEnt ity(Int32 entityCode)
at
Microsoft.Crm.Asynchronous.QueueDataAccess.GetEnti tyLogicalNameFromObjectTypeCode(Int32 objectTypeCode)
at Microsoft.Crm.Asynchronous.QueueDataAccess.GetLook up(Object objectId,
String objectIdName, Int32 objectDsc, Int32 objectTypeCode)
at
Microsoft.Crm.Asynchronous.QueueDataAccess.<>c__Di splayClass2.<SelectEvents>b__0(Object[] values)
at
Microsoft.Crm.Asynchronous.DataAccessBase.ExecuteS qlCommandAndProcessRecords(IDbCommand command, RecordProcessor recordProcessor)
at Microsoft.Crm.Asynchronous.QueueDataAccess.SelectE vents(Int32
numberOfEvents)

......

This error pops each time the service restarts; 4-5 times if I boot the
server.
The ORGANIZATION in the error log msg is the active organization I'm
running, and the guid is correct; what I don't understand is this part of the
log: "The entity with ObjectTypeCode = 0 was not found in the MetadataCache."

If you look at the Entity view in SQL Server, there are precisely *zero*
entity types with ObjectTypeCode = 0, so it seems this service would *always*
fail....

any ideas out there?

Thanks!

--
Rusty

Hi Rusty
Can you run the below query and send the results. By looking at the code, we
noticed that your database seems to be in an inconsistent state where you
have any Asyncoperation where the regardingobjectid is set but the
regardingobjecttypecode is Null.

select statecode,statuscode,operationtype from
asyncoperationbase where regardingobjectid is not null
AND regardingobjecttypecode is NULL

Have you directly updated any values in the AsyncOperation Table? Is this an
upgraded environment?
Thanks
Noor

"Rusty" wrote:

Hello,

I had the same issue.

What worked for me - I cleaned all workflow tasks, all import tasks and all
duplicate deletion jobs as well.

After that deleting/canceling - no more such event log entries appears and
no more waiting imports.

"Rusty" <Rusty@discussions.microsoft.com> pÃ*Å¡e v diskusnÃ*m pÅ™Ã*spÄ›vku
news:B74268B0-4E18-46CC-984C-AAB4C038D25C@microsoft.com...

Hi Rusyt , the organization that generated this error was it imported?

On Feb 4, 1:46*pm, Rusty <Ru...@discussions.microsoft.com> wrote:

I have the same.
I was upgrading from the 3.0.
Some workflow is not working properly.
In my case the error disappear in few sec as the log shows 17416 server
resolved the error.

Any idea?

url:http://www.ureader.com/msg/126511011.aspx

I had the same issue. Cancelling and deleting workflow tasks worked for me.

I did have an imported org.

On Apr 6, 8:28*pm, jexia <je...@discussions.microsoft.com> wrote:
http://support.microsoft.com/kb/950680