SQL Server

Troubleshooting SQL Server 2014 Analysis Services problems (Part 1)

Troubleshooting SQL Server 2014 Analysis Services problems (Part 1)

If you have problems with SQL Server 2014 Analysis Services (SSAS 2014), review this troubleshooting
checklist to find potential solutions.

1. Install the latest SQL Server 2014 service pack.

Because many SQL Server 2014 Analysis Services bugs were fixed in SQL Server service packs,
you should install the latest SQL Server service pack.
At the time this article was written the latest SQL Server 2014 service pack was service
pack 1. You can download the SQL Server 2014 service pack 1 at here:
https://www.microsoft.com/en-us/download/details.aspx?id=46694

2. You may find that the MDX queries run very slowly when you run MDX queries in an
application that uses the ADOMD.NET data provider through HTTP to connect to SSAS 2014.

This is SQL Server 2014 Analysis Services bug. To work around this problem, you can use
the OLE DB provider through HTTP, the OLE DB provider through TCP/IP, or the ADOMD.NET data
provider through TCP/IP instead of the ADOMD.NET data provider through HTTP.

3. When you set the value of the AllMemberAggregationUsage property to “None”,
the Aggregation Design Wizard still generates aggregations on the “All”
member of a dimension.

This problem occurs because the Aggregation Design Wizard ignores the value of the
AllMemberAggregationUsage property. To work around this problem, you should set the value
of the AggregationUsage property of the attribute of the dimension to “Full”.

4. The Analysis Services service may stop unexpectedly and Event ID 22 is logged
in the Application log when you process an object in a database.

This problem occurs when Analysis Services service tries to delete a file during the final phase
of the processing operation but this file is locked by other application, for example, antivirus
software or backup software. To work around this problem, avoid run any antivirus or backup
software during process an object in a database.

5. The error occurs when you execute a ProcessFull or ProcessAdd command against a
partitioned table in SSAS 2014 instance that is running in Tabular mode.

This is the error message text: “XMCompressionAnalyzer::SelectBitPackCompression”. This
bug was first fixed in Cumulative Update package 1 for SQL Server 2014. You can download
the Cumulative Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693
To work around the problem, perform a Process Defrag command against the table that has
the issue.

6. The error occurs when you run a “Process” command against the Microsoft Visual Studio
Team Foundation Server (TFS) SSAS cube.

This is the error message text: “Internal error: An unexpected error occurred”. The problem
occurs because a duplicate dimension key value in the data source is used by the Analysis
Services processing. This bug was first fixed in Cumulative Update package 1 for
SQL Server 2014. You can download the Cumulative Update package 1 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/2931693
To work around the problem, you can delete the invalid duplicate key in the data warehouse
dimension tables in SQL Server Database Engine.

7. Grand total or subtotal rows display incorrect results in a Power View report that
runs against a multidimensional cube in SSAS 2014.

This problem occurs when the report contains two or more group-by columns. This bug was
first fixed in Cumulative Update package 1 for SQL Server 2014. You can download the
Cumulative Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693

8. The error occurs when you run an MDX query that uses the Member.Name property
against an SSAS 2014 database.

This is the error message text: “The following system error occurred: Type mismatch.”
This bug was first fixed in Cumulative Update package 1 for SQL Server 2014. You can
download the Cumulative Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693
To work around the problem, you can use the Member.Caption property instead the
Member.Name property.

9. Query scope assignment works incorrectly after you run a ClearCache command
in SSAS 2014.

In this case, the assignment is deleted, and a NULL value is returned for the assignment.
This bug was first fixed in Cumulative Update package 1 for SQL Server 2014. You can
download the Cumulative Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693

10. “Invalid column name” error occurs when you run some MDX queries against ROLAP
partitions in SSAS 2014.

This problem occurs when the MDX query projects on non-root levels of a parent/child
hierarchy and the WHERE clause contains predicates on the members of the parent/child
hierarchy. This bug was first fixed in Cumulative Update package 1 for SQL Server 2014.
You can download the Cumulative Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693

11. SSAS 2014 instance crashes when you perform writeback action by using the role
with cell security defined.

This is SQL Server 2014 bug. This bug was first fixed in Cumulative Update package 2
for SQL Server 2014. You can download the Cumulative Update package 2 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2967546

12. The execution of an MDX query in SSAS 2014 is much slower than it is in SSAS 2008 R2.

This problem occurs if the MDX query uses calculated members and Sub Select statement.
This bug was first fixed in Cumulative Update package 2 for SQL Server 2014. You can
download the Cumulative Update package 2 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2967546

13. Data models do not load after you run a PowerPivot scheduled data refresh job.

In this case, you may receive the following error message: “We couldn’t load the Data
Model. This may be because the Data Model in this workbook is damaged.” This bug was
first fixed in Cumulative Update package 2 for SQL Server 2014. You can download the
Cumulative Update package 2 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2967546

14. You may experience poor performance when you use DAX functions on a String
or Boolean column in SSAS 2014.

This is SQL Server 2014 bug. This bug was first fixed in Cumulative Update package 2
for SQL Server 2014. You can download the Cumulative Update package 2 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2967546

15. Incorrect folder when deploying SQL Server 2014 PowerPivot solutions by using
SharePoint 2013 Central Admin.

This bug was first fixed in Cumulative Update package 3 for SQL Server 2014. You can
download the Cumulative Update package 3 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2984923
To work around this problem, you should redeploy the farm solution by using PowerPivot
for SharePoint 2013 Configuration Tool.

16. Sub-total of calculated measure is incorrect (non-filtered) when you execute
MDX query in SSAS 2014.

This bug was first fixed in Cumulative Update package 3 for SQL Server 2014. You can
download the Cumulative Update package 3 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2984923
To work around this problem, you can clear the cube cache in order to temporarily
eliminate the problem. Facebooktwitterredditpinterestlinkedinmail