D
David.Squires
Guest
Hey All,
Our team ran into this error:
[Analysis Services Execute DDL Task] Error: Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClientUI, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified
We had VS 2015 + SSDT 2015, and VS 2017 installed (no SSDT2017).
We have a VS2015 (SQL 2016) SSIS package with an "Analysis Services Execute DDL Task" that worked fine. After installing SSDT2017, we got the error above.
We had an environment without VS 2017, to confirm that's what broke it and sure enough it did. Confirmed by googling.
Microsoft has a fix for this in a CU: SQL server CU Fix
My question is, why is it a SQL server install fix instead of a Visual Studio fix?
I have SQL Management Studio 2017 installed in the same development environment. Should I install the newer version of SSMS and will that fix the problem? The fixed version of SSMS 2017 is version 14.0.3030.27, I have version 14.0.17119.0.I am hesitant to just try it and mess up the environment even further.
I would guess we also would need to update the version of SQL on the servers this package will run on eventually as well?
Continue reading...
Our team ran into this error:
[Analysis Services Execute DDL Task] Error: Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClientUI, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified
We had VS 2015 + SSDT 2015, and VS 2017 installed (no SSDT2017).
We have a VS2015 (SQL 2016) SSIS package with an "Analysis Services Execute DDL Task" that worked fine. After installing SSDT2017, we got the error above.
We had an environment without VS 2017, to confirm that's what broke it and sure enough it did. Confirmed by googling.
Microsoft has a fix for this in a CU: SQL server CU Fix
My question is, why is it a SQL server install fix instead of a Visual Studio fix?
I have SQL Management Studio 2017 installed in the same development environment. Should I install the newer version of SSMS and will that fix the problem? The fixed version of SSMS 2017 is version 14.0.3030.27, I have version 14.0.17119.0.I am hesitant to just try it and mess up the environment even further.
I would guess we also would need to update the version of SQL on the servers this package will run on eventually as well?
Continue reading...