SSAS error the source database does not exist, the source table does not exist, or because you do not have access to the data source

Christie R 1 Reputation point
2021-03-03T22:01:33.613+00:00

Hello everyone,
I'm hoping someone could help me resolving this error...

The operation failed because the source database does not exist, the source table does not exist, or because you do not have access to the data source.
More Details:
OLE DB or ODBC error: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done..
The current operation was cancelled because another operation in the transaction failed.

I know I don't have source database/table or access issues because I have other models using the same server, database and table that work properly.

I have a SSAS tabular model containing 14 views imported from sql server. (FYI, The views were created with the exact same code (except a WHERE clause) from one source table in the same sql DB). Everything deployed and processed (full) fine. However I get the error when I process it again, but only on some of the tables. If I delete the problem table/s and import it again, then would process successfully. The next time, some other tables would have the same error... I can't find a pattern, except the error happens when a table has new data? Can't be sure...

Anyone know what might be causing it? Thank you!!!

SQL Server Analysis Services
SQL Server Analysis Services
A Microsoft online analytical data engine used in decision support and business analytics, providing the analytical data for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
1,245 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lukas Yu -MSFT 5,816 Reputation points
    2021-03-04T08:06:27.41+00:00

    Hi,

    Data change should not cause this issue, the data would be load into SSAS database after deploying and processing. BTW, when would you recieve this error, when processing or else?

    I'd like to suggest you to check the Datasource impersonation info and also connection string see if they are the same as other cube.
    Or you could create new Datasource while choosing create datasource directly from other other project. And use the datasource from that working see if it works.

    If the issue persists after above checking and testing, you could go through the views , see if there are any security rules that apply to them, that impernated account can not access them.

    Regards,
    Lukas