SAP Knowledge Base Article - Preview

2250487 - SUM: Internal Error in SAPup memory


With SUM SP14 and onwards the new common SL UI is the default UI so when you run SUM ( URL : http://<hostname>:1128/lmsl/sumabap/<SID>/doc/sluigui or https://<hostname>:1129/lmsl/sumabap/<SID>/doc/sluigui), two SAPup executables are called , one with the gt=httpchannel parameter that manages the requests from SAP Host Agent and another with guiconnect parameter that calls tools like tp, R3trans or R3load, as shown in this picture.


It is not recommended to call any additional SAPup manually  without stopping previous one (specially the one started with guiconnect parameter) as this could disturb SAPup memory files and therefore mess the upgrade procedure, being impossible to run SUM tool again.

If you are not using  the new common SL UI, the SAPup call made by SUM is different but the recommendation not to call an additional SAPup manually without stopping the previous one is the same.

If you do not follow this recommendation errors similar to the following ones could appear:

  •  ERROR in MEM file: Corrupted line
  • <Memory file> corruption file line <xxx>
  • <Memory file>: Internal error [Read, update, got internally insert]


Starting with SUM SP14 there are some options that can be called from the browser that generates other SAup calls, these are not manually SApup calls.




MEMProcSAPup.dat Internal error MEMSAPup.dat best practice , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.