on 11-06-2009 10:47 AM
There was error in SM21 while running a program as
Termination occurred in the ABAP program "SAPLRSPC_BACKEND" - in
"RSPC_PROCESS_FINISH" .
What can be the soluiton for it?
Hi everyone,
Note was created for solve this type of errors and dumps:
2248991 - SAPLRSPC_BACKEND short dump when trying to load data through infopackage
Regards,
Janaina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Runtime Errors MESSAGE_TYPE_X
Date and Time 06.11.2009 10:08:43
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Job or process LOADING, waiting for event RSPROCESS 3X0NQO9ZQ8B1Y6JGO2EN
EBD3U is unknown
Long text of error message:
Diagnosis
Job LOADING has been started because of event RSPROCESS
3X0NQO9ZQ8B1Y6JGO2ENEBD3U. This job is not, however, known in the
active version of the process chain.
System Response
The job has been terminated.
Procedure
Procedure for System Administration
Technical information about the message:
Message class....... "RSPC"
Number.............. 002
Variable 1.......... "LOADING"
Variable 2.......... "RSPROCESS"
Variable 3.......... "3X0NQO9ZQ8B1Y6JGO2ENEBD3U"
Variable 4.......... " "
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ambarish
I guess your system is a BI system.
RSPC_PROCESS_FINISH report is used to make one process "successful or failure" forcefully. Probably after doing something manually in a process chain your BI team ran that report to make it successful or whatever , so that next process in the chain starts.
I do not think you need to be worried about this dump if you are not getting this on regular basis. I would suggest you to talk to your BI team and ask them if they ran any thing like that.
To perform this activity they need to provide six parameters
LOGID
CHAIN
TYPE
VARIANT
INSTANCE
STATE
They might have made some mistake there and that's why you got a dump. Please clarify with your BI team
Too less information - please post the first pages of the dump.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.