Troubleshoot issues with cubes and key performance indicators (KPIs)
Applies To: Microsoft Dynamics AX 2012 R3, 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 work with cubes and key performance indicators (KPIs) included with Microsoft Dynamics AX.
When deploying cubes, you receive an error that says you can’t connect to the OLAP server
During cube deployment, the Infolog form appears and displays the following error:
Unable to connect to the OLAP server name currently set as the default: [SSASServerName]. Please ensure that it is a valid OLAP server instance and that it is running. The value can be changed in the Analysis Servers form.
To resolve this issue, complete the following tasks:
Verify that a supported version of Microsoft SQL Server Analysis Services is installed and running.
If you use Windows Firewall to help protect your computers, verify that the firewall is configured to allow access to Analysis Services. By default, Analysis Services uses port 2383, so you may need to exclude that port. For more information, see Configure the Windows Firewall to Allow Analysis Services Access.
Users cannot add or modify KPIs
Users may receive the following message when they try to add or modify KPIs in Enterprise Portal for Microsoft Dynamics AX:
An unexpected error occurred while processing the Business overview Web part. Contact your system administrator.
This situation occurs under the following conditions:
Users access Enterprise Portal on a computer that is not the SharePoint server.
Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 Feature Pack is installed.
To resolve this issue, follow these steps.
Install the Knowledgebase 2744197 hotfix.
Assign the proxy account for the Business Connector to the server administrator role in Analysis Services. Follow these steps:
Open SQL Server Management Studio and connect to your instance of Analysis Services.
In the tree view, right-click the Analysis Services instance, and then click Properties. The Analysis Services Properties window is displayed.
In the Select a page area, click Security.
Click Add. The Select Users or Groups form is displayed.
Enter the Business Connector proxy account in the following format: [DomainName]\[UserName]. Click OK.
You cannot process cubes because the provider is not registered
You may receive the following error when processing an Analysis Services project using the Analysis Services Project Wizard:
The provider 'SQLNCLI11.1' is not registered.
To resolve this issue, verify that the Analysis Services data source has the correct provider by completing the following steps.
In SQL Server Management Studio, connect to your Analysis Services instance.
In the tree view, expand the Databases > [Database Name] > Data Sources node.
Right-click the Dynamics Database data source and choose Properties.
In the Connection String row, verify that the provider is correct.
If you are using Analysis Services 2008, the provider should be SQLNCLI10.1.
If you are using Analysis Services 2008 R2, the provider should be SQLNCLI10.1.
If you are using Analysis Services 2012, the provider should be SQLNCLI11.1.
Click OK to save your changes.
When processing a cube, you see errors related to an attribute key
When processing a cube, you may see errors that indicate that an attribute key was converted to an unknown member. These errors are similar to the following:
Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'CUSTINVOICETRANSEXPANDED', Column: 'INVENTSTYLEID', Value: ''. The attribute is 'Styles'.
Errors in the OLAP storage engine: The attribute key was converted to an unknown member because the attribute key was not found. Attribute Styles of Dimension: Styles from Database: Dynamics AX initial, Cube: Sales cube, Measure Group: Customer invoice lines, Partition: Customer invoice lines, Record: 1.
These messages indicate that there is not a valid join between a measure and a dimension for that record. When creating a join, if a record is not in both tables, the join will not be as expected. In this case, the record gets placed in an unknown or N/A bucket when you view the cube data.
Consider the following examples:
An invoice line has an item associated with it. In case of free text invoices, there may not be an item associated with an invoice line. For free text invoices, the item field is empty by design.
Employees that are active do not have a “retired date”. In the employee fact table, the Retired date field contains the NULL date value, 1/1/1900, by design.
If the zip code field has no validation in Microsoft Dynamics AX and a customer record has an invalid zip code, 99999, it would be an outlier. Possibly the customer did not provide one.
You can handle these errors in the following ways:
Take no action.
Understand that when viewing reports and cube data, the unknown or N/A bucket represents the values that do not line up with the joins that are in the dimension usage.
Change the dimension data source view (DSV) to include a union select to address certain known scenarios (like the null date value, 1/1/1900).
Change the dimension usage tab for the related cubes to remove the joins where data is in one table and not in another.
Replace null values with non-null values.
Use integration services to create an Extract, Transform, and Load (ETL) process that takes data from your Microsoft Dynamics AX database, adds data to these key missing fields (for example, populate with the word “N/A”, “missing”, “unknown”, or “standard”) and then have your cube pull from this location.