Applies to Product -Dynamics 365 Lifecycle Services
What’s happening?
Customers encounter errors when attempting to open reports in Dynamics 365 environments, specifically receiving messages such as "Unable to find report design" or "The AppliesTo address of the relying party was not a valid absolute URI."
Reason:
This are often related to misconfigurations in the web.config or wif.config files, particularly missing parameters such as the SPN value. Additionally, problems may arise after importing databases from different environments, leading to inconsistencies in report accessibility.
Resolution:
- For "Unable to find report design" Error:
- Verify that the custom reports are included in the deployment package.
- Check the deployment logs for any SSRS deployment failures.
- In Visual Studio, search for the report by name in the AOT, add it to your project, and right-click to select 'Deploy Reports'.
- If the issue persists, consider manually deploying SSRS reports using PowerShell as previously successful in other environments.
- For "The AppliesTo address of the relying party was not a valid absolute URI" Error:
- Modify the wif.config file to include the missing SPN value. Add the entry: add value="spn:customer's app_id".
- Ensure the web.config file is also updated with the appropriate parameters.
- Restart the affected machine after making changes to the configuration files.
- Perform a data mart reset using the scripts provided in the Microsoft documentation for resetting the Financial Reporting data mart.
- General Steps:
- If the problem started after a database import, ensure that the source and target environments are compatible in terms of version.
- Create a custom view to check events in the environment and monitor for any errors during report generation.
- If issues continue, consider deploying a new machine with the same version as the UAT environment and check for any customizations that may interfere with report execution.