SQL Server

Troubleshooting SQL Server 2014 Analysis Services problems (Part 3)

Troubleshooting SQL Server 2014 Analysis Services problems (Part 3)

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

1. If you use SSAS 2014. When you run a Multidimensional Expressions (MDX) query
against a Many-To-Many dimension, the memory consumption increases very quickly,
and surpasses HardMemoryLimit after some time.

In this case, the MDX query may not be canceled as expected when the total consumed
memory exceeds HardMemoryLimit. When physical memory is exhausted, the server may
become unresponsive. This bug was first fixed in Cumulative Update package 7 for
SQL Server 2014. You can download the Cumulative Update package 7 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3046038

2. High CPU usage after you uses DTExec utility to process SSAS 2014 data mining models.

In this case, after the processing finishes, the client keeps running infinitely with
very high CPU consumption. However, you cannot find the related thread that is running
in the SSAS server. This bug was first fixed in Cumulative Update package 7 for
SQL Server 2014. You can download the Cumulative Update package 7 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3046038

3. When you run a MDX query with subselect of different granularities after an
UPDATE CUBE statement, the query returns incorrect results for some measures.

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

4. After you divide a table into more than one logical part, and then you process
the partitions, some data in the partitions is updated incorrectly.

In this case, tabular queries (DAX/MDX) returns corrupted or incorrect information.
For example, some positive values in one or more table columns are changed to negative
values. This bug was first fixed in Cumulative Update package 7 for SQL Server 2014.
You can download the Cumulative Update package 7 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3046038

5. The error occurs when you schedule data refresh by defining Secure Store ID
in SQL Server PowerPivot for SharePoint 2013.

This is the error message text: “The provided Secure Store target application is
either incorrectly configured or does not exist”. This bug was first fixed in Cumulative
Update package 7 for SQL Server 2014. You can download the Cumulative Update package 7
for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3046038
To work around this problem, you can add the user to the administrator group so that the
Secure Store Service has the “Manage Target Application” permission.

6. When you run a MDX query against a large database that has a sub-select of different
granularities, the query may take a much longer time than the single granularity
under the same logic.

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

7. When you execute a MDX query to retrieve aggregated values on the cube, the result
of the aggregated values is incorrect.

This problem occurs when you have a cube that contains unary operators (~) on a regular
dimension in SSAS 2014. This bug was first fixed in Cumulative Update package 8 for
SQL Server 2014. You can download the Cumulative Update package 8 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/3067836

8. SSAS 2014 crashes when cube writeback commit transaction and processing batch
are executed at the same time.

This problem occurs when you use SSAS 2014 with roles that use cell security expressions.
This bug was first fixed in Cumulative Update package 8 for SQL Server 2014. You can
download the Cumulative Update package 8 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3067836

9. The error occurs when you update the pivot table in a SharePoint document.

This is the error message text: “Cannot find the OLAP cube Model. Either the OLAP
database has been changed or you don’t have permissions to connect to the cube.
The PivotTable report was not refreshed.” This problem occurs when you do not have
System Administration permissions on the SSAS 2014 instance. This bug was first
fixed in Cumulative Update package 10 for SQL Server 2014. You can download
the Cumulative Update package 10 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3094220

10. When you execute a query to retrieve data from the session cube, the result
may contain data that you do not have permission to access.

This problem occurs when you create a session cube by using dynamic role-based
security in SQL Server 2014. This bug was first fixed in Cumulative Update
package 10 for SQL Server 2014. You can download the Cumulative Update package 10
for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3094220

11. SSAS 2014 crashes when you execute an MDX query that contains lots of
Union expressions.

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

12. The Execute SQL Task may stop responding when you run the SSIS 2014 package.

This problem occurs when you use Microsoft Analysis Services OLE DB Provider for
MSOLAP 11.0 together with an Execute SQL Task.
This bug was first fixed in Cumulative Update package 10 for SQL Server 2014.
You can download the Cumulative Update package 10 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3094220
To work around this problem, you can use Microsoft Analysis Services OLE DB
Provider for MSOLAP 10.0.

13. It takes longer than expected when you run a query with non-admin user
role in SSAS 2014 in Tabular model.

This problem occurs when you execute a query that contains the MEMBER_CAPTION
or MEMBERVALUE functions. This bug was first fixed in Cumulative Update package 10
for SQL Server 2014. You can download the Cumulative Update package 10 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3094220

14. If you cannot connect to SQL Server 2014 Analysis Services, ensure that
SQL Server Browser service is started and was running under the account
that has local administrator rights.

The SQL Server Browser service enables client applications to connect to a named
instance of Analysis Services by specifying the name of the instance rather than
the TCP port number. To connect to SQL Server 2014 Analysis Services by specifying
the name of the instance, the SQL Server Browser service must be running under the
account with local administrator rights. For example, you can configure to run
SQL Server Browser service under the local system account.

15. The error occurs when you run the ProcessAdd command after you make changes
to the partition on a server that is running SQL Server 2014 Analysis Services.

This is the error message text: “Internal Error: An unexpected exception occurred”.
This error occurs if you run the ProcessAdd command before you restart the computer.
To work around this problem, you can restart the computer before executing the
ProcessAdd command. Facebooktwitterredditpinterestlinkedinmail