Microsoft Dynamics AX Support

This blog contains posts by the Microsoft Dynamics AX Support teams Worldwide

AX 2012 R2 In-Place Upgrade – Sometimes during the Data Upgrade Checklist the Detect Update Scripts step does not prepare any scripts to run.

AX 2012 R2 In-Place Upgrade – Sometimes during the Data Upgrade Checklist the Detect Update Scripts step does not prepare any scripts to run.

Rate This
  • Comments 2

The “Detect update scripts (Required)” is the first part of the Data upgrade section in the checklist.

image

If you get the following warning “Data Upgrade mode had already been initialized. If additional updates have been installed complete the data upgrade process for the previously installed updated before restarting the process for any additional updated” the when you for the first time click on the “Detect update scripts (Required)” step in the Data Upgrade Checklist, you will have problems as the required data upgrade scripts are not prepared.

clip_image001

Typically you will not see the “Presynchronize (required)” task, as shown below:

clip_image002

Please note that this is only an issue, if this is the first time you run this step; the warning message is a normal message for when you have already completed the data upgrade.

This problem has been seen a couple of times, and it was due to some historical data remaining in the ReleaseUpdate* tables from a restarted or incomplete AX 4.0/2009 to AX 2012 RTM upgrade. For some reason, even though some upgrades had appeared to be successfully updated to AX 2012, there was some old data remaining.

If you have this problem you can check for old data in SQL, by using the following scripts:

SELECT COUNT(*) FROM RELEASEUPDATEBULKCOPYFIELD_GLS;

SELECT COUNT(*) FROM RELEASEUPDATEBULKCOPYFIELDERRORS;

SELECT COUNT(*) FROM RELEASEUPDATEDISCOVERYSTATUS;

SELECT COUNT(*) FROM RELEASEUPDATEJOBSTATUS;

SELECT COUNT(*) FROM RELEASEUPDATEMINORSCRIPTS;

SELECT COUNT(*) FROM RELEASEUPDATESCRIPTDEPENDENCY;

SELECT COUNT(*) FROM RELEASEUPDATESCRIPTS;

SELECT COUNT(*) FROM RELEASEUPDATESCRIPTSUSEDTABLES;

If you find that there is old AX 2012 RTM upgrade records in the tables above from a previous upgrade, you can delete the records with the following steps:

1) Close the AX 2012 R2 Client

2) Stop the AOS Server

3) As with best practice, make a backup of the database as you are going to delete data.

4) Run the following SQL Script:

TRUNCATE TABLE RELEASEUPDATEBULKCOPYFIELD_GLS;

TRUNCATE TABLE RELEASEUPDATEBULKCOPYFIELDERRORS;

TRUNCATE TABLE RELEASEUPDATEDISCOVERYSTATUS;

TRUNCATE TABLE RELEASEUPDATEJOBSTATUS;

TRUNCATE TABLE RELEASEUPDATEMINORSCRIPTS;

TRUNCATE TABLE RELEASEUPDATESCRIPTDEPENDENCY;

TRUNCATE TABLE RELEASEUPDATESCRIPTS;

TRUNCATE TABLE RELEASEUPDATESCRIPTSUSEDTABLES;

5) Start the AOS and Client

6) Rerun the step “Detect update scripts (Required)” from the Data Upgrade checklist.

 

Disclaimer: Please ensure you have full backups of databases and files before making any changes as detailed in the steps above.

Leave a Comment
  • Please add 2 and 3 and type the answer here:
  • Post
  • Is there a particular reason the lines for "RELEASEUPDATEBULKCOPYFIELD_GLS" have "_GLS" as our DB does not have this appended to the table name.

  • Hi Dillon - you may not have this table, it was in the test system I originally found this issue in. So in that case, you need to just truncate the RELEASEUPDATEBULKCOPYFIELD table. As with any operation like this, please make sure you have full database backups before.

    Thanks, Thomas

Page 1 of 1 (2 items)