Hi @anders.e.jonsson 

What happens when you execute the execution package containing the SSL? Can you please share the execution package settings? Have you deployed the SSL instance after setting up the execution package?

In order to troubleshoot further, could you please try executing a job with only the SSL execution package (currently it looks like you are executing both MDW and SSL execution packages in one job)?

Hi @Christian Hauggaard 

When the execution package is executed in the SSL Execution panel it works fine.
These are the settings:
 

If I run the job with the SSL execution package as the only task, the result is the same. The execution fails, stating that the database doesn´t exist.
The database remains unaffected.
 

BR

Anders

Hi @anders.e.jonsson can you please try manually deleting the tabular endpoint from SSMS? Then redeploy and execute the SSL from TimeXtender, and try to run the job again  

Hi @Christian Hauggaard 

I deleted the db in SSMS, and redeployed and executed.

But I’m afraid it was the same result as before when I executed the job. “The 'Database' with 'Name' = 'xx' doesn't exist in the collection.”

BR

Anders

OK thanks for checking this. I will go ahead and create a support ticket for this, in order for us to investigate further.

Hi,

It turned out to be an access problem. The account for the TimeXtender Execution Service was not authorized to process the SSAS database.

So the error message was a bit misleading.

/Anders

Good to hear the issue has been resolved - by adding the user running the TimeXtender Execution Service under security properties for the SSAS database