Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archive) / CRM 2013 : Intermitten...
Microsoft Dynamics CRM (Archive)
Answered

CRM 2013 : Intermittent Async service failure - The remote procedure call failed and did not execute

(0) ShareShare
ReportReport
Posted on by xavierbe 45

Our CRM 2013 (6.1.5.0111) Async Service is intermittently failing with the following error.

A Microsoft Dynamics CRM Asynchronous Processing Service operation of type 1eade10f-16a5-e711-810a-005056bc3c01 has failed
ErrorMessage:Microsoft.Crm.CrmException: Failed to get priv user group information. k = 1eade10f-16a5-e711-810a-005056bc3c01 privUserGroupId: a4bcaf5c-0948-4b6d-a3bd-4c720345ecc5, localSystemAdGuid: cd9c85e3-d141-4c41-9924-d4e9711c6c51, Exception: System.Runtime.InteropServices.COMException (0x800706BF): The remote procedure call failed and did not execute. (Exception from HRESULT: 0x800706BF)
at Microsoft.Crm.Tools.ActiveDsWrapper.NameTranslateClass.Init(Int32 lnSetType, String bstrADsPath)
at Microsoft.Crm.ADNameUtility.Rfc1779NameFromGuid(Guid guid)
at Microsoft.Crm.SecurityUtils.CheckMembership(Guid principalId, Guid groupId)
at Microsoft.Crm.Caching.OrganizationSettingsCacheLoader.LoadCacheData(Guid key, ExecutionContext context). ---> System.Runtime.InteropServices.COMException: The remote procedure call failed and did not execute. (Exception from HRESULT: 0x800706BF)

Actions Taken:

- Production CRM Recently migrated (database restore) from 'X' AD domain to 'Y' AD domain.
- Issue is intermittent and does not always occur.
- Sometimes issue automatically resolved. Occasionally required App server server reboot.
- Enabled platform tracing, which produced the same error as a failed remote procedure call.

Categories:
Install and Upgrade
  • Verified answer
    xavierbe Profile Picture
    xavierbe 45 on at
    RE: CRM 2013 : Intermittent Async service failure - The remote procedure call failed and did not execute

    Hi,

    Managed to identify the cause. It seems the new AD has multiple DC replication and one of the DC in different subnet which required clearance. 

  • Pedro Cadavez de Freitas Profile Picture
    Pedro Cadavez de Fr... on at
    RE: CRM 2013 : Intermittent Async service failure - The remote procedure call failed and did not execute

    Hello xavierbe,

    Hope you are well.

    This seems a failure on calls to AD and if they are transient, its dificult to attach to a CRM failure, but more an unavailability on the DC.

    Some ideas are discussed here:    

    This is hard to discuss via the communities blog, as this might require sharing logs, memory dumps and AD collaboration.

    Since you confirmed you changed domain X to Y, maybe domain Y is not as stable as X and should be considered.

    If you still need help is probably a best idea to open a service request with our team.

    Thank you!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Community Spotlight of the Month

Kudos to Mohamed Amine Mahmoudi!

Blog subscriptions now enabled!

Follow your favorite blogs

TechTalk: How Dataverse and Microsoft Fabric powers ...

Explore the latest advancements in data export and integration within ...

more Community News

Leaderboard > Microsoft Dynamics CRM (Archive)

Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans