FIX: Can't retrieve ConnectionID and SPID when running an SSAS Profiler trace in SQL Server

Applies to: SQL Server 2016SQL Server 2017 Developer on WindowsSQL Server 2017 Enterprise on Windows

Symptoms


Assume that you have SQL Server Analysis Services (SSAS) installed on Microsoft SQL Server 2016 or 2017. When you run an SSAS Profiler trace to trace Query Cube Begin and Query Cube End events, the ConnectionID and SPID values are not retrieved. However, you can see the values in a SSAS 2014 Profiler trace.

Note Even XEvents cannot capture the values.

SSAS 2016 Profiler screen shot

SSAS 2016 Profiler screen shot

SSAS 2014 Profiler screen shot

SSAS 2014 Profiler screen shot

Resolution


This issue is fixed in the following cumulative updates for SQL Server:

Cumulative Update 13 for SQL Server 2017

Cumulative Update 3 for SQL Server 2016 Service Pack 2.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the standard terminology Microsoft uses to describe software updates.