In-place upgrade to AX 2012 R2 or AX 2012 R3

This topic contains 2 replies, has 3 voices, and was last updated by  Locus IT 8 months, 1 week ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #20597

    Abigail Donovan

    Can anyone tell me how to perform in-place upgrade to AX 2012 R2 or AX 2012 R3?


    Abu Mohammed Ali

    An upgrade from one version of Microsoft Dynamics AX 2012 to another is known as a minor version or in-place upgrade. This type of upgrade requires no source-to-target workflow of the kind that is used when you upgrade from Microsoft Dynamics AX 4.0 or Microsoft Dynamics AX 2009. Instead, the upgrade operations are performed on a copy of your production system.

    An upgrade to AX 2012 R2 is almost the same as an upgrade to AX 2012 R3 from a version prior to AX 2012 R2. The recommended topology for this in-place upgrade scenario requires three Microsoft Dynamics AX systems:

    Production – The existing system that you are upgrading.

    Test – A copy of your production system that is used to upgrade the database architecture, test new components, and test the data upgrade.

    Development – A copy of your test system, where you upgrade your customized code and other metadata.

    Upgrade Steps

    Step 1. Synchronize, Compile and Generate CIL on the AX 2012 R2 application.

    Step 2. Stop AOS & then back up model and business data databases.

    Step 3. Restore the model and business data databases in a new environment.

    Step 4. Start the AX 2012 R3 installation setup on a new environment.

    Step 5. Select only the databases component.

    Step 6. Select configure existing databases.

    Step 7. In this step, Assign the R2 database and make sure that the Baseline database name field is left blank during this procedure.

    Step 8. On the Select additional models page, select the Foundation model, Foundation Upgrade model, and any other models that you require for your deployment. Select the Foundation Labels model only if you are using country/region-specific features.

    Step 9. Now install all other required AX components.

    Step 10. Now, assign the database and upgraded baseline database in this step.

    Step 11. Once, the installation is completed then compile the whole application using the command “axbuild xppcompileall” from the command prompt. This compiled the whole application for me in just 30 to 40 minutes.

    Step 12. Now restart AOS and proceed with the code upgrade & data upgrade checklists. Follow the code upgrade document on the complete details.


    Locus IT

    Hello Abigail,

    The upgrade story from AX2012 RTM (R0/R1) will be more or less the same as when upgrading to R2. The significant part was the fact the entire Dynamics AX Database was split in two, one database for business data and one for the application.

    What is interesting with the R2 to R3 upgrade is that we now have two databases to begin with. Microsoft has solved this by doing the following:

    1) Create a R3 Upgrade Baseline named YOURDB_UpgradeR3Baseline
    2) Export the R2 Modelstore to disk
    3) Import the R2 Modelstore to the R3 Upgrade Baseline
    4) Replace all the Microsoft models in the actual modelstore with new shiny fresh R3 models!

    From there you have more or less the same upgrade story as you would have when upgradring RTM to R2 or R3. The story is divided in two stages:

    1) Code upgrade
    2) Data upgrade

    If you’ve done R2 upgrades, you will remember that code upgrade is recommended to do this in a isolated environment. It doesn’t have to be on a dedicated server, as long as you know how to keep the environments separated. The code upgrade should be done on a copy of the newly configured R3 Modelstore, and the whole idea is to make sure you end up with an upgraded R3 modelstore that keeps the element IDs. Otherwise, you’ll end up with having to start over.

    The code upgrade is done in a cyclic manner, and the upgrade guide explains it beautifully;

    1) Import modelstore
    2) Delete top most layers
    3) Upgrade current layer
    4) Export current layer models
    5) Back to step 1 and start working on next layer.

    1. First you choose a Database upgrade
    2. You then choose to Configure an existing database
    3. You point to your prepared, but yet not upgraded R2 database. Do not fill in Baseline, because Setup will make one for you.
    4. You will need to provide a location for where the exported modelstore from R2 will be saved. When this part is completed, you will install the AOS, a Client, Debugger and Management Utilities – all tools necessary for compiling. The debugger will be used for the code upgrade part. Remember I chose to do both the code and the data upgrade on the same server.
    5. Now, I did select the newly created R3Baseline for the first AOS installed, but only to show you the naming convention Microsoft used for the database. The baseline database comes to play when you are in the code upgrade phase. So I did eventually reconfigure my second AOS to use the baseline when I upgraded my layers to R3.
    6. Finally, you define the Instance and ports.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Skip to toolbar