I have a new installation of SQL Server 2017, along with an instance of Analysis Services Tabular 2017. I tried to connect to the SSAS instance for the first time, and I was greeted with the following error:
“Invalid connection information to establish the server connection”
I was using SSMS 17.3 to connect to the instance, so I wasn’t doing anything wonky with connection strings. I tried the following, without any success:
Nothing worked. I got a similar error when I tried to create a new project in Visual Studio using an integrated workspace. However, I could create an SSAS project using a local workspace server. I could create a model and deploy it to the server. And I could connect with Power BI Desktop to the SSAS instance. The plot thickens. Turns out I’m not the only one either who ever encountered this error:
I took a quick look at Event Viewer, and there were a bunch of errors in there as well for the OLAP service. Of course with pretty error messages:
Googling for this kind of messages led to one forum thread where someone had locale issues. Note the 8192 number, which isn’t even featured in the list of locale identifiers. Anyway, I fired up SQL Server Profiler and ran a trace while I was trying to log into the SSAS server. An error popped up:
Device attached to the system not functioning
This really didn’t make any sense. However, in one of the Discover Begin/End events, the same number appeared again: 8192 (this time explicitly marked as locale identifier). Hmmm, I had problems with weird locales before. I dug into my system, and yes, the English (Belgium) locale was lingering around. I removed it from my system and lo and behold, I could log into SSAS with SSMS again. Morale of the story: if you get weird errors, make sure you have a normal locale on your machine because apparently the SQL Server client tools go bonkers.
(note: there are some references to the en-be locale: here, here and here)
I was asked to do a review of the book Microsoft Power BI Performance Best…
This is a quick blog post, mainly so I have the code available if I…
Praise whatever deity you believe in, because it's finally here, a tenant switcher for Microsoft…
This book was making its rounds on social media, and the concept seems interesting enough…
I'm hosting a free webinar at MSSQLTips.com at the 19th of December 2024, 6PM UTC.…
The slides and scripts for my session "Tackling the Gaps & Islands Problem with T-SQL…
View Comments
Very helpful! Couldn't fix the issue until I found this info! Thanks a lot!
@Koen, how did you remove the locale?
The below worked for me
https://community.powerbi.com/t5/Issues/PBI-X64-error-July-2017-error-opening-We-weren-t-abble-to/idc-p/218417#M11138
Thank you very much for that link ! you solved my day!!!
Power BI and also Analysis Services ... from SSMS are now connected.
Hi Koen
Another cause of this which I've just stumbled upon is when the SSMS connection properties are set to connect by default to a specific SSAS database, but that database no longer exists.
Click on 'Options' and 'Connection Properties' tab, and remove the 'Connect to database' setting.
thanks man it helped me
Wow, Amazing. It helped. Thank you!
Thank you Koen, It worked.
Users like me, solution is Go to windows settings --> search for region settings --> change country or region to United states and regional format to English (United States)
Absolutely fantastic, made my day