SSMS raises "Unable to establish server mode" error if SSAS encounters errors during startup

SSMS raises "Unable to establish server mode" error if SSAS encounters errors during startup by Alberto Ferrari [SQLBI]

Closed

as Fixed

Type:	Bug
ID:	686801
Opened:	9/2/2011 2:29:46 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Today I cannot access my SSAS Denali Server, SSMS returns this error which, unexpectedly, does not return any result on google, and seems to be related to SSMS asking SSAS which serverMode is using.

The scenario is that I have a big IMBI database which fails to load due to an out of memory error during startup of the server (I have checked it with the flight recorder). I tried to rename the folder of the database but… no luck, the error was still there and the log was showing (of course) an error loading the database.

To make the server work again, I had to delete the db file of the offending database, manually delete the folder and now everything seems to work.

Thus, it seems that if SSAS has some error during startup, it will not answer to his server mode value and SSMS refuses to connect to it.

Details (expand)

English

SQL Server Denali CTP 3

Analysis Services

Windows Server 2008 R2 Enterprise (SP1)

English

Rename a folder containing an IMBI database, so that SSAS raises an error during startup. Restart the service and try to connect to SSAS from SSMS

===================================
Error connecting to '(local)\SQL2011'.
===================================
Unable to establish server mode. (ObjectExplorer)
------------------------------
Program Location:
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.SupportedServers.IsIMBIServer(SqlOlapConnectionInfoBase connectionInfo)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.SupportedServers.GetHierarchyBuilder(SqlOlapConnectionInfoBase connectionInfo)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorerControl.GetObjectBuilder(SqlOlapConnectionInfoBase ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorerControl.BuildDataModel(SqlOlapConnectionInfoBase ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorerControl.GetHierarchy(SqlOlapConnectionInfoBase ci, String displayName)
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ConnectToServer(UIConnectionInfo connectionInfo, IDbConnection liveConnection, Boolean validateConnection)

Connection works

X64

0 attachments

Posted by Microsoft on 7/25/2012 at 9:41 PM

Hello,

This issue with SSMS is resolved with the upcomming service pack release.

Regards,
Kasper de Jonge
Analysis services team

Posted by jjs781_yahoo.com on 7/20/2012 at 12:16 PM

I have a similar issue where I am receiving the same error. There are a number of RDBMS instances on my dev SSAS server which consume most of the available memory and spikes RAM utilization to near 100% at times. Once usage drops back down, SSAS remains unresponsive until the service is restarted. 2008 R2

Posted by Christopher Webb on 5/28/2012 at 8:57 AM

I also got the same error when SSMS was trying to connect to a database that no longer existed on the server: http://cwebbbi.wordpress.com/2012/05/28/unable-to-establish-server-mode-error-in-ssms/

Posted by Microsoft on 10/11/2011 at 2:07 PM

And sorry Alberto for the typo in the reply, I assumed you were Marco because he files a lot of bugs.

Cathy

Posted by Microsoft on 10/11/2011 at 2:05 PM

Hi Marco, I regret to inform you that the previous fix we had was troublesome. We will have a developer look at an alternate solution in the future.

Regards,
Cathy Dumas

Posted by Microsoft on 9/29/2011 at 4:51 AM

Hello Alberto,

We are happy to inform you that we have found a solution for this problem. You will now be able to connect to the server when one or more databases are toublesome.

Regards,
The Analysis Services Team

Posted by Microsoft on 9/2/2011 at 12:12 PM

Thank you for the feedback. We are investigating this issue and will get back with you.