Program terminated with dump SYNTAX_ERROR

Question

Hi
When updating Solution Manager patches, program terminated and went on to dump.
Now I am not able to login into system with GUI to do any other thing.
It also showing "Status LIVE of the User interface SAPLSRABAX_EXC missing". With this message I got the following link.
SYNTAX_ERROR when executing any transaction
But, I am not able to login into the system now.
I need to do at OS level something to overcome this problem.
Can any one faced same problem.... Plz help me.
Dump:
Runtime Errors         SYNTAX_ERROR
Date and Time          14.10.2008 19:11:44
Short text
     Syntax error in program "SAPLSUNI ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPMSPAM" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "SAPLSUNI " in include
      "CL_ABSTRACT_ENH_TOOL==========CU " in
     line 24:
     "The type "CX_ENH_SPOT_IS_INTERNAL" is unknown."
     The include has been created and last changed by:
     Created by: "SAP "
     Last changed by: "SAP "
     Error in the ABAP Application Program
     The current ABAP program "SAPMSPAM" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     The following syntax error was found in the program SAPLSUNI :
     "The type "CX_ENH_SPOT_IS_INTERNAL" is unknown."
Regards
Jayakar

Answer 1

Hi @all, Iu2019ve had the same error but I fixed it without restore as follows:
Error Messages:
before you login to SAP you can see in sap logon:
Status 0020 of the user interface SAPMSYST missing
after login in status bar:
Status LIVE of the user interface SAPLSRABAX_EXC missing
In SLOG1234.SID:
WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.
      Please check that the R/3 system is running.
      Please check the system. Use transactions SM21, SM37, SM50.
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System SID. Warning.        20081211092715 :
Please find and solve the problem, which was the cause for it. In my case it was an ORA dead lock.
You can find the transport (support package or add on installation transport file) with errors in support package queue as follows:
hostname:sidadm 63> tp showbuffer SID tag=spam pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL
Or you can find return codes with grep; for example:
hostname:sidadm 54> tp showbuffer SID tag=spam pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL | grep 0012
SIDK001215          .100|SID_P00003          | |will not be imported because it is not tagged.
SAPK-701DRINSAPBASIS.ALL|                    | |0012 |0004 |0004 |0012 |      |      |      |      |      |      |     |D
Kill all tp prozesses and clean tables TRBAT and TRJOB in DB:
hostname:sidadm 63> ps -ef | grep tp
ntp       4124     1  0 Jul12 ?        00:00:01 /usr/sbin/ntpd -p /var/lib/ntp/var/run/ntp/ntpd.pid -u ntp -i /var/lib/ntp
sidadm    6216 28099  0 Dec10 ?        00:00:05 /usr/sap/SID/DVEBMGS01/exe/tp hostname.domain.de hostname 55855300 IDX=1
hostname:sidadm 64> kill 6216
Import in command line the abordet transport in r3i mode:
hostname:sidadm 73> tp r3i SAPK-701DRINSAPBASIS SID pf=/usr/sap/trans/bin/TP_DOMAIN_T1D.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8
After finished import with RC = 0 or 4 you can normally login correctly to SAP system and restart the import in SPAM or SAINT again in last stopped phase.
Edited by: Rene Schulz on Dec 12, 2008 2:27 PM