A successful Riva connection to Microsoft Dynamics CRM 2011 experienced a connection error after applying Roll Up 10 or higher to the CRM system. This article includes:
Examination of crmex-log files reveals that standard CRM connections worked as expected.
2013-08-28 17:55:25,110 INFO [CTP-eqf #1887] [21ERJKI5GNB4] [xd9da39c952a5401f, x6036ca329a7e65e9] Discovered! DOMAIN\riva_connection_user (email@example.com) via https://crm.example.com/MSCRMServices/2007/SPLA/CrmDiscoveryService.asmx with Org: ExampleOrgName (21cf307e-a6ca-e111-bbd6-0050568e7f47) to https://crm.example.com/MSCrmServices/2007/CrmService.asmx2013-08-28 17:55:27,625 INFO [CTP-eqf #1887] [21ERJKI5GNB4] [xd9da39c952a5401f, x6036ca329a7e65e9] DOMAIN\riva_connection_user
Examination of the crmex-log files reveals the following CRM connection error:
2013-08-29 06:00:01,165 INFO [CTP-zpj #123] [1U141126TZB4] Establishing connection to Microsoft Dynamics CRM [IMPERSONATION]...
2013-08-29 06:00:01,322 ERROR [CTP-zpj #123] [1U141126TZB4] [CL: xd9da39c952a5401f; M:x6036ca329a7e65e9] Attempted connection to: DOMAIN\riva_connection_user (DOMAIN\riva_connection_user) @ https://crm.example.com/MSCRMServices/2007/SPLA/CrmDiscoveryService.asmx2013-08-29 06:00:01,322 INFO [CTP-zpj #123] [1U141126TZB4] Connection to CRM Server failed: The request failed with HTTP status 404: Not Found.
The Riva server used a connection to Dynamics CRM that consumed standard web service "endpoints". We refer to that client as the "Legacy" client, which supports Dynamics CRM 4 and 2011.
Dynamics 2011 also included support for XRM web service endpoints, which have been supported since the RTM release. The Riva "Legacy" connection to Dynamics CRM does not support XRM web service endpoints.
With the conversion of CRM Dynamics Online to Office 365, Microsoft removed support for standard web service endpoints and switched to using XRM web service endpoints. After Office 365 and Dynamics Online customers with Riva servers were transitioned to those new instances, their Riva "Legacy" connection failed.
Riva 2.4.35 includes a new XRM-based Riva connection to Dynamics CRM. In some circumstances, you can choose which Riva connection to use:
There is one major difference between the "Legacy" and XRM-based CRM connections.
If you are considering applying the Dynamics Roll-up 10 or higher, be aware of the requirement to switch to using the Riva XRM-based CRM connection and the lack of plug-in "compatibility" mode.
If the Riva server was originally configured with a "Legacy" CRM connection and an Office 365 Dynamics Online refresh (upgrade) or applying Dynamics CRM 2011 Roll Up 10 or higher has resulted in CRM connection errors, use the following procedure to upgrade to the XRM-based CRM connection.
DO NOT create a new sync policy. Creating a new sync policy would create duplicate records in the CRM and the email system and/or remove previously synced contact records from the CRM and/or the email system. It would be time-consuming and difficult to recover from such an action.
To replace a "Legacy" connection with a "XRM-based" connection:
Article ID: 983
Last updated: 06 Feb, 2017
Also listed in
Riva On-Premise - CRM Sync -> Manage Riva On-Premise (Admin Guides) -> Troubleshooting (Includes Monitoring) -> Resolving CRM Connection Issues