IDbConnection error on process SASS database caused by Windows updates

Vladimir Kovalenko 11 Reputation points
2020-09-22T10:05:03.96+00:00

Hello,

At some point, our developer instance of Analysis Services started to give an error: Errors in the high-level relational engine. . The exception was raised by the IDbConnection interface. It does not contain any on what is wrong with it. It usually has more information, but not in this case.

26446-image.png

Having spent a couple of days, it was found that uninstalling the latest Windows updates fixes the issue. These updates were:

26482-image.png

I cannot tell which one of these two was the reason, but I assume that it was KB4507448. Trying to identify, which one of these was the reason, I installed some other updates, including one that cannot be uninstalled and also was causing the same error. So there is no way to fix it now.

And the question is how to fix it? Is it a known issue? Is there a fix for it?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,173 questions
SQL Server Analysis Services
SQL Server Analysis Services
A Microsoft online analytical data engine used in decision support and business analytics, providing the analytical data for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
1,245 questions
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. m 4,271 Reputation points
    2020-09-23T06:05:23.577+00:00

    Hi @Vladimir Kovalenko ,

    The error clearly states that the connection cannot be made to the datasource.

    "Errors in the high-level relational engine.A connection could not be made to the data source with the ..."

    Now here go to Impersonation Information tab and select “use a specific windows user name and password. Double click .ds file->
    And then follow this doc. to process and deploy your cube: how-to-process-and-deploy-an-ssas-cube
    26608-20200923windowsuser.jpg

    BR,
    Mia

    If the answer is helpful, please click "Accept Answer" and upvote it.

  2. m 4,271 Reputation points
    2020-09-23T10:22:57.36+00:00

    Hi @Vladimir Kovalenko ,

    There maybe some changes caused by windows update. Maybe the port is blocked or whatever.

    What is your SQLServer Version?
    Please use code as next to check:
    select @@version
    Then install the latest cu for your current version.

    And then check the SSCM, whether all the services are running normal, use the doamain\Administartor to restart all the sql services and then use the same account to restart your ssas service and then use this account to running your process.

    Please Enable TCP/IP protocol both in server side and client side, and set port:1433

    Note: Restart your service after every change.

    You can also use telnet to verify the connectivity is ok or not : verify-connectivity-to-sql-server.

    More information: troubleshoot-connecting-to-the-sql-server-database-engine

    BR,
    Mia

    If the answer is helpful, please click "Accept Answer" and upvote it.

    0 comments
  3. m 4,271 Reputation points
    2020-09-24T01:45:28.527+00:00

    Hi @Vladimir Kovalenko ,

    Do you check the connectivity is ok?
    Is the reply helpful?

    BR,
    Mia

    If the answer is helpful, please click "Accept Answer" and upvote it.

    0 comments
  4. Peter Johnson 1 Reputation point
    2020-11-16T13:41:47.927+00:00

    I recently had this problem - it was incredibly frustrating not to be able to understand what was going on. I still don't know what caused it, all I know is what resolved it and am posting here in case it helps someone else.

    The model data source which was causing the problems used the '.NET Framework Provider for SQL Server'. I tried a million things and was always returned the IDbConnection error as above.

    In the end I created a new and simple test tabular model from scratch which connected to the data source just fine. When I checked the data source details, it had defaulted to using provider 'SQL Server Native Client 11.0'. So I changed the provider on the problematic model, deployed it and whaddya know... it connected successfully.

    As I say I don't know the whys & wherefores but my guess is an update did something to .NET which caused the problems?

    0 comments