Hi @Christian Hauggaard ,
--- Please disregards this post, it works now --------------------------
I get this error when I try to deploy to a SSAS 2022 instance with default compatibility level 1600.
Deployment target is set to Analysis Service Universal and Campatibility level is 1600.
SSMS Version is 20. Timextender version is 6718.
Could not load file or assembly 'Microsoft.AnalysisServices.Tabular, Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
Module: TimeXtender.Tabular.Engine.2022
System.IO.FileNotFoundException
at TimeXtender.Tabular.Engine.TabularEngine.CreateModel(Model model)
at TimeXtender.Semantic.TOMEndpointDeployExecute.Deploy(SharedSemanticLayerEndpointTOM endpointModel, Boolean scriptDatabase)
at TimeXtender.Semantic.StepEndpointDeploy.DoAbstractStep(IStepSetup stepSetup)
Any ideas?
Hi,
normally you need to install the appropriate Analysis Services client libraries from here: https://learn.microsoft.com/en-us/analysis-services/client-libraries?view=asallproducts-allversions
You need all three types MSOLAP, AMO, ADOMD
Microsoft is going to stop delivering MSI installers from the end of the year, so you will need to switch to NuGet at some point. The NuGet site is a mess, so I am not sure exactly which you need to install. Theoretically NuGet would solve some of the version mismatch issues you can run into as it bundles multiple runtimes.
I sometimes find I need to explicitly select 2019 as deployment target and 1500 as compatibility level, but this differs. Some work with automatic settings for the deployment target.
I’m receiving the same for SQL 2017
Could not load file or assembly 'Microsoft.AnalysisServices.Tabular, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
Module: TimeXtender.Tabular.Engine.2017
System.IO.FileNotFoundException
at TimeXtender.Tabular.Engine.TabularEngine.Process(Model model)
at TimeXtender.Semantic.StepEndpointExecute.DoAbstractStep(IStepSetup stepSetup)
I’ve installed the client libraries as above but still no luck. @rory.smith, I assume 1400 would be the correct compatibility mode to set if I explicitly set the version to SQL 2017. If so, I also tried this to no avail.