MSCRMKeyGenerator warning in the Windows event log after each Async Svc restart RRS feed

  • Question

  • Has anyone any got any ideas about the following issue please?

    Up until now: When updating a custom workflow step (for example, adding new output parameters), we update the plugin with the Registration Tool, and always have to restart the CRM Async Service before the changes become visible in the workflow editor.  The Async Service normally restarts without error.

    Now: The above procedure no longer causes the plugin updates to become visible in the workflow editor.  We now have to to run ISSRESET on the App server, for changes to become effective.  Also, we now see a Warning in the Windows event log, regarding the MSCRMKeyGenerator, after each Async Svc restart

    We are not sure what the MSCRMKeyGenerator is for, but the log entry definitely coincides with each async restart, and contains the following detail…

    Log Name:      Application

    Source:        MSCRMKeyGenerator

    Date:          26/06/2012 12:28:11

    Event ID:      18948

    Task Category: None

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      BTL-CRMPLAT01.BTL.com


    CrmKeyGenerator has stopped.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">


        <Provider Name="MSCRMKeyGenerator" />

        <EventID Qualifiers="32768">18948</EventID>




        <TimeCreated SystemTime="2012-06-26T11:28:11.000000000Z" />




        <Security />





    Wednesday, June 27, 2012 9:25 AM

All replies

  • We are getting the same exact error. Has anyone resolved this problem?
    Wednesday, August 22, 2012 3:45 PM
  • I've had nothing back on this at all, sorry. We are still none the wiser!
    Tuesday, August 28, 2012 8:15 AM
  • I don't know about the 'CrmKeyGenerator has stopped' error, but the need to recycle the CrmAppPool (slightly less sever than IISReset), is normal to see updates to custom workflow assemblies in the workflow editor. This is because the workflow editor is part of the web application, rather than the Async Service

    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk

    Wednesday, August 29, 2012 8:47 AM