Ever encountered the above error when starting SQL server management studio and connecting to SSAS ? The error has a few different root causes one of which is detailed in the link below.
However this is not the only cause, the error can even occur if the databases are not operational. E.g. in this case the database was corrupt it opened fine in SQL Server 2014 management studio but refused to open in SQL 2012 management studio.
Once the databases were dropped and I tried connecting to Analysis Services and it went thru fine.
Here is another blog that covers the issue as having the root cause as incorrect default database in connection sting.
This post was written by Jayanth Kurup. A Microsoft SQL Server Consultant and Trainer based out of Bangalore, India. Jayanth has been working on MS SQL Server for over 15 years. He is a performance tuning and Business Intelligence expert. Having worked with companies like Microsoft, DELL, Wells Fargo, Thomson Reuters and many other fortune 100 companies. Some other technologies Jayanth works on include Microsoft Azure, PowerBI, Python and AWS. When he isn’t consulting or training, Jayanth like to travel, paint and read. He is also very active in social causes and the founder of Enabled Business Solutions. Visit his company by clicking the link in the menu or email him directly.
