You may encounter this error when launching the Live Preprocessing or the Delta processing scripts, for the AX2012 Upgrade checklist in AX2009, even though you have successfully completed the Upgrade Readiness scripts.
Error:
We have encountered this error in the following scenario:
- Ran the Upgrade Readiness scripts. All scripts completed fine.
- Ran the Live Preprocessing scripts. All scripts completed fine.
- Opened the Upgrade Readiness scripts form to review the results; and closed the cockpit form without running the scripts again.
- Tried to launch the Delta Processing scripts > encountered the error.
Cause:
When the Upgrade Cockpit is opened, it loads all the scripts, for the current stage, into the ReleaseUpdateScripts table. When the form is closed, it checks whether all the scripts have completed. If they have, the logic deletes the records from the ReleaseUpdateScripts table. The records in ReleaseUpdateScripts do not get deleted if the scripts, for the current run, have not completed.
The reason for the error was that when we closed the Readiness cockpit, the records in the ReleaseUpdateScripts table did not get deleted.
Solution:
Delete all the records from the ReleaseUpdateScripts table.
hi all,
i am migrating from ax2009 to ax2012r2cu7 .while running the delta preprocessing checklist the batch job is still in executing for the first step more than two days ,can anyone tell me how long it will takes.
Naveen, two days seems excessive. I suggest restarting the checklist job.
thanks for the reply.I TRIED TO RESTART the checklist but the probelm still same.the problem is in collect patching delta method this is the method running for several days can anyone tell me wat is the issue.
Hello Naveen,
i have exactly the same problem in the Run Delta preprocessing scripts, with the first task “collect Patching Delta”.
the task never finsih, and the status is still in execution.
I follow all the check list, without any problems…
Do you find finally the solution?
thanks so much.
Naveen, you may need to look into the script’s class/method and try to determine what it is doing (which tables it populates etc.). This may give you an insight into the issue.