No results are returned in the Analyzer in the Information Centric Analytics (ICA) console, or the data are stale and haven't been updated overnight. In addition, the RiskFabric Processing job appears to run indefinitely. The job's history in the SQL Server Agent shows CustomComplianceData (step 15) is the last step to have completed, with processing hung on Risk Fabric cube processing (step 16). Running a SQL Server Profiler trace against the SQL Server Analysis Services (SSAS) server hosting the RiskFabric cube shows no processing activity.
Version : 6.x
Component : Microsoft SQL Server
Cube processing durations increase or processing hangs after installing the security update for SQL Server 2016 SP2 CU7, published July 7, 2019, to address CVE-2019-1068, per Microsoft document KB4505222:
https://support.microsoft.com/en-us/help/4505222/security-update-for-sql-server-2016-sp2-cu7
NOTE: link available as of 2023-02-25
The following builds are affected:
SQL Server 2022 is not known to be affected by this issue.
This issue is resolved by upgrading both Microsoft SQL Server and Microsoft SQL Server Analysis Services to the latest available build. Per Microsoft document KB4589170, a fix for this issue was initially released in the following updates:
NOTE: link available as of 2023-02-25
For some environments, including those with fewer than 16 CPU cores, it's also necessary to disable the CoordinatorSafeJobUnblocking setting on the Analysis Services (SSAS) server after installing a patched version of SQL Server. To disable this setting, follow this procedure:
%SystemDrive%\Program Files\Microsoft SQL Server\MSAS<n>.MSSQLSERVER\OLAP\Config\(where <n> refers to the version of SQL Server)
CoordinatorSafeJobUnblocking
<CoordinatorSafeJobUnblocking>1</CoordinatorSafeJobUnblocking>
<CoordinatorSafeJobUnblocking>0</CoordinatorSafeJobUnblocking>
NET STOP "SQL Server Analysis Services" && NET START "SQL Server Analysis Services"
NET STOP "SQL Server Analysis Services (<instance name>)" && NET START "SQL Server Analysis Services (<instance name>)"
The attached document from the Bay Dynamics consulting team provides a root cause analysis of cube processing issues experienced after installing cumulative updates 7 through 13 for Microsoft SQL Server 2016 SP2. These issues were caused by a security patch for SP2 CU7 released by Microsoft in July 2019 which had adverse effects on cube processing in SQL Server Analysis Services (SSAS). Note that this issue also affects builds of SQL Server 2017 and 2019. Refer to the Cause section of this article for affected versions and builds.
After applying the CU7 patch to SQL Server environment, SQL Server Analysis Services is adversely affected during ICA's nightly processing job, resulting in cube processing hanging indefinitely. After adjusting settings in Analysis Services and rebooting the server, manually processing the cube proved successful, however only in a sequential fashion. By nature, serial processing proved to be much more time consuming, increasing the overall cube processing time from 30 minutes under the former parallel setting, to an hour and a half. This behavior was later replicated in Bay Dynamics’ internal environment by applying the same SQL patch. After removing that patch, cube processing was allowed to continue successfully, further underscoring the point that this issue was directly related to the security update provided by Microsoft.
If patching SQL Server is not possible, the process in the attached document can be followed as a workaround for the issue described above, which will enable the cube to process successfully. Note that as previously mentioned, this will increase the duration of cube processing; however, it will allow data in Risk Fabric to update.