Hi @avanrijn 

Has the SSAS database been renamed in SSMS by any chance?

https://dba.stackexchange.com/questions/194407/the-database-with-id-xxxxxxx-doesnt-exist-in-the-collection

When you say it is “running successfully by hand” do you mean a manual execution of the execution package, as opposed to scheduled, or do you mean it is running successfully when you manually process the database from within SSMS?  

Hi Christian,

Your question: Has the SSAS database been renamed in SSMS by any chance?
My answer: SSAS database has not been changed,

“running successfully by hand” means a manual execution of the package in the TX interface.
Sorry I am Dutch.

Regards,

Arthur



 

Hi,

how are you authenticating to SSAS? If you are passing the user to SSAS it may be that the user running the Execution Service does not have rights to the specific database in SSAS whereas your developer account does.

Sidenote: looks like your error occurs in the ‘Default’ package - if you are scheduling that, that may not be a good idea

@avanrijn as Rory mentions, please do not use the execute the default package either manually or by schedule. It is used by TimeXtender when you execute objects within the semantic model.

The default package should look like this, please do not edit the default package:

Instead, please create a new execution package as follows, and then try to schedule this new package:

Hi @avanrijn in addition to above, I would advise to set the managed execution to Execution Time and increase the Max Threads. Please find here more information about what these settings exactly do:

https://legacysupport.timextender.com/hc/en-us/articles/360051368612--Scheduled-Execution

Kind Regards,

Devin

This was resolved by adding the user running the Execution service in SSAS.

In my case, the TestUser is running the Execution Service.

Therefore I add this user to my SSAS instance.
 

Hi Christian,

That’s right, your solution solved the issue with our client.

Thank you for looking into this matter.

Regards,

Arthur