Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
Invoice Settlements/Discounts/Reversals
SSRS and SSAS Integration
Workflow
Hi, what is the best way to upgrade from AX 2012 FP installed on Win server 2008 R2 to AX 2012 R2 with Win Server 2012.
From what I understand, run the in-place upgrade on current production server (AX 2012 FP on Win Server 2008 R2) and upgrade to AX 2002 R2
and then Install a fresh R2 copy on Win server 2012 and then restore the database copy.
Appreciate if someone could clarify.
any thoughts from anyone?
Since the only supported upgrade path from AX 2012 RTM with or without FP (v 6.0/6.1) is an in-place upgrade, meaning you need to upgrade to R2 (v6.2) on top of an existing RTM, the answer is sort of already given.
If you plan to do this on a new server (your Windows Server 2012), then establish a copy of your RTM version on that new server, and do the in-place upgrade on that server.
I highly and strongly recommend you study the in-place upgrade guide here:
technet.microsoft.com/.../jj733502.aspx
You will need to follow this guide regardless of what strategy you choose.
Tommy Skaue | Dynamics AX Developer from Norway | http://yetanotherdynamicsaxblog.blogspot.no/ | www.axdata.no
hi, I am currently running AX 2012 Feature Pack on Win 2012 OS. (and not AX 2012 R2 RTM). yes. I am able to install feature pack on Win 2012!
Hello!
It is necessary to be carefull about this upgrade. From my last environment i was not able to install the Enterprise Portal for AX2012 using Windows Server 2012.
Some AX components cannot be avaiable using Windows Server 2012.
Dont forget to mark this as na answer!
Francisco Silva Jr.
Microsoft Dynamics AX
http://fsilvajunior.blogspot.com.br
This posting is provided "AS IS" with no warranties, and confers no rights.
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 any ISV or custom code other than - setting up custom index to allow excel import for customer/vendor
2. I have installed management reporter but in a different server box.
3. I don't have any CU except that I installed the 2012 Feature Pack (downloaded from partnersource around late Sep / Oct 2012)
You need to have at least CU3 before starting the upgrade process. You also need to remove the "Foundation Labels II" if you have this installed.
As with any CU upgrade, you need to go through a code upgrade process in order to preserve any customization to code in any layers above Microsofts layers.
Thanks. is there a blog that show how to run the CU3? I have a question - Even though we don't have any custom code, does it mean, we still need to run the code upgrade process?
I have seen number of blogs that show how to install Feature Pack on CU3. I thought feature pack came after CU3. If I have Feature Pack, do I need to run Cumulative Update 3? I am not 100% clear on this. could you please clarify?
Installing a CU is more or less the same as when installing a Rollup in AX 2009. You still need to examine any overshadowing elements in non-Microsoft application layers. If you don't have any code changes at all above Microsofts layers, then the code upgrade check list will more or less be a matter of compiling the application, compiling CIL and synchronizing the database.
Feature Pack is built on CU 2. You can read more about it here:
blogs.technet.com/.../dynamics-ax-2012-feature-pack-servicing.aspx
CU 3 and CU 4 came later. I have upgraded from AX2012 RTM to AX2012 R2 on an application without Feature Pack but with CU4. The in-place upgrade guide states you need CU3 at the least. The upgrade will work whether you have Feature Pack or not.
skaue,
You were able to successfully upgrade from Ax2012 RTM to Ax2012 R2? I get an SQL error (SQL error description: [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid column name 'PARTITION'.) when I open Ax to start the "data upgrade checklist for in-line upgrade" checklist. Did you experience this as well? I tried ignoring it to see if completing the checklist would correct it but when I got to the "Launch data upgrade" step, 5 of the scripts failed and now I can't progess beyond that point.
I'm still using WinServer 2008R2 and SQL Server 2008R2, did you upgrade these to 2012 versions before upgrading?
Thanks.
Curt Weaver
To be perfectly honest, I never got as far as completing the upgrade of production, but I did complete the data upgrade of TEST, and we decided to use that copy of the database. We weren't live, so it was a viable option.
I have an ongoing support request regarding the upgrade process, so I don't know how much I can disclose regarding this, but as far as I can tell, at the point of writing, the data upgrade for PROD is not working as intended. It is independent of version of OS or SQL Server version.
Sorry.
Thanks. Upgrading of just test would be an improvement at this point.
I'm getting ready to enter my own support ticket on this as well. I have customers that will need/want to upgrade to R2 and I can't come up with a resonable set of instruction to get them from RTM to R2.
Curt W.
If you follow the in-place upgrade guide carefully, and apply various Ax Jedi skills, you should be able to pull through in data upgrading test. I got through on the second attempt, but there are a few bumps on the road, and there are little to few warnings about them on MSDN.
When I know the upgrade works (even half baked), I want to blog about this. Right now, it is too early.