SDL MultiTerm Convert caught in loop during conversion that may lead to System out of Memory Error
SDL MultiTerm Convert
During the Converting (10/11) phase SDL MultiTerm Convert is stuck in a loop and eventually it will lead to a System out of Memory exception if left running.
This issue can be caused by the occurrence of ampersands, even escaped ampersands, in some fields.
The SDL Development team is aware of this problem and is working on a solution. Until a permanent solution is in place, please apply the Workaround described in the Resolution section.
Remove all ampersands from the source XML and re-add them once the conversion is done.
Open the source XML in a text editor of your choice (i.e Notepad, Wordpad, Notepad++, etc.) and use Find and Replace (usually reachable with [Ctrl]+[H]) to replace all occurrences of & with AMPERSAND
Run the conversion as usual
Open the target XML and use Find and Replace to replace AMPERSAND with &
If you have a valid Support and Maintenance contract: log into your SDL Customer Gateway and log a support request.
If you do not have a Support and Maintenance contract but a Licensing or Installation issue: log your request also via the SDL Customer Gateway Portal and select the Licensing and/or Installation option in the form.
Technical issue but no PSMA?
If you do not have a Support and Maintenance contract BUT encounter a technical issue, create a post via the SDL Community. In the SDL Community users help users and can answer/comment no problems you encounter.