Program terminated with dump SYNTAX_ERROR

[former_member479273]

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.

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

[Former Member]

Great Work!!!

[Former Member]

This helped me a lot. Thank you Rene.

[former_member302557]

Hi,

I tried these steps of doing through the tp.exe command, but its halfway through. After imported with warnings and restarting hte instances, some tcodes are working now, like SU01/SM51 etc, but SPAM/SAINT are giving the same error.

I tried the activation through tcode SE18, but when I click on activate the programs throw the same error.

Any idea?

Srinivasan K

[stefanbussman]

I wonder why there is no solution at SAP-OSS

Good Job Renè

Greetings

steve

[Former Member]

Had the same error symptoms while upgrading to SolMan 7.0 EHP1 SP5 and discovered that both SAPK-701D0INSAPBASIS AND SAPK-701DRINSAPBASIS had import errors. The instructions provided on the previous page were exactly what I needed to solve the program. Be sure to clear the TRBAT table prior to performing the individual import.

Thanks very much for posting this valuable solution!

[RobertH]

Hello Rene.

Many thanks. I have had exactly the same problem when installing EhP1 for SolMan. With your manual I was able to solve the issue.

Regards

Robert

[Former Member]

I had the same problem upgrading SAP Solution Manager to EHP1 - after successfully reimporting the component with error as stated I was able to log in, and SAINT asked me to restart the system, and afterwards everything worked as expected. Thank you, Rene !

ZP.

[Former Member]

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

[Former Member]

Hi Reene ,

we have followed your procedure but this line i.e.

hostname:sidadm 73> tp r3i SAPK-701DRINSAPBASIS SID pf=/usr/sap/trans/bin/TP_DOMAIN_T1D.PFL tag=spam - i am getting a syntax error. our patch is SAPKB70010. Please tell us as how to overcome this syntax error.

Thanks And Regards

amit

[former_member388385]

Hi Rene,

Thanks for your details steps..I have resolved the same issue which I had during applying Solution Manager 7.0 EHP1.

Amit: may be you can replace with SID with your own SID and profile name with your tp profile.

Best Regards,

Nilkanth.

Edited by: Nilkanth Patil on Dec 26, 2008 6:03 PM

[Former Member]

Rene,

Thanks for your valuable solution....

[greg_drozd]

Hi Rene.

Thanks for the solution.

Cheers.

Greg

SM 7 / AIX 5.3 / ORACLE

[Former Member]

This worked like a charm....amazing!

[Former Member]

Thanks Rene, it solved my issue

[Former Member]

Hello Rene,

I faced the same severe issue upgradung our SolMan System from 7.00 - ST 17 to 7.0T EHP1 ST 20; your solution helped me too

to overcome the problems!!! )

see "my" tp buffer before and after:

SAPK-701DRINSAPBASIS| | |0016 |0004 |0004 |0016 | | | | | | | |D

SAPK-701DRINSAPABA | | |0000 |0004 |*0004 |1 | | | | | | | |D

Thanks too for the solution.

Cheers. Thomas

SM 7.01 / hpux IA 11.23 / ORACLE 10.2.0.4.0

P.S. I wonder why there is no solution at SAP-OSS?

[Former Member]

Thank You Very Much for the Advice of how to deal with this problem, 😃

[alejandro_navajas3]

Excellent post!!

I was able to resolve this issue after I ran out of space on the hard drive.

The log showed me the following:

SLOG1023.SLM

ERROR: stopping on error 12 during MAIN IMPORT

WARNING:
solmansap01\sapmnt\trans\tmp\Q100612.SLM : cant open

WARNING:
solmansap01\sapmnt\trans\tmp\Q100611.SLM : cant open

WARNING: : cant open

WARNING: : cant open

WARNING:
solmansap01\sapmnt\trans\tmp\Q100612.SLM : cant open

WARNING:
solmansap01\sapmnt\trans\tmp\Q100611.SLM : cant open

WARNING: : cant open

WARNING: : cant open

Then, I followed the steps described here and the short dump was resolved. Then I continued with the upgrade through SAINT.

Regards,

Alejandro

[former_member479273]

Thanks for all, who suggested me.

[debasissahoo]

Hi Jayakar,

The error shows, syntax error was found in the program SAPLSUNI:

"The type "CX_ENH_SPOT_IS_INTERNAL" is unknown."

You can also do a syntax check in SE38 for the program SAPLSUNI, it will show the same error. You can take help of an ABAPer to see what can be done here. You should also create support message to SAP if you are not able to get any standard notes/ known error list.

Regards,

Debasis.

[former_member479273]

Dear

I am not able to login into system, It is giving dump after giving user id & pwd.

This happed in My Solution Manager System, when applying basis 13 patch.

As per Note 1112065, I tried to FIX the problem. But when I run the TP command, getting error ERROR: Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.

Where I am not able to login into the system to run RDDNEWPP report.

please help me.

Regards

Jayakar

[debasissahoo]

Hi,

For your information, RDDNEWPP is run in the clients (to which transports/supportpackages are imported) with DDIC user ID.

I hope you're aware of this.

Regards,

Debasis.

[former_member479273]

dear all,

I raised OSS Message, resolved this issue by restoring the last backup as per SAP.

Regards

Jayakar

[Former Member]

Hi,

As per your error you can consult with abaper. The abaper can see that programe what is the error in this programe.

Anil