Skip to Content
0

spro_admin dump

Jun 05, 2017 at 08:29 AM

48

avatar image

dear expert,

When i executed the t-code spro_admin , the system generated a dump error.

Exception condition "COMP_NOT_FOUND" raised.

Error analysis
A RAISE statement in the program "SAPLSUGU" raised the exception
condition "COMP_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.

Short description of exception condition:

Unable to find software component

For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
-

How to correct the error

If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:

"RAISE_EXCEPTION" " "
"SAPLSUGU" or "LSUGUU09"
"DELIVERY_GET_COMPONENT_RELEASE"

or

"SAPLSUGU" "COMP_NOT_FOUND"

or

"SAPLS_IMG_TOOL_5 " "COMP_NOT_FOUND"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File
(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File

Information on where terminated
Termination occurred in the ABAP program "SAPLSUGU" - in
"DELIVERY_GET_COMPONENT_RELEASE".
The main program was "SAPLS_IMG_TOOL_5 ".

In the source code you have the termination point in line 21
of the (Include) program "LSUGUU09".

i could not find the answer from sap knowledge. Please help me.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Jürgen L
Jun 05, 2017 at 08:38 AM
0

Could you eventually explain what happened in the hours before that dump?

Did you install a new system, did you upgrade?

Does the dump occur right after SPRO transaction execution or when you click a certain task within the IMG?

Had you already tried something that is explained in the lines that you copied to here? What was the result?

Share
10 |10000 characters needed characters left characters exceeded
ling long Jun 06, 2017 at 03:00 AM
0

The system was refreshed before and spro transaction was ok . When executed the spro_admin the dump occurred.

Share
10 |10000 characters needed characters left characters exceeded