Archiving Transaction SARA throws dumps.

Question

S0003731475
Hi Gurus
I am trying to run archiving transaction SARA but it throws dumps and I canu2019t seem to find the reasonu2026u2026
Here is the dumpu2026u2026..Anyone who faced similar problemu2026u2026.Please help.
Runtime errors         SYNTAX_ERROR
       Occurred on     12/08/2009 at   13:45:09
Syntax error in program "SAPLARCH ".
What happened?
The following syntax error occurred in the program SAPLARCH :
"Method "GET_DATA" is unknown or PROTECTED or PRIVATE."
Error in ABAP application program.
The current ABAP program "SAPMAADM" 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?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLARCH ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
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
The following syntax error was found in the program SAPLARCH :
"Method "GET_DATA" is unknown or PROTECTED or PRIVATE."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "M3SAPA01"
Network address.......... "136.133.230.177"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "M3SAPA01"
Database type............ "MSSQL"
Database name............ "RDS"
Database owner........... "rds"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Mar 10 2009 01:13:21"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "274"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 220
User................ "RHEMNANI"
Language key........ "E"
Transaction......... "SARA "
Program............. "SAPMAADM"
Screen.............. "SAPMAADM 0001"
Screen line......... 2
Information on where terminated
The termination occurred in the ABAP program "SAPMAADM" in "D0001_DISPLAY".
The main program was "SAPMAADM ".
The termination occurred in line 278 of the source code of the (Include)
program "MAADMO01"
of the source code of program "MAADMO01" (when calling the editor 2780).
Source code extract
002480   * check if parameters exists
002490     progname = arch_obj-retrie_prg.
002500     answer = 'YES'.
002510     CALL FUNCTION 'RS_SELSCREEN_EXISTS'
002520       EXPORTING
002530         report            = progname
002540       IMPORTING
002550         answer            = answer
002560       EXCEPTIONS
002570         no_report         = 01
002580         program_incorrect = 02
002590         program_not_found = 03.
002600     IF sy-subrc EQ 0.
002610       IF answer EQ 'NO'.
002620         LOOP AT SCREEN.
002630           CHECK screen-group1 = 'VAR'.
002640           screen-active = 0.
002650           MODIFY SCREEN.
002660         ENDLOOP.
002670       ENDIF.
002680     ENDIF.
002690   ENDMODULE.                             " D0300_DISPLAY  OUTPUT
002700
002710   *&---------------------------------------------------------------------*
002720   *&      Module  D0001_DISPLAY  OUTPUT
002730   *&---------------------------------------------------------------------*
002740   *       text                                                           *
002750   *----------------------------------------------------------------------*
002760   MODULE d0001_display OUTPUT.
002770     SUPPRESS DIALOG.
----->     CALL FUNCTION 'ARCHIVE_DISABLE_MONITORING'.
002790   ENDMODULE.                             " D0001_DISPLAY  OUTPUT
002800   *&---------------------------------------------------------------------*
002810   *&      Module  INIT_0120  OUTPUT
002820   *&---------------------------------------------------------------------*
002830   *       text
002840   *----------------------------------------------------------------------*
002850   MODULE d0120_display OUTPUT.
002860     DATA: format1(12) TYPE c.
002870     DATA: format2 TYPE i.
002880     LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
002890     SET PF-STATUS 'SPACE'.
002900     SET TITLEBAR '105'.
002910     WRITE: / 'Archivverzeichnis:'(060), file_path.
002920     ULINE.
002930     MOVE freespace TO format2.           "to format with points
002940     WRITE format2 TO format1.
002950     WRITE: / 'Verfügbarer Freiplatz:'(061),format1 NO-ZERO,'KB'.
002960     LEAVE SCREEN.
002970
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 0
SY-TABIX 0                             SY-DBCNT 0
SY-FDPOS 0                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1                             SY-PFKEY
SY-UCOMM                               SY-TITLE Archive Management Module Pool
SY-MSGTY                               SY-MSGID
SY-MSGNO 000                           SY-MSGV1
SY-MSGV2                               SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
       Program
       Include                                  Line
       Class
     2 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
     1 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
Chosen variables
     2 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
%_DUMMY$$
                               2222
                               0000
                               0000
                               0000
     1 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
No dump information available
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "ab_genprog" of the SAP
Basis System, specifically in line 1423 of the module
"//bas/640_REL/src/krn/runt/abgen.c#14".
The internal operation just processed is "FUNC".
The internal session was started at 20091208134509.
Program name.........: "SAPLARCH ".
Error message........: "Method "GET_DATA" is unknown or PROTECTED or PRIVATE.".

Answer 1

Rajesh,
This might happen if the orginal function module ARCHIVE_GET_INFORMATION in LARCHF03 program is altered, bring back the the function module to original, it might solve your problem.
Anand B Vodnala