locked
CrmAsyncService.exe 100 % CPU RRS feed

  • Question

  • Hi,

    I have a MS CRM 4.0 running. I did not do much of customization or installed any plugins.
    The CrmAsyncService uses 100% of the CPU. There is nothing in the event log about a problem.
    I started the SQL Server profiler. There seams to be an endless loop:

    Code Snippet

    exec sp_executesql N'delete from WorkflowWaitSubscriptionBase where WorkflowWaitSubscriptionId = @subscriptionId',N'@subscriptionId uniqueidentifier',@subscriptionId='00753318-EEC1-DD11-B7B5-00188BE6BCAC' exec sp_executesql N'insert into WorkflowWaitSubscriptionBase (WorkflowWaitSubscriptionId, AsyncOperationId, EntityName, EntityId, IsModified, ModifiedOn, Data) values (@workflowWaitSubscriptionId, @asyncOperationId, @entityName, @entityId, @isModified, GETUTCDATE(), @data)',N'@workflowWaitSubscriptionId uniqueidentifier,@asyncOperationId uniqueidentifier,@entityName nvarchar(4),@entityId uniqueidentifier,@isModified bit,@data nvarchar(36)',@workflowWaitSubscriptionId='01753318-EEC1-DD11-B7B5-00188BE6BCAC', @asyncOperationId='C3C89B3E-83B5-DD11-8255-00188BE6BCAC',@entityName=N'lead', @entityId='C1C89B3E-83B5-DD11-8255-00188BE6BCAC',@isModified=0,@data=N'a728f50e-5cff-4b4d-a525-1f042262d34a'

    Code Snippet


    exec sp_executesql N'insert into WorkflowWaitSubscriptionBase (WorkflowWaitSubscriptionId, AsyncOperationId, EntityName, EntityId, IsModified, ModifiedOn, Data) values (@workflowWaitSubscriptionId, @asyncOperationId, @entityName, @entityId, @isModified, GETUTCDATE(), @data)',N'@workflowWaitSubscriptionId uniqueidentifier,@asyncOperationId uniqueidentifier,@entityName nvarchar(4),@entityId uniqueidentifier,@isModified bit,@data nvarchar(36)',@workflowWaitSubscriptionId='02753318-EEC1-DD11-B7B5-00188BE6BCAC', @asyncOperationId='47EB1D68-87B5-DD11-8255-00188BE6BCAC',@entityName=N'lead', @entityId='45EB1D68-87B5-DD11-8255-00188BE6BCAC',@isModified=0,@data=N'8e167293-bce7-4a36-b916-5950058563cf

    '
    Code Snippet


    exec sp_executesql N'select lead0.FullName as ''fullname'', lead0.Telephone1 as ''telephone1'', lead0.LeadId as ''leadid'', lead0.LastName as ''lastname'', lead0.CreatedBy as ''createdby'', lead0.CreatedOn as ''createdon'', lead0.StateCode as ''statecode'', lead0.OwnerId as ''ownerid'', lead0.CompanyName as ''companyname'', lead0.CreatedByYomiName as ''createdbyyominame'', lead0.CreatedByName as ''createdbyname'', lead0.CreatedByDsc as ''createdbydsc'', lead0.OwnerIdName as ''owneridname'', lead0.OwnerIdType as ''owneridtype'', lead0.OwnerIdYomiName as ''owneridyominame'', lead0.OwnerIdDsc as ''owneriddsc'', lead0.OwningBusinessUnit as ''owningbusinessunit'', lead0.OwningUser as ''owninguser'' from Lead as lead0 where ((lead0.DeletionStateCode in (@DeletionStateCode0)) and lead0.LeadId = @LeadId0)',N'@DeletionStateCode0 int,@LeadId0 uniqueidentifier',@DeletionStateCode0=0,@LeadId0='C1C89B3E-83B5-DD11-8255-00188BE6BCAC


    '


    It repeats this every second.
    Does anybody have an idea what I can do?

    Marek
    Thursday, December 4, 2008 10:59 AM

Answers

  • Hi,

    Looks like there is a workflow processed in the background. You can check through Settings->System Jobs and see whether there is any workflows running/failed in the background.

    Regards,

    hadi teo.
    Thursday, December 4, 2008 2:27 PM
  • Hey Hadi,

    thank you for your answer! I looked at this screen several times before and there were no problematic job. After I did a bulkdelete on the logs, there was a workflow running. I stopped it and my problem stopped.

    Marek
    Thursday, December 4, 2008 4:15 PM

All replies

  • Hi,

    Looks like there is a workflow processed in the background. You can check through Settings->System Jobs and see whether there is any workflows running/failed in the background.

    Regards,

    hadi teo.
    Thursday, December 4, 2008 2:27 PM
  • Hey Hadi,

    thank you for your answer! I looked at this screen several times before and there were no problematic job. After I did a bulkdelete on the logs, there was a workflow running. I stopped it and my problem stopped.

    Marek
    Thursday, December 4, 2008 4:15 PM