on 09-23-2014 7:04 AM
Hi All,
Am getting this dump in my system after system refresh
Runtime Error IMPORT_FORMAT_ERROR
Error in ABAP application program.
The current ABAP program "SAPLSTUW" had to be terminated beca
statements could not be executed.
This is probably due to an error in the ABAP program.
Error analysis
When attempting to IMPORT the object "PROTOCOL", there was a format error.
Unable to read an IMPORT dataset.
The dataset may have been processed using SQL and is
thus no longer readable for the IMPORT.
One standard Program
SAP_COLLECTOR_FOR_PERFMONITOR / 23524501 failed
job log:
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC
ABAP/4 processor: IMPORT_FORMAT_ERROR
Job cancelled
Thanks
Hi Srikanth,
Con you upload the full dump once and make sure you zip+upload ?
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Reddy
Could you paste /attach the full dump
BR
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Runtime Error IMPORT_FORMAT_ERROR
Occurred on 09/22/2014 at 00:00:46
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSTUW" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
When attempting to IMPORT the object "PROTOCOL", there was a format error.
Unable to read an IMPORT dataset.
The dataset may have been processed using SQL and is
thus no longer readable for the IMPORT.
How to correct the error
Determine which actions resulted in the destruction of the
dataset.
System environment
SAP Release.............. "620"
Application server....... "a9126us12"
Network address.......... "9.126.9.12"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 80686"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 11
Short dump setting....... "full"
Database server.......... "A9126US12"
Database type............ "ORACLE"
Database name............ "QAS"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Jul 3 2011 22:04:05"
Created in............... "NT 5.2 3790 Service Pack 2 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "381"
Patch text............... " "
Supported environment....
User, transaction...
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSTUW"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSTUW" in
"SAPWL_STATCOL_GET_PROTOCOL".
The main program was "RSSTAT83 ".
The termination occurred in line 36 of the source code of the (Include)
program "LSTUWU35"
of the source code of program "LSTUWU35" (when calling the editor 360).
The program "SAPLSTUW" was started as a background job.
Hi Reddy
Could you check this SAP Note I thing you have to check the service tools
69455 - Servicetools for Applications ST-A/PI (ST14, RTCCTOOL, ST12)
BR
SS
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
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.