Logg på med Microsoft
Logg på, eller opprett en konto.
Hei,
Velg en annen konto.
Du har flere kontoer
Velg kontoen du vil logge på med.
Engelsk
Beklager. Denne artikkelen er ikke tilgjengelig på språket ditt.

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.

About SQL Server builds

Each new build for SQL Server 2016 contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server: 

Latest cumulative update for SQL Server 2017

latest build for SQL Server 2016

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.

Trenger du mer hjelp?

Vil du ha flere alternativer?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Var denne informasjonen nyttig?

Hva påvirket opplevelsen din?
Når du trykker på Send inn, blir tilbakemeldingen brukt til å forbedre Microsoft-produkter og -tjenester. IT-administratoren kan samle inn disse dataene. Personvernerklæring.

Takk for tilbakemeldingen!

×