AX4 to AX2012 R2 Upgrade Check Upgrade Readiness function error

AX4 to AX2012 R2 Upgrade Check Upgrade Readiness function error

This question is not answered
Hi, When I try to run the CHECK UPGRADE READINESS function in the Pre-processing checklist for upgrading AX4 to AX 2012 R2 - I get the following error: Error: Error executing code: Wrong argument types in variable assignment. Stack trace (S)\Classes\ReleaseUpdateDB\parmScriptStage - line 4 (S)\Classes\ReleaseUpdateDB\constructList - line 20 (S)\Classes\ReleaseUpdateCockpit\loadJobs - line 36 (S)\Classes\ReleaseUpdateCockpit\init - line 18 (C)\Forms\ReleaseUpdateCockpit\Methods\init (C)\Classes\SysSetupFormRun\init - line 3 (C)\Classes\ReleaseUpdateCockpitLoader\main - line 84 (C)\Classes\MenuFunction\run (C)\Classes\SysHelp\processMenuFunction - line 69 (C)\Classes\SysHelp\processStandardLink - line 18 (C)\Classes\SysHelp\processOnEventNavigate - line 43 (C)\Classes\SysHelp\onEvent_BeforeNavigate2 - line 27 (C)\Classes\FormActiveXControl\onEvent_BeforeNavigate2 Has anyone came across this before - it would indicate that an enum value _ScriptStage is not being passed into the code correctly, or is not of the correct data type. Any help here would be appreciated
All Replies
  • I am not sure about AX4, but in AX2009 ReleaseUpdateDB is in the sys layer.  I had a similar error during my AX2009 to AX2012 upgrade because there were modifications to the releaseUpdateDB classes leftover from the AX3 to AX2009 upgrade.  I removed the mods and reimported the XPO.

  • Hi,

    Yeah you are correct, ReleaseUpdateDB does exist in version 4 in the Sys layer.  As instructed, I import the AX4 upgrade XPO from the 2012 R2 CD and then compile the AOT afterwards.

    I have debugged the code and I cannot see the exact error - this is causing me major issues - can anyone else shed some light on this towards a solution?

  • Update: If I manually assign the enum value inside the parmScriptStage method - I can access the form options - the values are not being passed correctly into the parmScriptStage method, I appear to be able to work around this, however it must be Microsoft issue, I am amazed there are not more AX4 users that have experienced this in their upgrade attempt.

  • You don't mention if you are slipstreaming an update along with AX2012 R2.  There is an upgradeax4.xpo file dated 10/31/2013 in the CU7 DatabaseUpgrade directory, so perhaps the problem was fixed with an update.