Our frontend server is currently being flooded with errors from MSCRMKEYGenerator - all errors are along the lines of:
The current active key (KeyType : CrmTicketKey) is expired. This may indicate that a key is not being regenerated correctly. Current Active Key : CrmKey(Id:250f0345-8e6d-e811-80f4-005056b03f70, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmTicketKey, Expired:True, ValidOn:06/11/2018 15:44:05, ExpiresOn:06/13/2018 15:44:05, CreatedOn:06/11/2018 15:44:05, CreatedBy:<user>. Key Setting : CrmKeySetting(Id:<id>, KeyType:CrmTicketKey, KeyLength:128, KeyGenerationInterval:24, KeyTimeToLive:48, CryptoTimeToLive:24, Algorithm:HMACSHA256, ArchiveLength:1, Enabled:True, ActiveKeys:[ScaleGroupId=00000000-0000-0000-0000-000000000000,ActiveKeyId=<id>])
This error appeared at the same time on both our development, test and production servers. However, as the eventlog is being flooded, I can't see exactly when it started.
It doesn't appear to have any impact on performance on CRM itself, but I'd still like to get it sorted.
I've tried all the usual things... restarting the async service(s), iisreset, restarting the entire server, running "Microsoft.Crm.Tools.WRPCKeyRenewal.exe /R" followed by yet another iisreset and following the workaround mentioned here: https://partnersupport.microsoft.com/en-us/par_msdyn/forum/par_dyn365p/top-issuehow-to-solve-the-dynamics-crm/89d196cb-202c-49b5-a2f5-f1fcbce5eb2c - nothing seems to work for longer than 24 hours tops.
I've heard rumours that it might be a specific windows update that's causing this issue to occur, but would really rather not have to uninstall any KB-updates, so am hoping somebody might know of a better solution?
