Dynamics Community Forum Thread Details

Hello SH-30040526-0,

The error message you're encountering during the "Apply solution" step while enabling Dual Write is:

[UnknownError] Failed to get solutions containing entity maps. - Type=Microsoft.PowerApps.CoreFramework.Communication.Http.NonSuccessHttpResponseException, Stat Session ID: bNStq4vX0qjG5j/O6De027+h Root Activity ID: 407e202a-11c9-40c5-a621-67f604e56868

This error indicates that the system is failing to retrieve the necessary information about solutions that contain entity maps required for Dual Write. The NonSuccessHttpResponseException suggests that an HTTP request made by the Power Platform to another service failed with a non-2xx (success) status code.

Here's a breakdown of potential causes and troubleshooting steps you can take:

Possible Causes:

Service Interruption or Outage: The most likely cause for this type of error, especially during a complex operation like enabling Dual Write, is a temporary service interruption or outage within the Power Platform or related services (like Dataverse or Finance and Operations).

Network Connectivity Issues: Although less probable within the Microsoft cloud infrastructure, transient network issues between the different services involved in Dual Write could cause HTTP request failures.

Incorrect Configuration or Prerequisites Not Met: While you're at the "Apply solution" stage, it's worth double-checking if all the prerequisites for enabling Dual Write have been correctly configured. This includes:
- Linking your Dataverse and Finance and Operations environments.
- Ensuring the necessary licenses are in place.
- Verifying that the Dual Write feature is enabled in both environments.

Permissions Issues: The user account you're using to enable Dual Write might lack the necessary permissions to access information about solutions and entity maps.

Corrupted Solution or Environment: In rare cases, a corrupted solution or an issue within one of your environments (Dataverse or Finance and Operations) could lead to this error.

Recent Platform Updates: A recent update to the Power Platform or Dynamics 365 services might have introduced a temporary bug or incompatibility.

Troubleshooting Steps:

Check the Power Platform Admin Center Health:
- Navigate to the .
- Go to Environments and select the environment where you are trying to enable Dual Write.
- Check the Health section for any active alerts or notifications regarding service issues.
- Also, check the Analytics section for any performance issues or errors.

Check the Dynamics 365 Service Health Dashboard:
- Go to the and navigate to Health > Service health.
- Look for any incidents or advisories related to Dynamics 365, Power Platform, or Dataverse.

Retry the Operation: This might seem simple, but often temporary service glitches resolve themselves. Wait a few minutes and try applying the solution again.

Verify Dual Write Prerequisites:
- Carefully review the official Microsoft documentation on setting up and enabling Dual Write. Ensure you have completed all the necessary steps, including linking the environments and enabling the feature.

Check User Permissions:
- Ensure the user account you are using has sufficient privileges in both the Dataverse and Finance and Operations environments. This typically requires System Administrator or similar roles.

Examine Solution Details:
- In your Dataverse environment, navigate to Solutions. Check the status of the solutions related to Dual Write. Look for any that might be in a failed or error state.

Restart Related Services (If Possible and Applicable):
- If you have any control over related services (e.g., Azure Logic Apps or connectors used in the Dual Write setup), consider restarting them (with caution and understanding the potential impact).

Review Activity Logs:
- Check the activity logs in both Dataverse and Finance and Operations for any errors or warnings that occurred around the time you attempted to apply the solution.

Contact Microsoft Support: If the issue persists after trying the above steps, the next best course of action is to contact Microsoft Support. Provide them with the error message, session ID, root activity ID, and details of the steps you have already taken. They will have access to more detailed logs and diagnostic tools to identify the underlying cause.

Information to Provide to Microsoft Support:

The full error message you provided.

The Session ID and Root Activity ID.

The specific step at which the error occurs during the Dual Write enablement process.

Whether this is a new setup or an existing setup that suddenly started failing.

Any recent changes made to your environments or configurations.

Whether you have checked the service health dashboards.

By systematically working through these troubleshooting steps and involving Microsoft Support if necessary, you should be able to identify and resolve the error preventing you from applying the solution and enabling Dual Write. Remember to check the service health dashboards first, as this type of error often indicates a temporary platform issue.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak