Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012
Data Import, Export, and Migration
Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
SSRS and SSAS Integration
This page is intended to provide a consolidated list of published documentation, known issues, solutions as well as tips and tricks for SSRS and SSAS integration in Microsoft Dynamics AX 2009.
The default OLAP cubes that are provided with Microsoft Dynamics AX were designed with full license and configuration keys. When using License and Configuration Keys where all modules are not present, OLAP cubes will be need to be configured. If any license or configuration key is turned off, you must complete the procedures in the Microsoft Dynamics AX 2009 White Paper: Configuring the Default OLAP Cubes.
The Enterprise Portal Role center pages contain SSRS reports and SSAS default cubes. If you have not implemented the SSRS or have not completed your Dynamics® AX customizations you may want to consider removing the SSRS web parts from Enterprise Portal or selecting the Default Role Center which does not have BI content. Implementing the reporting features can be done at a later time after the main implementation is complete.
When setting up SSRS, SSAS, and WSS or MOSS on multiple severs you will need to be aware of how to set up and configure Kerberos Authentication. See the Microsoft Dynamics AX 2009 White Paper: Configuring Kerberos Authentication with Role Centers and the common problems section below.
A number of the common issues can be resolved by ensuring that the prerequisites have been properly installed on the correct servers and by carefully reviewing the installation and troubleshooting documentation before attempting the actual installation.
This section lists the most common issues encountered when building the integration between Microsoft Dynamics® AX, SSRS and OLAP and the solution recommended by the Microsoft Dynamics® AX Support team.
Error trying to deploy reports: Microsoft Dynamics AX Reporting Project Deployment: The following components have not been installed or are not configured correctly: AL.exe
Download and install the Windows SDK for Windows Server 2008 and .NET Framework 3.5 Ensure it is fully installed. Note: Install regardless of operating system
Error trying to deploy reportsSystem.InvalidOperationException: The following components have not been installed or are not configured correctly: Microsoft Domain-Specific Language Tools
Download and install these required components. Microsoft Visual Studio 2008 Shell (isolated mode) Redistributable Package
Error trying to deploy reportsMicrosoft Dynamics AX Reporting Project Deployment: ClrBridgeLoader: fatal error : Microsoft.Dynamics.ClrBridge.dll cannot be loaded. Fatal error: ClrBridge is note loaded.
Ensure you are trying to deploy reports from the SSRS server and that you can validate the SSRS server name in the Reporting Servers from within Microsoft Dynamics AX 2009. If this error appears right after installing the reporting extensions, launch the report deployment tool again.
Enterprise Portal (EP) or SSRS Reports don’t run or stop workingAn attempt has been made to use a data extension 'AXDATAMETHOD' that is not registered for this report server. (rsDataExtensionNotFound) ordata extension 'AXQUERY' and 'AXADOMD'
Installing or Reinstalling Reporting Extensions will resolve this issue. As a precaution make a Backup of:Program Files\Microsoft SQL Server\MSSQL.<Instance>\Reporting Services\ReportServer folderNote: SSRS updates or Service Packs may remove entries from rsreportserver.config file.
Enterprise Portal (EP) Reports don’t run or stop workingA ProgressTemplate must be specified on UpdateProgress control with ID 'AxProgressControl'
You can resolve the issue by using one of the three methods below:
Report deployment tool crashesAttempted to read or write protected memory. This is often an indication that the memory is corrupt
If multiple versions of Dynamics AX are installed on the same server you will need to change your AX 2009 Path in your environment variables ahead of your AX 4.0 path to avoid running the wrong version of DLL’s
Error running reportsError during processing of 'AX_CompanyName' report parameter. (rsReportParameterProcessingError).
Process OLAP the cubes to supply data to the reports orAn incorrect Execution account has been specified in the Reporting Services Configuration ManagerNote: For SSRS 2008 the Business Connector proxy account is required to be the SSRS service account and for SSRS 2005 the Business Connector Proxy account should be running as the SSRS application pool in IIS. Also look at application event log for details on other issues.
Enterprise Portal (EP) web site runs but not the reports in the EP web parts:Dynamics Adapter LogonAs failed orMicrosoft.Dynamics.BusinessConnectorNet.LogonFailedException
Leave the Execution account blank on SSRS 2005 or set to BC Proxy account on SSRS 2008 (Microsoft Dynamics AX 2009 SP1 only)Note: SSRS Execution account is set to an account other than BC Proxy Account
EP or SSRS Reports don’t run or stop workingDynamics Adapter LogonAsGuest failed orFatalSessionException...
The issue is caused by the Reporting Services web site set to anonymous Authentication. Changing the SSRS website to Integrated and/or un-marking Anonymous Authentication will resolve this issue.
Double Hop \ Kerberos Authentication An Error has occurred while establishing as connection to the Analysis Server orReports don’t display in the EP website from a Client Browser not local to the IIS server Cannot read information from SQL Server Reporting Services. Validate that the Report Manager URL is correct
Setup Service Principle names (SPN) and Delegation to allow the passing of Kerberos certificate
Office Data Connection (ODC) file deployment fails with SQL Server 2008 Microsoft Dynamics AX is searching for the SQL Server 2005 Microsoft.AnalysisServices.dll (v18.104.22.168)
Apply one of the following hotfixes:
If the hotfix does not resolve the issue, make sure you are running a Dynamics AX 2009 client on the EP web server when deploying the ODC files. As a workaround you can manually deploy the ODC files by following these steps:
DataSet panel is missing in Report Designer when creating reports in Visual Studio Server 2008
For Visual Studio 2008, apply the fix in KB947173 OR apply Microsoft Visual Studio 2008 Service Pack 1.
"Connection forcibly closed by remote host" in Dynamics setup log when trying to create an EP site in Microsoft Dynamics AX 2009
Download and install the Microsoft Analysis Management Objects:
"Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'"
Ensure SSRS service is running and are able to connect to instance via SQL Server Management Studio.Note: Additional information can be found in SSRS error log.
Exception from HRESULT: 0X80041FFF
Change Visual Studio project location to local drive if using a network share
The Analysis extension is not seeing the SQL cluster name for Analysis Services when Analysis services is setup on a SQL cluster.You will get an error similar to this when trying to install Analysis Extension in this environment:Connecting to SQL Server 2005 Analysis Services on server 'SQL02' and instance 'MSOLAP$ANALYSIS'. A connection cannot be made. Ensure that the server is running. No connection could be made because the target machine actively refused it 127.0.0.1:2383 An error occurred while Setup was connecting to SQL Server Analysis Services instance 'MSOLAP$ANALYSIS' on server 'SQL02'. An error occurred while Setup was connecting to SQL Server Analysis Services instance 'MSOLAP$ANALYSIS' on server 'SQL02'.
The workaround is to manually run the script to create the Dynamics AX OLAP db from the AX 2009 CD.Navigate to this folder: \support\Analysis Services\Scripts on the Microsoft Dynamics AX 2009 installation CD. Then run the dynamicsax.xmla script from within SQL Management Studio (connected to the SSAS instance).This script will create the Dynamics AX OLAP database.
BC Proxy account fails to start for the SSRS reports in Enterprise Portal with RPC exception 5When Enterprise Portal starts for the first time and displays SSRS reports, normally two Business Connectors are started. After a period of time or if the impersonated web user logs out for the SSRS Proxy account you may experience an RPC error 5 access denied and the SSRS reports will no longer display in Enterprise Portal.Example Event Type: Error Error: Event Source: Dynamics .NET Business Connector 5.0 Event Category: None Event ID: 180 Date: 10/7/2008 Time: 6:21:04 PM User: N/A Computer: AX2009 Description: Microsoft Dynamics AX Business Connector Session 18. RPC error: RPC exception 5 in Ping occurred in session 36
RPC error 5 can occur if the SSRS Execution account is set in the Reporting Services Configuration Manager. If the account used is the Business Connector proxy account the first startup of the Business Connector will work, but not any subsequent startups unless the IIS application pool if recycled or an IIS reset is done.SSRS 2005 Remove the SSRS execution account through Reporting Services Configuration Manager and ensure the Business Connector account is running the IIS Application Pool for the SSRS web site.SSRS 2008 Change the SSRS service to start as the Business Connector Proxy account and remove the SSRS execution account through Reporting Services Configuration Manager. Note: Changing the SSRS account would require a change in the registered SPN’s if you are using Kerberos authentication
If you are experiencing issues downloading the install file or documentation on CustomerSource/PartnerSource, please contact ITMBSSUP@microsoft.com
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics