|
| 1 | +--- |
| 2 | +title: Troubleshoot Failures When Provisioning Unified Routing in Dynamics 365 |
| 3 | +description: Learn how to troubleshoot failures when you provision unified routing in Dynamics 365 Customer Service. |
| 4 | +author: hbarik |
| 5 | +ms.author: hbarik |
| 6 | +ms.reviewer: nenellim |
| 7 | +ms.topic: troubleshooting-problem-resolution |
| 8 | +ms.collection: |
| 9 | +ms.date: 09/22/2025 |
| 10 | +ms.custom: sap:Routing Setup\Unable to turn on Unified Routing |
| 11 | +--- |
| 12 | + |
| 13 | +# Troubleshoot failures when provisioning unified routing |
| 14 | + |
| 15 | +This article provides troubleshooting guidance for issues that occur when you provision [unified routing](/dynamics365/customer-service/administer/overview-unified-routing) in Dynamics 365 Customer Service. |
| 16 | + |
| 17 | +## Symptoms |
| 18 | + |
| 19 | +When you try to [enable the unified routing toggle](/dynamics365/customer-service/administer/provision-unified-routing#enable-unified-routing-for-customer-service-only) in Dynamics 365 Customer Service, the feature isn't enabled, and you receive one of the following error messages: |
| 20 | + |
| 21 | +- "Unified routing provisioning failed due to issues in configuration..." |
| 22 | +- "Unified routing provisioning failed due to an error in deactivation of basic routing rulesets..." |
| 23 | +- "Unified routing provisioning failed due to an error in activation of basic routing rulesets..." |
| 24 | + |
| 25 | +## Cause 1: Issues in basic routing rule sets |
| 26 | + |
| 27 | +If you're already using [basic routing](/dynamics365/customer-service/administer/create-rules-automatically-route-cases), conflicts might occur when you activate or deactivate routing rule sets or modify their permissions. |
| 28 | + |
| 29 | +### Solution |
| 30 | + |
| 31 | +1. Check the ownership of all the basic routing rule sets. If the owner of a rule set no longer has access, either reactivate the user or transfer the ownership of the rule set to an active user. |
| 32 | +1. Try again to enable unified routing. |
| 33 | + |
| 34 | +For more information about basic routing rule sets, see [Automatically route cases using basic routing rule sets](/dynamics365/customer-service/administer/create-rules-automatically-route-cases). |
| 35 | + |
| 36 | +## Cause 2: Failures because of master entity routing configuration |
| 37 | + |
| 38 | +During provisioning, the system [creates a master entity routing configuration for the Case table](/dynamics365/customer-service/administer/set-up-record-routing#configure-unified-routing-for-records). This step might fail in the following scenarios: |
| 39 | + |
| 40 | +- During a copy operation from an existing organization, the decision contract is added in the target organization, but the related records are missed. Because the records are missing, the system can't create a master entity routing configuration for the Case table during provisioning. |
| 41 | +- You manually create a Case master entity record configuration by using the name `new_incidentmasterentityroutingconfiguration` before you trigger provisioning. |
| 42 | + |
| 43 | +### Solution |
| 44 | + |
| 45 | +1. From your Dataverse instance, delete the record of type `msdyn_decisioncontract` that has the following attributes: |
| 46 | + - `msdyn_name`: `Case decision ruleset` |
| 47 | + - `msdyn_uniquename`: `new_incidentmasterentityroutingconfiguration` |
| 48 | +1. Try again to enable unified routing. |
| 49 | + |
| 50 | +For information about how to delete records in Dataverse, see [Delete record](/power-apps/developer/model-driven-apps/clientapi/reference/xrm-webapi/deleterecord). |
| 51 | + |
| 52 | +## Related information |
| 53 | + |
| 54 | +[Manage unified routing in Dynamics 365 Customer Service](/dynamics365/customer-service/administer/provision-unified-routing) |
0 commit comments