locked
Expired Key - Can No Longer Access CRM2011 Organisation RRS feed

  • Question

  • Our CRM2011 deployment stopped working overnight - whenever we attempt to access by web browser we now get following error message:

    "An error has occurred.

    Try this action again. If the problem
    continues, check the Microsoft Dynamics CRM Community for solutions or contact
    your organization's Microsoft Dynamics CRM Administrator. Finally, you can
    contact Microsoft Support. "

    Installed CRM Diagnostic Tool and turned DevErrors On we get following message when trying to access using web browser:

    Microsoft CRM Error Report:

    Error Description:
    The key specified to compute a hash value is
    expired, only active keys are valid. Expired Key :
    CrmKey(Id:71b19167-2852-e311-9c9a-3c4a92f3a5e3,
    ScaleGroupId:00000000-0000-0000-0000-000000000000,
    KeyType:CrmStaticVersionScaleGroupKey, Expired:True, ValidOn:11/20/2013
    21:12:05, ExpiresOn:01/19/2014 21:12:05, CreatedOn:11/20/2013 21:12:05,
    CreatedBy:FUTUREPC\MSCRMSERVICE.

    Error Details:
    The key specified to compute a hash value is expired, only active keys are valid.  Expired Key : CrmKey(Id:71b19167-2852-e311-9c9a-3c4a92f3a5e3, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmStaticVersionScaleGroupKey, Expired:True, ValidOn:11/20/2013 21:12:05, ExpiresOn:01/19/2014 21:12:05, CreatedOn:11/20/2013 21:12:05, CreatedBy:FUTUREPC\MSCRMSERVICE.

    Full
    Stack:
    [CrmException: The key specified to compute a hash value is expired, only active keys are valid.  Expired Key : CrmKey(Id:71b19167-2852-e311-9c9a-3c4a92f3a5e3, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmStaticVersionScaleGroupKey, Expired:True, ValidOn:11/20/2013 21:12:05, ExpiresOn:01/19/2014 21:12:05, CreatedOn:11/20/2013 21:12:05, CreatedBy:FUTUREPC\MSCRMSERVICE.]
       at Microsoft.Crm.CrmKeyService.ComputeHash(CrmKey key, Guid scaleGroupId, HashParameterBase[] parameters)
       at Microsoft.Crm.Caching.StaticFileVersionCache.StaticFileVersionCacheLoader.FetchGeneralStaticVersion()
       at Microsoft.Crm.Caching.BasicCrmCache`2.LookupEntry(TKey key, IOrganizationContext context)
       at Microsoft.Crm.Application.Utility.CrmUri.set_UseVersionStamp(Boolean value)
       at Microsoft.Crm.Application.Utility.CrmUri..ctor(String uri, String organizationName, Boolean useWebResourcesVersion, IOrganizationContext context)
       at Microsoft.Crm.Controls.PageResourceManager.SetStyleSheet(String file)
       at Microsoft.Crm.Controls.Header..ctor(Boolean isControlHeader)
       at Microsoft.Crm.Controls.BasicHeader..ctor()
       at Microsoft.Crm.Application.Controls.AppHeader..ctor()
       at ASP.default_aspx.__BuildControlcrmHeader()
       at ASP.default_aspx.__BuildControlTree(default_aspx __ctrl)
       at ASP.default_aspx.FrameworkInitialize()
       at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
       at System.Web.UI.Page.ProcessRequest()
       at System.Web.UI.Page.ProcessRequest(HttpContext context)
       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
    
    

    Other Message:

    Error Number:
    0x8004A106

    Source File:
    Not available

    Line Number:
    Not available

    Error Trace:
    Date: 01-27-2014

    Time:
    06:49:05

    Server: crmts
    Request URL:
    http://crmts:5555/default.aspx
    Microsoft CRM Unhandled Error Details:
    Basic Server & Client
    Information:
    <iframe frameborder="0" id="ifrmDebug" name="ifrmDebug" src="/FuturePC/home/home_debug.aspx" style="width:100%;height:100%;"></iframe>
    What the End User would have
    seen:
    <iframe frameborder="0" id="ifrmEnduser" name="ifrmEnduser" src="/_static/blank.htm" style="width:100%;height:100%;"></iframe>
    Copy to Clipboard:
    The error information has been copied to the
    clipboard.

    We would appreciate whatever help we can to resolve this problem - We have tried using the WRPCKeyRenewal.exe followed by IISReset - doesn't resolve the issue.

    Sunday, January 26, 2014 5:54 PM

Answers

  • May be related to an Async service issue.  Try restarting the Async service(s) and see if you continue to see the error.

    The Async service may even not be running.  So check this.  You may also want to make sure that the account running the service has the correct permissions.

    The Async is responsible for renewing an encryption key that is used by CRM.

    If you continue to have the problem, you may want to also look at the rollup level on the CRM server to make sure it is current.


    Jason Peterson

    • Marked as answer by WayneDawson Monday, January 27, 2014 7:03 PM
    Monday, January 27, 2014 2:27 PM

All replies

  • Have you try to restart the crm server

    Hope this helps. ----------------------------------------------------------------------- Santosh Bhagat If this post answers your question, please click "Mark As Answer" on the post and "Vote as Helpful"

    Monday, January 27, 2014 3:27 AM
  • May be related to an Async service issue.  Try restarting the Async service(s) and see if you continue to see the error.

    The Async service may even not be running.  So check this.  You may also want to make sure that the account running the service has the correct permissions.

    The Async is responsible for renewing an encryption key that is used by CRM.

    If you continue to have the problem, you may want to also look at the rollup level on the CRM server to make sure it is current.


    Jason Peterson

    • Marked as answer by WayneDawson Monday, January 27, 2014 7:03 PM
    Monday, January 27, 2014 2:27 PM
  • Thanks Santosh - we have restarted the Server many times without resolution of the issue
    Monday, January 27, 2014 7:04 PM
  • Many thanks Jason - turned out to be a service account permissions issue for the Async Service - once we resolved that the CRM deployment commenced operation ok. 
    Monday, January 27, 2014 7:05 PM