SSMS 18.11.1 Bug Report

Hi there,

I was hoping you could have a look at what appears to be a bug in SSMS when connecting to tabular Azure instance and running XMLA script.
I have tried to keep this as simple as possible to avoid external / unexpected issues.
And, btw, using the same technique - XMLA can run without issues against local copy of a database - just not a tabular Azure one.

--
Steps to recreate the problem:

Deploy a tabular cube on Azure instance (in my case from VS) *

• Compatibility level is 1500 , Readonlymode : ReadWrite, and incidentally, the actual size is very, very small (just a couple of dimansions), as we are just doing some testing. The tabular cubes connection is present and corect in this project.

Open SSMS (-- I have installed / uninstalled (to verify the bug) 18.6, 18.9.2, 18.10, 18.11.1 - my colleague verified the same on 18.7.1 - same result on any of those)

Choose : Connect > Analisys Services > Sign into your tabular Azure instance (Azure Active Directory - Universal with MFA method)

("Sign into your account" prompt, after "Sign into your account" prompt, after "Sign into your account" prompt, after "Sign into your account" prompt ...)

Open Databases > (Your Cube) > Connections > Right click connection > Scipt connection as > Create or replace to > New query window

Run the script (either F5 or Contol + E or Button Click on Execute)

(Another "Sign into your account" prompt)

Result : (Error & script does not complete)

Error details below:

TITLE: Microsoft SQL Server Management Studio

Object reference not set to an instance of an object. (Microsoft.AnalysisServices.Controls)

BUTTONS:

OK

Object reference not set to an instance of an object. (Microsoft.AnalysisServices.Controls)

Program Location:

at Microsoft.AnalysisServices.Controls.QueryExecution.XMLAQueryThreadController.PutMessage(String strMessageText, Kind kind)
at Microsoft.AnalysisServices.Controls.QueryExecution.XMLAQueryThreadController.ExecuteExceptionChecked(ExceptionChecked function)
at Microsoft.AnalysisServices.Controls.QueryExecution.XMLAQueryThreadController.Execute()
at Microsoft.AnalysisServices.Controls.QueryExecution.XMLAQueryResultFormatter.Microsoft.AnalysisServices.Controls.QueryExecution.IAnalysisServicesExecutionControlPlugIn.ExecuteQuery()
at Microsoft.AnalysisServices.Controls.QueryExecution.AnalysisServicesExecutionControl.StartCurrentBatchExecution()
at Microsoft.AnalysisServices.Controls.QueryExecution.AnalysisServicesExecutionControl.StartExecution(String strSQL)
at Microsoft.AnalysisServices.Controls.QueryExecution.AnalysisServicesExecutionControl.Run(String textOfQuery, Int32 execTimeout)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DisplayAnalysisServerResultsControl.ValidateAndRun(String SQLScript, IDbConnection connection, Int32 execTimeout, Boolean parseOnly)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DisplayAnalysisServerResultsControl.Run(ITextSpan textSpan, IDbConnection connection, UIConnectionInfo connectionInfo, Boolean unused)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ScriptAndResultsEditorControl.DoScriptExec(ITextSpan textSpan)

As I don't believe it's only happening to me, I would be very grateful if you could investigate it please.

Thank you very much,

Dmitri