Insufficient memory allocation causes Microsoft Dynamics AX upgrade to fail during ‘Detect code upgrade conflicts’ checklist
During the process of running the code upgrade conflict detection in the SP1 upgrade checklist, the Microsoft Dynamics AX client can stop working when one or more layers are very large and there is not enough system memory to support the process.
To work around this issue, ensure that at least 3GB of memory are available to the Microsoft Dynamics AX upgrade process.
Important
We recommend restoring the 2GB user-mode process threshold after the upgrade has completed.
For information about ensuring that 3GB of memory are available to the upgrade process, and about restoring the default 2GB threshold for user mode-processes, see
Use of the /3GB switch in Exchange Server 2003 on a Windows Server 2003-based system.