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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

What are the issues facing Upgrade to AX 2012 R2 from AX 2012 Feature Pack?

(0) ShareShare
ReportReport
Posted on by 5,990
Hello, we have AX 2012 Feature Pack running on Windows 2012 with no ISV or custom code components.  Separate server box for AOS, DB - SQl 2012. 
So far, we only have reporting services running on the AX 2012 FP on Win 2012.  Now, I searched this forum and found that there are lot of issues/challenges upgrading to R2. Could someone share their experience and what to avoid?  for e.g. the database size seems to grow too large, 
1. we don't have any ISV or custom code other than - setting up custom index to allow excel import for customer/vendor 
2. We installed management reporter but in a different server box. 
3. Didn't run any CU3 except that I installed the 2012 Feature Pack (downloaded from partner-source around late Sep / Oct 2012) 
 
Some Questions: 
From the upgrade guide, it talks about code upgrade in the Development Systems.  Since we don't have any ISV/custom Code, do we still need to go through these steps 

Import ISV-provided models into the development system

Assign the working layer on the development system and delete all higher models

Upgrade customer models

Import upgraded models into their layers on the development system

many thanks 


*This post is locked for comments

I have the same question (0)
  • Verified answer
    Tommy Skaue Profile Picture
    Moderator on at

    You need to upgrade to CU3 at the least. Otherwise the upgrade of the existing data based on standard code will not work properly. At least this is the notion from the in-place upgrade.

    Even if you do not have any custom code, you still need to run the code upgrade check list as part of preparation for making a complete R2 compatible modelstore.
    Could this be done in the TEST environment, the same environment you will do the first data upgrade for testing? I haven't tested it, so I don't know for sure.

    The guide says after preparing the upgraded R2 modelstore, you will import it to your TEST prior to doing the data upgrade:

    The nest step is running the data upgrade on your TEST environment and have the customer or consultants test if everything is how it should be. Your data based on standard AX should be upgraded properly. There are a lot of changes to the database schema, so this step is critical for success. 

  • ewills Profile Picture
    5,990 on at

    Thanks for the pointer and I really appreciate it.  I could not proceed with CU3 because - we are unable to install the Management utility for AX 2012 FP with OS running Win Server 2012. I couldnot find a dll.  Based on my research, others have tried to install this component from the latest version of AX.  Is that a good idea or is this the way to resolve this issue? Without AX Management Utility, is there a way to run AUX uti command?

  • ewills Profile Picture
    5,990 on at

    Will Windows PowerShell 2.0 work in stead of management utilities?

  • Tommy Skaue Profile Picture
    Moderator on at

    First of all. I think it would be best to create a new thread on new questions. :-)

    The management utilities are built on Powershell. So basically, you can open a Powershell session, but you would have to manually load the Powershell library containing the management utilities. The shortcut made by the installed simply loads a script that does all of this for you.

    You are not dependent on Powershell to run the management utilities operations. You can use AxUtil.exe as long as the AxUtilLibrary.dll is in the same folder. However, I believe setup requires the Powershell compontents to be there.

    What exactly is the error or failure when installing management utilities on Windows 2012? I have not tried that just yet.

  • ewills Profile Picture
    5,990 on at

    I resolved this issue - management framework.dll is found to be missing from a folder.

    I haven't applied CUs before. I couldn't find the steps in detail but list of KBs that it would fix etc. how is this handled?

  • ewills Profile Picture
    5,990 on at

    Hello Tommy, how are you? I have a quick question - when duplicating from Test to Development server, what is the best way to do that? Is it a virtual image copy or SQL Server backup/restore? But for backup restore, does it imply that development server be installed with R2 and then restore the database from Test to development? from the R2 upgrade Guide on page 38

    In many cases, you can also use backup and restore operations for Microsoft SQL Server to work with the model store. However, Microsoft Dynamics AX Setup can accept only model store files.
    Create development system

    Duplicate the test system
    Figure 5. Create a copy of your test system for development use.
    Duplicate the Microsoft Dynamics AX 2012 R2 test system to create the development system, which is used to upgrade customer models. In its initial state, the development system contains the standard Microsoft models for Microsoft Dynamics AX 2012 R2 and also any customer models that exist on the legacy system.
    Important:

  • Tommy Skaue Profile Picture
    Moderator on at

    Hi again, ewills. :-)

    You could copy the virtual image, but I reckon you'd still have to do some minor changes to the image afterwards.

    Here is what I did:

    I made a new set of databases based on TEST (business database and application database - aka _model).

    I had these database on the same SQL Server instance as test.

    I installed a new AOS for the purpose of DEV, but I only installed the AOS, and not the other components (like SSRS, SSAS and EP). The purpose of DEV is just to upgrade the code without losing element IDs and element handles.

    Of course by doing this, I had to tamper a bit with the restored database. I emptied out sysserversession and syssqmsettings, if I remember correctly. I also made sure all batches had status = 0, so they didn't start working. I think you get the idea.

    Hope that helps - a bit at least.

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…

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