Troubleshoot Report Deployment Issues
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
This topic provides information that can help you troubleshoot issues that you may encounter when you deploy Microsoft Dynamics AX reports.
For more information about how to troubleshoot Microsoft SQL Server Reporting Services reports, see Troubleshooting Report Problems in the SQL Server documentation.
Why won’t my report deploy?
The following table provides possible issues and troubleshooting details for common deployment issues.
More information for troubleshooting
Unable to deploy the report in Visual Studio
Unable to deploy the report in the AOT
Why doesn’t deploying the report overwrite the old report?
The following list describes two scenarios and the steps to troubleshoot reports that are not updated.
The deployed report is not updated after you modify the report in Visual Studio.
Follow these steps to update the Report Definition Language (RDL) and the data for the report:
In the AOT, expand the SSRS Reports node, right-click the Reports node, and then click Refresh.
Expand the Reports node, right-click the report to update, and then click Restore. The RDL and the data that is rendered on the report are updated.
You can also update the cache. In a Development Workspace, on the Tools menu, click Caches, and then click Refresh elements.
The deployed report is not updated after you add a default value to an existing parameter and then deploy the report.
There are two options to resolve this issue:
Update the default value in Reporting Services Report Manager.
Delete the report before you deploy it.
We do not recommend this option if you use the report history or subscriptions, because these are bound to the report and are deleted together with it.
Why do I get a permission error when I try to deploy a report?
The most common reasons for permission errors are as follows:
UAC is enabled. Run the applications that you are deploying reports from as the administrator. Right-click the application, and then click Run as administrator.
You are not a member of the local Administrators group on the report server.
You have not configured Reporting Services for local administration.
If you want to administer a report server instance locally, you must complete additional configuration steps to deploy Reporting Services on Windows Server 2008. Windows Server 2008 limits the overuse of elevated permissions by removing administrator permissions when users try to access applications. Because the operating system removes permissions, members of the local Administrators group run most applications as if they are using the Standard User account. Although this practice improves the overall security of a system, it prevents you from using the predefined, built-in role assignments that Reporting Services creates for local administrators.
For information about how to fix this issue, see How to: Configure a Report Server for Local Administration on Windows Vista and Windows Server 2008 (UAC).
Why do I get a permission error when I try to access the Report Manager website?
When you try to access the Report Manager website, you may receive the following permission error:
User '[DomainName]\[UserName]' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.
By default, you cannot access the Report Manager website if UAC is enabled. To access the Report Manager site when UAC is enabled, follow these steps.
Open your browser as an administrator. To open Internet Explorer as an administrator, follow these steps:
Right-click the Internet Explorer option.
Click Run as administrator.
Open the Report Manager website. By default, the URL is http://[SSRSServerName]:80/Reports.
Why does my report deployment throw this error: Unrecognized element 'extendedProtectionPolicy'?
When you deploy the report, you are running an application that is based on Windows Communication Foundation. The application uses the extendedProtectionPolicy type. The underlying .NET Framework 2.0 SP2 Network Client Library feature layer is not updated when the Windows Communication Foundation feature layer is updated to use the new type. The underlying .NET Framework 2.0 SP2 Network Client Library feature layer does not support this new type.
For information about why this occurred, and to download the hotfix, see Microsoft Support Article 2262911.
Why do I receive a network path error when I try to deploy a report?
When you try to deploy a report, you may receive the following error:
The network path was not found.
To resolve this issue, you may have to start the Remote Registry service on the server that runs Reporting Services. Follow these steps to start the service.
Click Start > Administrative Tools > Services to open the Services management console.
Right-click the Remote Registry service, and then click Start.
Why do I receive a SQL connection error when I try to deploy a report?
Deployment failures can be expected if more than one developer is trying to deploy a report. Deployment often requires a service restart, which affects other active deployments.
Why do I receive a security access fault when I try to deploy a report?
You must be a local administrator on the report server to deploy reports.
How do I deploy reports after I receive a file locked error?
When you deploy reports, you may receive the following error:
The process cannot access the file '[ReportName].dll' because it is being used by another process.
To resolve this issue, you can add the RestartReportServer option as part of the report deployment in Windows PowerShell. For more information, see Deploy the default reports.