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) / Error Processing HR Ma...
Microsoft Dynamics AX (Archived)

Error Processing HR Managment Cube

(0) ShareShare
ReportReport
Posted on by Nabil Abdelrahman 1,551

Hi All

I got this error Once process HR cube by Press Process Button from Properties of HR Managment Cube by MS VS :

OLE DB error: OLE DB or ODBC error: Invalid object name 'KMACTION'.; 42S02.

Any Idea how to resolve ?

BR.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    I see no such table or view in my business database for 2012 R3 CU8.  That looks like a table from AX 2009.  Can you inspect your AOT and see if it has a configuration key or license key attached that prevents it from being synchronized to the business database?

  • Nabil Abdelrahman Profile Picture
    Nabil Abdelrahman 1,551 on at

    Hi Brandon KMACTION is a table name

  • Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    Process the cube from SQL Server Management Studio and the error will also include the SQL statement that is being executed.  Can you post that SQL statement?

  • Nabil Abdelrahman Profile Picture
    Nabil Abdelrahman 1,551 on at

    I removed that table now im reciving Errors in the high-level relational engine. The data source view does not contain a definition for the 'KMACTION' table or view. The Source property may not have been set.

  • Suggested answer
    Lance [MSFT] Profile Picture
    Lance [MSFT] on at

    The default analysis services project shipped in AX 2009 was made under the assumption that most config keys would be enabled.  Its a common problem to have to go into that project and remove references to elements that aren't actually present in the sql database.

    There's an overview of how this is done here.

    www.microsoft.com/.../details.aspx

    It looks like you've already started by identifying a table that's not present and are removing references to that table.

    The message, "data source view does not contain a definition for the 'KMACTION' table or view" means that there is still some element in the analysis services database project that is trying to use the KMAction table, so, the project build and deploy steps end up looking for that table in the data source view to try to find the definition of that table.

    Find all the remaining references to KMAction table in the project and delete those elements should get rid of that problem.  Those elements might in turn be used elsewhere in formulas like kpi or calculated measures though, so it could take a few cycles to find and remove everything that's not valid without that table.

    To find references to KMAction, in the project editor, try running the Find in Files command and searching for the string KMAction.  It's probably in either in a cube file as the table for some measure group, or in a dimension file as the table for a dimension.  If you find a measure group in a cube file using table KMIActions delete the measure group.   Similarly, if there is a dimension using that table, remove the dimension file from the project and delete any references to that dimension in any cube files.  Also look for the name of that dimension in any calculation formulas in the cube files.  If you find it is used in a calculation, that calculation needs to be deleted too.

    Then build and deploy the project.  If there are still references to the missing table or to the other elements being deleted, you'll get deploy errors and will then need to find the references to deleted objects that remain and remove those too.  Once deploy succeeds try to process.   There could be additional processing errors if there is a calculated measure or kpi using any of the deleted elements.  If you get any of those, also delete the calculation or kpi using the deleted object and then try deploying and processing again until they are all gone.  Typically the errors reported for process time calculations are rather vague and don't tell you what element was not found or even which calculation failed.  If you do get a process error from a calculation, you may have to just look through the formulas for the calculations until you spot the one containing the name of a measure or a dimension that is being removed.

    Hope this helps.

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