SQL Server

Troubleshooting SQL Server 2014 Analysis Services problems (Part 2)

Troubleshooting SQL Server 2014 Analysis Services problems (Part 2)

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

1. The error occurs when you process a partition in a measure group in SQL Server 2014
Analysis Services.

This is the error message text: “Errors in the high-level relational engine. The binding for the
‘ column is not a ColumnBinding type”. This problem occurs when you process the
partition by using Business Intelligence Development Studio. To work around this problem, you can
process the whole cube or the whole database or you can process the partition by using SQL Server
Management Studio.

2. You may receive an access denied error message when connect to SQL Server 2014
Analysis Services after changing the service account by using the Computer
Management or Services.

To work around this problem, you should change the service account by using the SQL Server
Configuration Manager instead of the Computer Management or Services.

3. When you run an MDX query in SQL Server 2014 Analysis Services, the following
error may occur: “Dimension attribute was not found”.

This problem occurs when the MDX query requests a dimension property, the dimension property
is either an attribute or an intrinsic property and the MDX query returns a rowset.

4. Dimension attribute is lost in Excel PivotTable Field List when you set
AttributeHierarchyDisplayFolder to “” in SQL Server Data Tools – Business
Intelligence (SSDT-BI).

This is SQL Server 2014 bug. 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

5. When you use MDX with WHERE clause query or Data Analysis Expressions (DAX)
query to select multiple dimension members, incorrect result is returned.

In this case, the query returns the sum of them instead of individual member result.
This bug was first fixed in Cumulative Update package 4 for SQL Server 2014. You can
download the Cumulative Update package 4 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2999197

6. When you use MDX query to do session cube grouping in SSAS 2014, the query
fails and exception occurs.

This is the error message text: “Internal error: An unexpected error occurred (file
‘mdpartitionrolap.cpp’, line 948, function ‘MDPartitionRolapMapper::AddRolapCondition’).
Execution complete”. This bug was first fixed in Cumulative Update package 4 for
SQL Server 2014. You can download the Cumulative Update package 4 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/2999197

7. MDX query returns no result when the cache is not cleared after you run a
previous query in OLAP or tabular model.

This bug was first fixed in Cumulative Update package 4 for SQL Server 2014. You can
download the Cumulative Update package 4 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2999197
To work around this problem, you can clear the cache before you execute each query.

8. When you create a calculated member at the ALL member level in a dimension
hierarchy, the Except function does not return this member in a query.

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

9. Exception occurs when you select more than one hierarchy from parent/child
dimension in SSAS 2014.

This problem occurs when at least one level name of the parent/child hierarchy naming
template is identical to the name of an existing attribute hierarchy in the same
dimension. This bug was first fixed in Cumulative Update package 5 for SQL Server 2014.
You can download the Cumulative Update package 5 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3011055

10. The error occurs when you use DAX to execute a query, and the query retrieves
the member unique name for a parent/child hierarchy in a parent/child dimension.

This is the error message text: “File system error: The record ID is incorrect.”
This bug was first fixed in Cumulative Update package 5 for SQL Server 2014. You can
download the Cumulative Update package 5 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3011055

11. When a cube writeback commit transaction and a processing transaction are
executed at the same time on an instance of SSAS 2014, the instance crashes.

In this case, you receive a mini-dump file in the SSAS log folder. This bug was first
fixed in Cumulative Update package 6 for SQL Server 2014. You can download the
Cumulative Update package 6 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3031047

12. Database corruption occurs after you perform a ProcessData and then
ProcessRecalc operation in SSAS 2014.

This problem occurs because of database dictionary corruption after you perform a
ProcessData operation followed by a ProcessRecalc operation on the tables in a database.
This bug was first fixed in Cumulative Update package 6 for SQL Server 2014. You can
download the Cumulative Update package 6 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3031047

13. A crash occurs when proactive caching is triggered for a dimension in SSAS 2014.

In this case, the following error message occurs: “Internal error: An unexpected
error occurred (file ‘mdprocesspart.cpp’, line 164, function
‘MDProcessPartitionJob::LaunchJobInternal’).”
This bug was first fixed in Cumulative Update package 6 for SQL Server 2014. You can
download the Cumulative Update package 6 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3031047
To work around this problem, you can use Hybrid OLAP (HOLAP) mode instead of Relational
OLAP (ROLAP) mode in SSAS 2014.

14. An internal error occurs in Power View when it is used to access an SSAS 2014
multidimensional cube.

This problem occurs when there is a dimension attribute that has a ValueColumn defined
in the cube and the attribute is ordered by AttributeKey or AttributeName. This bug was
first fixed in Cumulative Update package 6 for SQL Server 2014. You can download the
Cumulative Update package 6 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3031047 Facebooktwitterredditpinterestlinkedinmail