After migration the semantic layer can't execute.

Hi ​@rbrandsma 

please see the following article

• Error: Login failed error when executing first dimension

Hi ​@Christian Hauggaard, 

Thanks for your quick response. 

I have followed the article that you linked. Bur unfortunately this did not solve the issue. We even tried to raise the user mapping levels to db_owner instead of db_datareader. 

​@rbrandsma can you please confirm which user is running you SQL Server Analysis Services service? e.g. NT Service\MSSQLServerOLAPService

Please make sure to give this user read access to the MDW

Also can you please send a screenshot of your tabular settings similar to below?

Also can you please confirm if you are using SQL server authentication for your MDW?

Hi,

Assuming you are trying to leverage the built-in service account for SSAS: NT Service\MSSQLServerOLAPService (or slightly different naming if you are running a named instance)

if TimeXtender is not running on the same machine as your SQL Server / SSAS instance and both VMs are Windows AD domain-joined or not joined to a domain at all then you need to use SQL Server Authentication or a service account to solve this.

The NT Service \**** accounts are local accounts that cannot be interacted with from outside the VM (mostly). If your VMs are domain-joined you can use a “traditional” service account to have SSAS authenticate to SSAS. If your setup uses local accounts only, you will need to use SQL Server authentication (and should really consider using Windows AD / Entra ID / another identity provider).

Hi ​@Christian Hauggaard,

As requested the screenshots 

SQL Server Analysis Services Service & User:

 This user has access to the MDW database mentioned in the error message:

Tabular endpoint settings:

They are not using SQL Server authentication (see screenshot below). As mentioned this was an upgrade to a new version of TX and these are the settings taken over from the “older” version of TX. 

TX is installed on an application server and connects to a database server. 

​@rbrandsma can you please try using SQL server authentication instead?

​@Christian Hauggaard 

We can certainly try!

One question though….In your screenshot you are using the built in SA account. I reckon we should not be using that. 

But what account should we use? The Service account from the application server that is used to start the TimeXtender Services? Or does this not matter?

I disabled the global database option of the MDW datawarehouse and changed the authentication to SQL Server Authentication. Then the admin I'm working with filled in his credentials. Saved the changes and tried to execute the semantic layer again. There was no change in the results. Same error message appeared on executing the semantic layer. 

Hi ​@rbrandsma 

Can you try to change the two settings Deployment Target and Compability Level so they are their default values.

Like this.

Hi ​@Thomas Lind 

Tried changing the settings you advised, but still the same error message appears. Also tried reinstalling the Analysis Services client libraries, all without any result. 

Would there be any chance to have some one assist with this in a different capacity?