Import model store error AX 2012 R2 CU7

-
For model databases that have been upgraded to CU7 there is a possibility that they might be missing the following tabels.

- ModelOperatioin
- ModelOperationHistory
- ModelCustomLayerConflicts

The result will be that following error in the eventlog in the sql environment when applying the temp schema using axutil.

AXUtil operation failed : ImportStore

Cannot find the object 'ModelOperation', because it does not exist or you do not have permission.
Cannot find the object 'ModelOperationHistory', because it does not exist or you do not have permission.
Cannot find the object 'ModelCustomLayerConflicts', because it does not exist or you do not have permission.

When applying the the temp schema with the powershell command Import-AXModelStore the output in the console with be a flush of red SQL commands with DROP ******.

Solution:
Find a model database for a CU7 environment with the tabels. Use SQL manager to generate create scripts and run them in the model database for the environment where applying the modelstore schema fails.

- ModelOperatioin
- ModelOperationHistory
- ModelCustomLayerConflicts


Comments

  1. Unknown09 May, 2015 00:10

    THANKS. This issue seems also related to an upgrade to CU8. Your post solved my problem!

    ReplyDelete
  2. Berna Kahya24 February, 2017 00:07

    Thank you

    ReplyDelete
  3. Anonymous06 September, 2017 03:01

    Or use Initialize-AXModelStore (after applying latest kernel):
    https://technet.microsoft.com/en-us/library/jj720267.aspx

    "The Initialize-AXModelStore cmdlet can be used to ..., update the existing model store"

    ReplyDelete
  4. Anonymous06 September, 2017 13:27

    initializing and then apply schema works

    ReplyDelete
  5. Usimabrom-ma_Phoenix23 April, 2022 07:18

    Usimabrom-ma_Phoenix Damon Knecht https://marketplace.visualstudio.com/items?itemName=concestheji.Descargar-Protect-The-Campus-gratuita
    barkglabampor

    ReplyDelete
  6. sumppiKiqwo199224 May, 2022 15:21

    sumppiKiqwo1992 Annie Martinez click
    aragarpa

    ReplyDelete

Post a Comment

Popular posts from this blog

How to disable auto enabled flight key using KillSwitch

-
Image
Microsoft is introducing new functionality into Dynamics 365 for Finance and Operations with flight keys in every other new release. For this they use  Flight  classes so that the changes are automatically applied and can be reversed.  Example of a flight class that control the functionality of a new set of functionality.  When a flight key that enable functionality can be found in the flight key table  SysFlighting To disable the functionality don't delete or change the enabled flag on the flight record, instead insert a KillSwitch  record. The KillSwitch record will ensure that the flighed functionality will stay disabled as long as it exist in the flight table.  In an environment that Microsoft maintain can raise a support ticket in LCS to disable specific flight keys.  SQL statement for insert the KillSwitch record.  DECLARE @flightName NVARCHAR(100) = 'WHSWorkCancelForcedFlight_KillSwitch' IF NOT EXISTS (SELECT TOP 1 1 FROM SysFlighting WHERE flightName = @flightName
Read more

Technical intro to Feature management in D365FO

-
Image
Feature management is an alternative to configuration keys for releasing and introduce a new features into D365FO.  MS is still releasing updates around the framework but the existing state as per 10.0.9 provide all we need to get started with releasing functionality that is controlled by the feature management framework.  The key to the feature framework is the feature class, in my example below see the class  pekTestingFeature. It is used as a descriptor for the feature and the flag to indicate if the feature is enabled or not. Once the class is created and compiled, users can navigate to Feature management  under System administration  and enabled/disable the feature. It is possible to make a feature enabled by default or disable the possibility to disable the feature. If the feature doesn't automatically appear, run the Check for updates button.   The feature class can be applied to menu items and menus. If enabled the menu item or menu will be visible to the
Read more

Continuous integration and deployment Power platform FinOps tweaking

-
Image
If you are working with the new unified development environments and CICD pipelines described here .  You might find the fact that we have to update the pipeline with the platform and application version annoying.  A quick way to get around this if you are using azure hosted agent pipeline as per this repo is to pull the number from the package.config and using it in the create deployable package task as per the two example tasks below.  The first powershell task will pull the version from the nuget files and save it to variable that can be reused in later tasks within the job. 
Read more