Skip to main content

Notifications

Microsoft Dynamics AX forum

*Modelstore is not a recognised Model Store: Inplace Upgrade to R2

Posted on by Microsoft Employee

HI,

I am doing an in place upgrade from AX 2012 Feature Pack CU3 to AX 2012 R2. I am following the upgrade guide.

At Step: Run Microsoft Dynamics AX 2012 R2 Setup on the test system -> Point 8 "Run Setup and confirm that an upgrade is being performed. On the Add or modify components page, select Application Object Server (AOS). When prompted, provide Setup with the AOS and database configuration values you recorded above."  for AOS upgrade, i didnt received any such upgrade confirmation page from set up and i continued with R2 AOS installation.

The AOS installed with a warning and its not starting. Error: "The * modelstore (Created by R2 Set up upon upgrade of DB) is not a recognised model store"

i am running short of options on how to proceed, Please help!

Regards,

Gaurav

*This post is locked for comments

  • skaue Profile Picture
    skaue on at
    RE: *Modelstore is not a recognised Model Store: Inplace Upgrade to R2

    Glad you figured it out.

    The SecurityAdmin permission grants the user to define (modify) permissions to the database.So any user with SecurityAdmin can modify the permissions on the database. Normally, the AOS account needs ddladmin (ie. modify the database schema), datareader and datawriter. In addition it needs a set of special rights on a list of database objects. The easiest way to secure the service account access with least privileges is to use AXUtil. In PowerShell it is just a matter of running the "Initialize-Modelstore" with the "AOSAccount" command switch.

    technet.microsoft.com/.../jj720267.aspx

    "-AOSAccount<String>

    Grants permissions to the model store in the Microsoft Dynamics AX database to the account that an Application Object Server instance is running as. The account is granted EXECUTE rights for the appropriate stored procedures, and SELECT rights for the appropriate views. Use this account primarily when moving a model store to a new environment."

    By giving dbowner, you are granting full permission on the database.  

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: *Modelstore is not a recognised Model Store: Inplace Upgrade to R2

    HI Tommy,

    Thanks for taking out time to reply.

    I followed the steps from technet article, as you advised. The error was not getting resolved. By looking at logs, the hint was that my account, which i used for upgrade, didnt had appropriate permissions on *Model DB.

    I tried to add my account as SecurityAdmin to *ModelDB, but was unable to do so as my account was made owner of this DB. So i changed the Owner of *Model DB to another account, added my account as securityadmin, and voila! it worked :)

    Regards,

    Gaurav

  • skaue Profile Picture
    skaue on at
    RE: *Modelstore is not a recognised Model Store: Inplace Upgrade to R2

    Hi Gaurav

    I will assume you have successfully split the database and you are now preparing to setup the AOS for TEST.

    Setup will automatically check to see if there are any other AOSes installed on the environment. If there are, it will prompt you and ask if you are doing an upgrade the second you tick the "Application Object Server". This is the step where you select what components you are installing. If you click YES, if will later on ask you which instance you want to upgrade. If you don't have an RTM instance installed, you will not be able to select anything. If you click NO I believe setup will ask you what database you want to connect to.

    However, if there is no AOS installed, it will not ask you if you are doing an upgrade. I have seen the error "The selected database is not a model store database", but I believe it was related to how I ordered the components during installation.

    I have successfully split the database first. Since the database server was on a different server, I ran the PowerShell command "Initialize-Modelstore -server dbserver -database modelstoredatabasename -AOSAccount domain\aosservice" in order to ensure the service account will have sufficient access when I installed the AOS. I then installed the R2 AOS and pointed it at prepared database.  

    Pay attention to the installation logs under "C:\Program Files\Microsoft Dynamics AX\60\Setup Logs\", one folder for each run, and the file "DynamicsSetupLog.txt".

    Make sure to install in that order; DB split (1), AOS (2), Client+Debugger+Utils (3). The graphics on the in-place upgrade poster is ordering these steps wrong (at the time of writing). The TechNet article has it right.

    I 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

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,818 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 229,147 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans