web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / AX 2012 cube error
Microsoft Dynamics AX (Archived)

AX 2012 cube error

(0) ShareShare
ReportReport
Posted on by Community Member

hello guys! 

i have a problem trying to process and deploy cubes in SQL server

i got this:

OLE DB error: OLE DB or ODBC error.

Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Dynamics Database', Name of 'Dynamics Database'.

Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'PROJTRANSBUDGETCUBE_DIM', Name of 'Forecasts' was being processed.
Server: The current operation was cancelled because another operation in the transaction failed.
OLE DB error: OLE DB or ODBC error.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Dynamics Database', Name of 'Dynamics Database'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'PROJTRANSBUDGETCUBE_DIM', Name of 'Forecasts' was being processed.
OLE DB error: OLE DB or ODBC error.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Dynamics Database', Name of 'Dynamics Database'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'PROJTRANSBUDGETCUBE_DIM', Name of 'Forecasts' was being processed.

Any clue about this???

thanks in advance!

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Brandon Ahmad Profile Picture
    Brandon Ahmad 2,465 User Group Leader on at

    I've had this error about a Gazillion times in my life, unfortunately.  99% of the time, it means that either the credentials that Analysis Services is running under or your credentials don't have read permissions on the database.  It can also mean that you don't have Kerberos enabled, but you will see a session error in the logs if that is the issue.  

    You can think of the way that Analysis Services authentication works like this:  

    1. When you first try to connect to connect to the database, SQL server will use the credentials or impersonate settings to go to the database.  If someone used the local service account(default), it doesn't contain permissions to the datasource by default.  So, you get that error with SQL telling you that the account couldn't be configured.

    You need to go into SQL Server Configuration Manager, and change the account running under Analysis Services in that case to one that has the read permissions on the database where it loads data from.  

    2. After the server connects, it then looks at the user account(the one that is being connected with Windows Authentication), which is usually your own account to determine what can be read from the cube.  If you don't have permissions here, you will connect but won't be able to read anything or will get further errors.  So, this account needs to also have permissions(you) while developing.  Afterwards, you could just specify that everything use the service account to make things easier.  

    Google "SQL Server Configuration Manager", "Change Service Account".  If you've ever changed the account running under a windows service, you will be just fine.  

     

    ***I should add that it could truly be a case of the data mart not being setup correctly, so that there truly is no data source for analysis services to contact, but this is rare***

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    it worked perfectly!

    thanks for your help Brandon!

  • Verified answer
    Brandon Ahmad Profile Picture
    Brandon Ahmad 2,465 User Group Leader on at

    Awesome! You know its one of those issues that never goes away. I am actually dealing with a whole new nasty variant of the message on SQL Server 2012/SharePoint 2013 that goes by the cryptic term: "database server not found." But that is for the future when people start integrating Dynamics with SharePoint 2013. I am glad this worked. Your client will love the cube (and Excel). They always do.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans