Applies to Product - Dynamics 365 Finance
What’s happening?
The dual-write script failed execution against the cloud-hosted VM, resulting in a generic error code (0xFFFFFFFF). This issue typically arises when using the dual-write feature in finance and operations applications.
Reason:
The failure can be attributed to several potential factors, including: - Missing required columns in both the finance and operations app and Dataverse. - Version mismatches between the dual-write solutions in Dataverse and the required solution versions. - Stale configurations in either the finance and operations apps or Dataverse. - Insufficient permissions for the user executing the script, which requires system administrator roles in both finance and operations apps. - Environment issues, such as the linked Dataverse environment not being available or properly configured.
The failure can be attributed to several potential factors, including: - Missing required columns in both the finance and operations app and Dataverse. - Version mismatches between the dual-write solutions in Dataverse and the required solution versions. - Stale configurations in either the finance and operations apps or Dataverse. - Insufficient permissions for the user executing the script, which requires system administrator roles in both finance and operations apps. - Environment issues, such as the linked Dataverse environment not being available or properly configured.
Resolution:
To resolve the dual-write execution failure, follow these steps: 1. Check for Missing Columns: Ensure that all required columns are present in both the finance and operations app and Dataverse. If columns are missing, refresh the tables or add the missing columns. 2. Verify Version Compatibility: Check for version mismatches between the dual-write solutions in Dataverse and the required solution versions. Update the dual-write solutions to the latest versions. 3. Clean Up Stale Configurations: Review and clean up any stale configurations in either the finance and operations apps or Dataverse. 4. Confirm User Permissions: Ensure that the user has the necessary permissions to execute the script and perform dual-write operations. The user must have system administrator roles in both finance and operations apps. 5. Check Environment Configuration: Verify that the linked Dataverse environment is available and properly configured. If the environment was reset without unlinking dual-write, it could cause issues. 6. Refresh Entity List: Go to the finance and operations application, navigate to Framework parameters > Entity settings, and run the Refresh entity list. If the entity is activated, deactivate it and run the process again. If it is deactivated, activate it and execute the steps again.
If the issue persists after following these steps, further investigation may be required, including reviewing logs and detailed repro steps from the user.
To resolve the dual-write execution failure, follow these steps: 1. Check for Missing Columns: Ensure that all required columns are present in both the finance and operations app and Dataverse. If columns are missing, refresh the tables or add the missing columns. 2. Verify Version Compatibility: Check for version mismatches between the dual-write solutions in Dataverse and the required solution versions. Update the dual-write solutions to the latest versions. 3. Clean Up Stale Configurations: Review and clean up any stale configurations in either the finance and operations apps or Dataverse. 4. Confirm User Permissions: Ensure that the user has the necessary permissions to execute the script and perform dual-write operations. The user must have system administrator roles in both finance and operations apps. 5. Check Environment Configuration: Verify that the linked Dataverse environment is available and properly configured. If the environment was reset without unlinking dual-write, it could cause issues. 6. Refresh Entity List: Go to the finance and operations application, navigate to Framework parameters > Entity settings, and run the Refresh entity list. If the entity is activated, deactivate it and run the process again. If it is deactivated, activate it and execute the steps again.
If the issue persists after following these steps, further investigation may be required, including reviewing logs and detailed repro steps from the user.