Error in program RSAL_BATCH_TOOL_DISPATCHING (job SAP_CCMS_MONI_BATCH_DP)

Hi All,
After successfull upgrade in Support pack level 17, I am getting an error message in with a standard job SAP_CCMS_MONI_BATCH_DP. I am getting the following error messages in SM21.
Database error -440 at OPC
> SQL0440N No authorized routine named "DB6PMCF" of type
> "FUNCTION" having compatible arguments was found.
> SQLSTATE=42884
Database error -440
Database error -440 at OPC
> SQL0440N No authorized routine named "DB6PMCF" of type
> "FUNCTION" having compatible arguments was found.
> SQLSTATE=42884
Database error -440
Database error -440 at OPC
> SQL0440N No authorized routine named "DB6PMCF" of type
> "FUNCTION" having compatible arguments was found.
> SQLSTATE=42884
Database error -440
Database error -440 at OPC
> SQL0440N No authorized routine named "DB6PMCF" of type
> "FUNCTION" having compatible arguments was found.
> SQLSTATE=42884
Even after checking the error in details I found the program "RSAL_BATCH_TOOL_DISPATCHING" causing the error message. In details the error message says :
Job started
Step 001 started (program RSAL_BATCH_TOOL_DISPATCHING, variant , user ID
:Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
:  Kernel Error ID:
:  SYSID: <SID>
:  SY-SUBRC: 1208
:  Message: ADBC error
:  SQL statement: SELECT '20091109062730',0 as DB6PMCF_PARTITION,' ','T
:  ','20091106055752','700',0.0,0.0,0.0,0.0,0 FROMSYSIBM.SYSDUMMY1, TABL
:  E(SAPTOOLS.DB6PMCF('/db2/SID/log_dir/') ) AS FS_CONFIG
:  Database:
:caused by
:Exception CX_SQL_EXCEPTION in class CL_SQL_STATEMENT
:  Kernel Error ID:
:  DB Error: Yes
:  SQL Code: 440-
:  SQL Message: SQL0440N No authorized routine named "DB6PMCF" of typ
:  e "FUNCTION" having compatible arguments was found. SQLSTATE=42884
:  DB Object Exists: No
:  Duplicated Key: No
:  Internal Error: 1
:  Invalid Cursor: No
:  Unknown Connection: No
:  Connection Closed: No
Did anybody encountered with any situstion like this...Would appreciate any early response.
DID CHECK WITH KERNEL FILES, LOOKS GOOD FOR ME. ALSO CHECKED WITH note 978319 ..
Thanks in Advance

I have not yet tried to apply the note 978319.
Current DB LEVEL is as follows..
DB client lib.     DB6_81
DB releases        DB6 08.02.*, DB6 0
DBSL version       700.08
DBSL Patch Level   171

Similar Messages

  • Error in CCMS monitoring Batch job SAP_CCMS_MONI_BATCH_DP.

    Hi All,
    I am using a Sanbox system for CCMS Monitoring activities. I assigned a method CCMS_ONAlert_Email under auto reaction to the MTE class ABAP shortdumps on node System errors. So the requirement is when an alert triggered i have to receive an alert email. I just found there is an error in Batch job created for Alert monitoring, please find the error details mentioned below. Please let me know how to solve this error
    Job started
    Step 001 started (program RSAL_BATCH_TOOL_DISPATCHING, variant , user ID NBKIPXP)
    :Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :  Kernel Error ID:
    :  SYSID: ES1
    :  SY-SUBRC: 1208
    :  Message: ADBC error
    :  SQL statement: SELECT '20110613075617',0 as DB6PMCF_PARTITION,FS_NAM
    :  E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
    :  SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/sapdata1')
    :  ) AS FS_CONFIG
    :  Database:
    :caused by
    :Exception CX_SQL_EXCEPTIONin class CL_SQL_RESULT_SET
    :  Kernel Error ID:
    :  DB Error: Yes
    :  SQL Code: 444-
    :  SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
    :  B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
    :  /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
    :  on code: "4". SQLSTATE=42724
    :  DB Object Exists: No
    :  Duplicated Key: No
    :  Internal Error: 1
    :  Invalid Cursor: No
    :  Unknown Connection: No
    :  Connection Closed: No
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :  Kernel Error ID:
    :  SYSID: ES1
    :  SY-SUBRC: 1208
    :  Message: ADBC error
    :  SQL statement: SELECT '20110613075633',0 as DB6PMCF_PARTITION,FS_NAM
    :  E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
    :  SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/log_dir/NO
    :  DE0000/') ) AS FS_CONFIG
    :  Database:
    :caused by
    :Exception CX_SQL_EXCEPTION in class CL_SQL_RESULT_SET
    :  Kernel Error ID:
    :  DB Error: Yes
    :  SQL Code: 444-
    :  SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
    :  B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
    :  /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
    :  on code: "4". SQLSTATE=42724
    :  DB Object Exists: No
    :  Duplicated Key: No
    :  Internal Error: 1
    :  Invalid Cursor: No
    :  Unknown Connection: No
    :  Connection Closed: No
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :  Kernel Error ID:
    :  SYSID: ES1
    :  SY-SUBRC: 1208
    :  Message: ADBC error
    :  SQL statement: SELECT '20110613075633',0 as DB6PMCF_PARTITION,FS_NAM
    :  E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
    :  SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/sapdata4/d
    :  b2es1/NODE0000/ES1/T0000003/C0000000.TMP') ) ASFS_CONFIG
    :  Database:
    :caused by
    :Exception CX_SQL_EXCEPTION in class CL_SQL_RESULT_SET
    :  Kernel Error ID:
    :  DB Error: Yes
    :  SQL Code: 444-
    :  SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
    :  B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
    :  /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
    :  on code: "4". SQLSTATE=42724
    :  DB Object Exists: No
    :  Duplicated Key: No
    :  Internal Error: 1
    :  Invalid Cursor: No
    :  Unknown Connection: No
    :  Connection Closed: No
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :  Kernel Error ID:
    :  SYSID: ES1
    :  SY-SUBRC: 1208
    :  Message: ADBC error
    :  SQL statement: SELECT '20110613075634',0 as DB6PMCF_PARTITION,FS_NAM
    :  E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
    :  SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/sapdata2/d
    :  b2es1/NODE0000/ES1/T0000003/C0000001.TMP') ) ASFS_CONFIG
    :  Database:
    :caused by
    :Exception CX_SQL_EXCEPTION in class CL_SQL_RESULT_SET
    :  Kernel Error ID:
    :  DB Error: Yes
    :  SQL Code: 444-
    :  SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
    :  B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
    :  /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
    :  on code: "4". SQLSTATE=42724
    :  DB Object Exists: No
    :  Duplicated Key: No
    :  Internal Error: 1
    :  Invalid Cursor: No
    :  Unknown Connection: No
    :  Connection Closed: No
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :  Kernel Error ID:
    :  SYSID: ES1
    :  SY-SUBRC: 1208
    :  Message: ADBC error
    :  SQL statement: SELECT '20110613075634',0 as DB6PMCF_PARTITION,FS_NAM
    :  E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
    :  SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/sapdata1/d
    :  b2es1/NODE0000/ES1/T0000003/C0000002.TMP') ) ASFS_CONFIG
    :  Database:
    :caused by
    :Exception CX_SQL_EXCEPTION in class CL_SQL_RESULT_SET
    :  Kernel Error ID:
    :  DB Error: Yes
    :  SQL Code: 444-
    :  SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
    :  B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
    :  /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
    :  on code: "4". SQLSTATE=42724
    :  DB Object Exists: No
    :  Duplicated Key: No
    :  Internal Error: 1
    :  Invalid Cursor: No
    :  Unknown Connection: No
    :  Connection Closed: No
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :  Kernel Error ID:
    :  SYSID: ES1
    :  SY-SUBRC: 1208
    :  Message: ADBC error
    :  SQL statement: SELECT '20110613075634',0 as DB6PMCF_PARTITION,FS_NAM
    :  E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
    :  SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/sapdata3/d
    :  b2es1/NODE0000/ES1/T0000003/C0000003.TMP') ) ASFS_CONFIG
    :  Database:
    :caused by
    :Exception CX_SQL_EXCEPTION in class CL_SQL_RESULT_SET
    :  Kernel Error ID:
    :  DB Error: Yes
    :  SQL Code: 444-
    :  SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
    :  B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
    :  /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
    :  on code: "4". SQLSTATE=42724
    :  DB Object Exists: No
    :  Duplicated Key: No
    :  Internal Error: 1
    :  Invalid Cursor: No
    :  Unknown Connection: No
    :  Connection Closed: No
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :  Kernel Error ID:
    :  SYSID: ES1
    :  SY-SUBRC: 1208
    :  Message: ADBC error
    :  SQL statement: SELECT '20110613075634',0 as DB6PMCF_PARTITION,FS_NAM
    :  E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
    :  SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/sapdata3/d
    :  b2es1/NODE0000/ES1/T0000004/C0000003.UTM') ) ASFS_CONFIG
    :  Database:
    :caused by
    :Exception CX_SQL_EXCEPTION in class CL_SQL_RESULT_SET
    :  Kernel Error ID:
    :  DB Error: Yes
    :  SQL Code: 444-
    :  SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
    :  B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
    :  /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
    :  on code: "4". SQLSTATE=42724
    :  DB Object Exists: No
    :  Duplicated Key: No
    :  Internal Error: 1
    :  Invalid Cursor: No
    :  Unknown Connection: No
    :  Connection Closed: No
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :  Kernel Error ID:
      SYSID: ES1
      SY-SUBRC: 1208
      Message: ADBC error
      SQL statement: SELECT '20110613075634',0 as DB6PMCF_PARTITION,FS_NAM
      E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
      SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/sapdata4/d
      b2es1/NODE0000/ES1/T0000004/C0000000.UTM') ) ASFS_CONFIG
      Database:
    caused by
    Exception CX_SQL_EXCEPTION in class CL_SQL_RESULT_SET
      Kernel Error ID:
      DB Error: Yes
      SQL Code: 444-
      SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
      B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
      /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
      on code: "4". SQLSTATE=42724
      DB Object Exists: No
      Duplicated Key: No
      Internal Error: 1
      Invalid Cursor: No
      Unknown Connection: No
      Connection Closed: No
    xception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
      Kernel Error ID:
      SYSID: ES1
      SY-SUBRC: 1208
      Message: ADBC error
      SQL statement: SELECT '20110613075634',0 as DB6PMCF_PARTITION,FS_NAM
      E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
    :  SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/sapdata2/d
    :  b2es1/NODE0000/ES1/T0000004/C0000001.UTM') ) ASFS_CONFIG
    :  Database:
    :caused by
    :Exception CX_SQL_EXCEPTION in class CL_SQL_RESULT_SET
    :  Kernel Error ID:
    :  DB Error: Yes
    :  SQL Code: 444-
    :  SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
    :  B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
    :  /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
    :  on code: "4". SQLSTATE=42724
    :  DB Object Exists: No
    :  Duplicated Key: No
    :  Internal Error: 1
    :  Invalid Cursor: No
    :  Unknown Connection: No
    :  Connection Closed: No
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    :  Kernel Error ID:
    :  SYSID: ES1
    :  SY-SUBRC: 1208
    :  Message: ADBC error
    :  SQL statement: SELECT '20110613075634',0 as DB6PMCF_PARTITION,FS_NAM
    :  E,'T','20110521174003','700',FREE_KB,USED_KB,TOTAL_KB,NUM_IUSED,PCT_IU
    :  SED FROM SYSIBM.SYSDUMMY1, TABLE(SAPTOOLS.DB6PMCF('/db2/ES1/sapdata1/d
    :  b2es1/NODE0000/ES1/T0000004/C0000002.UTM') ) ASFS_CONFIG
    :  Database:
    :caused by
    :Exception CX_SQL_EXCEPTION in class CL_SQL_RESULT_SET
    :  Kernel Error ID:
    :  DB Error: Yes
    :  SQL Code: 444-
    :  SQL Message: SQL0444N Routine "SAPTOOLS.DB6PMCF" (specific name "D
    :  B6PMCF") is implemented with code in library orpath "/usr/sap/ED2/SYS
    :  /exe/run/db6pmudf", function "Db6pmcf" which cannot be accessed. Reas
    :  on code: "4". SQLSTATE=42724
    :  DB Object Exists: No
    :  Duplicated Key: No
    :  Internal Error: 1
    :  Invalid Cursor: No
    :  Unknown Connection: No
    :  Connection Closed: No
    Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
    Job finished

    Hi Dinesh,
    Please check the note is applicable for you [Note 978319 - DB6: Incorrectly cataloged table functions|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=978319]
    so please check wheter db2<sid>user has enough permission
    Thanks,
    Jansi

  • SAP_CCMS_MONI_BATCH_DP getting cancelled with error in program SAPLSPFL

    Hi Experts,
    The job SAP_CCMS_MONI_BATCH_DP scheduled by user DDIC is getting cancelled everyday at 20:00 CET (system time).
    The reason for the job getting cancelled with the runtime error Syntax error in program SAPLSPFL  and a short dump is generated.
    Runtime Errors         SYNTAX_ERROR
    Date and Time          07.03.2012 20:24:50
    Short text
        Syntax error in program "SAPLSPFL ".
    As per instructions I did syntax check for Program SAPLSPFL . It shows syntactical error as shown below.
    The following syntax error occurred in program "SAPLSPFL " in include "LSPFLF07
    " in
    line 148:
    "Bei PERFORM bzw. CALL FUNCTION "SET_DIRVALUE" ist der Aktualparameter "
    ""DIR_VALUES-DIR_ROLL" zum Formalparameter "DIR_VALUE" inkompatibel."
    Please help me on this.

    hi
    check out this SAP Note
    1000897  RZ10 profile import: Maximum path length is 60 characters

  • Error in background job for program RSGET_SMSY error message No active job

    Hello!
    I would like to set up the Change Request Management functionality in SAP Solution Manager.
    The only red warning by executing Test-button in Tcode “SOLAR_ADMIN_PROJECT” is:
    <b>Error in background job for program RSGET_SMSY error message No active job found</b>
    Can someone please tell me how to solve this problem?
    (tcodes, technical steps)
    Thank you very much!
    regards
    Thom

    Thank you very much!
    Can you also help me with the warning "Errors occurred during synchronization of the system landscape" in tcode SOLAR_PROJECT_ADMIN" --> System landscape --> Change requests --> "Refresh"?
    The second issue I cannot see any projects in Tcode "/TMWFLOW/CMSCONF"
    according to the SPRO-step "Set Project Assignment of Requests as Mandatory"
    Thank you!
    regards

  • Runn time error "CNTL_ERROR" for batch job created for program RBDAPP01

    We have encounter run time error and the batch job for program RBDAPP01 was terminated.
    Information on where terminated
        Termination occurred in the ABAP program "CL_GUI_CUSTOM_CONTAINER=======CP" -
         in "CONSTRUCTOR".
        The main program was "RBDAPP01 ".
        In the source code you have the termination point in line 62
        of the (Include) program "CL_GUI_CUSTOM_CONTAINER=======CM001".
        The program "CL_GUI_CUSTOM_CONTAINER=======CP" was started as a background job.
    Can any member reachout help in identifying the reason.

    Hi Amol,
    Check the following link.
    Call Transaction 'VL32N' in background: termination with Exception
    Regards,
    Raju.

  • Standard Job SAP_CCMS_MONI_BATCH_DP is cancelling

    Hello All
    I am facing problem with standard job SAP_CCMS_MONI_BATCH_DP...It is scheduled on hourly basis.
    But on some days at some time it is failing with only one error message as
    08/04/2011 17:52:26 Job started
    08/04/2011 17:52:26 Step 001 started (program RSAL_BATCH_TOOL_DISPATCHING, variant , user ID
    08/04/2011 17:52:29 You can only work in client 320
    08/04/2011 17:52:29 Job cancelled
    There is no specific time that it is failing.Please suggest me how can i resolve this?
    Manmohan Soni

    Hi,
    Looks like the client in which job is to run, is different from which client the job is called from.
    Check thread: Sm37 job problem
    Also check sm21 log to get more details.
    Regards,
    Srikishan

  • Job: SAP_CCMS_MONI_BATCH_DP

    Basis jobs seem to error on Sunday morning, after the Cold backup system outage ??
    The SAP_CCMS_MONI_BATCH_DP, but seems to error each week after the system is started up from the backup outage ??
    This past Sunday morning, the system stopped at 3:25 am and started 3:30 am
    Job scheudle to starts at : 04:15:59
    It fails everytime after system restarts on Sunday after cold backup....other times it works fine.
    Any help would be much appericated.
    Kumar

    Date       Time     Message text                                                                     Message class Message
    09/23/2007 04:16:03 Job started                                                                           00           516
    09/23/2007 04:16:03 Step 001 started (program RSAL_BATCH_TOOL_DISPATCHING, variant , user ID DANCHA)      00           550
    09/23/2007 04:17:14 No alerts in configuration range                                                  ME_CCMS_NAK      030
    09/23/2007 04:17:22 ABAP/4 processor: DBIF_RSQL_INVALID_CURSOR                                            00           671
    09/23/2007 04:17:22 Job cancelled                                                                         00           518
    ABAP Short dump:
    Runtime Error          DBIF_RSQL_INVALID_CURSOR
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          09/23/2007 04:17:22
    Error analysis
        An exception occurred. This exception is dealt with in more detail below
        . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
         neither
        caught nor passed along using a RAISING clause, in the procedure
         "SBOM_BUILD_SYSCHECK_TREE" "(FUNCTION)"
        Since the caller of the procedure could not have expected this exception
         to occur, the running program was terminated.
        The reason for the exception is:
        One of the database selections included a database commit.
        The selection was then supposed to continue. Before a
        database commit, however, all outstanding database selections must be
        concluded.
        Possible causes in the application program:
        Within a loop (SELECT/LOOP/EXEC SQL), one of the following
        statements is used:
        - MESSAGE (apart from MESSAGE S...)
        - COMMIT WORK
        - ROLLBACK WORK
        - CALL SCREEN
        - CALL DIALOG
        - CALL TRANSACTION
        - SUBMIT
        - BREAK-POINT
        - WAIT
        In debugging mode, a program sometimes triggers
        a "COMMIT WORK" during the database selection. As a result
        this termination may also occur in debugging mode with a correct
        program.
        A "COMMIT WORK" during debugging may be due to the following reasons:
        1. A program or screen was regenerated
           and updated in the database.
        2. Each user needs a private process in debugging mode, but
           the number of available processes is restricted. If this
           limit is exceeded, each debugging step then requires a
           "COMMIT WORK".
        The error occurred in a statement that accesses the table "DBCHECKORA ".
    see if that helps you.
    Kumar

  • Internal error occurs in background job scheduling

    Hi Experts,
    We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
    Please find the following observation on our side on this message.
    1) This message is not coming for only one report not for others.
    2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
    3) Persons having SE38 auhtorization are able to run this report.
    Please advise.
    Thanks in advance,
    Viven

    What is the message ID and number? Have you tried OSS search and debugging?
    What does this program do, in a nutshell?

  • SYNTAX_ERROR unable to log in to SAP system Syntax error in program "SAPMSE

    hi SAP Experts,
    I have applied Basis patch 12 and I scheduled the background.  Backgroud job was terminated. System became slow. Then I stopped the server and restarted.  Now, I am unable to log in to SAP GUI by entering Username and Password and getting syntax error.
    Syntax error in program "SAPMSEM1".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program '????????????????????????????"
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occured in program "SAPMSEM1" in include
    "CL_SALV_FORM_ELEMET==========CU" in
    line 13:
    "the type "IF_SALV_FORM_CONFIG" is unknown."
    The include has been created and last changed by:
    Created by: "SAP "
    Last Changed by: "SAP "
    I am unable to access any transction code.
    Please help me..
    Thanks in advance...
    Raju

    hi,
    Thanks for your response.
    i haven't take any back up.  can u pls tell me step by step procedure to implement the SP with TP.
    your answer will be helpful..
    Regards
    Raju

  • Unable to login in the system ---- Syntex Error is Program SAPLSFES

    Hi,
    We have Sol_Man 7(N/W 700) in Win2003 and MSSQL 2005.
    During Support pack SAPKB70014 application in our Soloution Manager, I have continued all the step in Dialog but today it shows a message that "Inform SAP system for tp termination".The SP application was running for almost 12-14hrs.
    Then I restart my SAP system.Now when I opening SAP GUI
    Message is comming
    ABAP Runtime Error   Error Code <no erorr name or code was mentioned >
    In bottom of the page messege is comming
    " Syntex Error is Program SAPLSFES "
    Login name & password not asking.
    I also found in the Slog that
    "WARNING:       Background job RDDIMPDP could not be started or terminated abnormally."
    In SAPIB70014
    2EETW000 sap_dext called with msgnr "1":
    2EETW000 -
    db call info -
    2EETW000 function:   db_xrtab
    2EETW000 fcode:      RT_MI_LOAD
    2EETW000 tabname:    SPROXHDR                     
    2EETW000 len (char): 1740
    2EETW000 key:        CLASCX_SERVICES_REGISTRY_SIPUBLIS8 CLASCX_SERVICES_REGISTRY_SIPUBLIS82F7E61BA8717B7CD295188A843F6CB8E97F12D39
    2EETW000 retcode:    1
    2EETW125 SQL error "1105" during "" access: "[1105] Could not allocate space for object 'dbo.SPROXHDR'.'SPROXHDR~HAS' in database 'SM1' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."
    I also checked and found that TRBAT table contains only header information where as TRJOB table is empty.
    Also found tp.exe in Task Manager.
    I have already created a message with SAP.
    Please guide me in this regard.
    Regards,
    Partha

    WARNING: Background job RDDIMPDP could not be started or terminated abnormally."
    login into Client 000 and schedule the background job again.
    Could not allocate space for object 'dbo.SPROXHDR'.'SPROXHDR~HAS' in database 'SM1' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."
    Check the database space also. i think there is some space problem also, you need to add some space or need to add datafile.
    Regards,
    Subhash

  • SUBMIT program VIA JOB and SET/GET parameter

    Hi All
    I need to pass the content of a variable from the program 'A' to program 'B'.
    Program A uses JOB_OPEN , SUBMIT program VIA JOB jobname NUMBER jobnumber AND return, JOB_CLOSE.
    I tried to use import/export memory but it didn't work. Then I am trying to use set/get parameters but it also did not work.
    Program A is going to run in any server and program B will run in the central instance (it is determined in the FM JOB_CLOSE, parameter target_server).
    Program does not have selection-screen.
    Is it possible use set/get parameter with submit via job?
    Could you please advise?
    Thanks in advance.
    João Gaia

    Here a simple code
    *Submit report as job(i.e. in background)
    data: jobname like tbtcjob-jobname value
                                 'TRANSFER DATA'.
    data: jobcount like tbtcjob-jobcount,
          host like msxxlist-host.
    data: begin of starttime.
            include structure tbtcstrt.
    data: end of starttime.
    data: starttimeimmediate like btch0000-char1 value 'X'.
    * Job open
      call function 'JOB_OPEN'
           exporting
                delanfrep        = ' '
                jobgroup         = ' '
                jobname          = jobname
                sdlstrtdt        = sy-datum
                sdlstrttm        = sy-uzeit
           importing
                jobcount         = jobcount
           exceptions
                cant_create_job  = 01
                invalid_job_data = 02
                jobname_missing  = 03.
      if sy-subrc ne 0.
                                           "error processing
      endif.
    * Insert process into job
    SUBMIT zreport and return
                    with p_param1 = 'value'
                    with p_param2 = 'value'
                    user sy-uname
                    via job jobname
                    number jobcount.
      if sy-subrc > 0.
                                           "error processing
      endif.
    * Close job
      starttime-sdlstrtdt = sy-datum + 1.
      starttime-sdlstrttm = '220000'.
      call function 'JOB_CLOSE'
           exporting
    "            event_id             = starttime-eventid
    "            event_param          = starttime-eventparm
    "            event_periodic       = starttime-periodic
                jobcount             = jobcount
                jobname              = jobname
    "            laststrtdt           = starttime-laststrtdt
    "            laststrttm           = starttime-laststrttm
    "            prddays              = 1
    "            prdhours             = 0
    "            prdmins              = 0
    "            prdmonths            = 0
    "            prdweeks             = 0
    "            sdlstrtdt            = starttime-sdlstrtdt
    "            sdlstrttm            = starttime-sdlstrttm
                strtimmed            = starttimeimmediate
    "            targetsystem         = host
           exceptions
                cant_start_immediate = 01
                invalid_startdate    = 02
                jobname_missing      = 03
                job_close_failed     = 04
                job_nosteps          = 05
                job_notex            = 06
                lock_failed          = 07
                others               = 99.
      if sy-subrc eq 0.
                                           "error processing
      endif.
    Then... for import/export of a variable, you can use Import Memory and Export Memory function.
    Like this:
    REPORT A:
      IF NOT it_dlist_out IS INITIAL.
        EXPORT it_dlist_out TO MEMORY ID 'TEST1234'.
      ELSE.
    * Clearing memory
        FREE MEMORY ID 'TEST1234'.
      ENDIF.
    REPORT B:
    IMPORT it_dlist_out TO lt_dlist_out FROM MEMORY ID 'TEST1234'.
    Edited by: spantaleoni on Jan 11, 2011 3:21 PM
    Edited by: spantaleoni on Jan 11, 2011 3:23 PM

  • RFC error while running sync job in AC 10

    I have done all the configuration to add new SAP system via SPRO in GRC 10. Now I am trying to run the sync job for the first time, I am getting the below mssage. I checked the RFC desitinations, it looks fine.
    Error in RFC; 'Function module "/GRCPI/GRIA_ROLE_GET_RANGES" not'
    Error in RFC; 'Function module "/GRCPI/GRIA_ROLE_GET_RANGES" not'
    Role sync failed with errors
    Program for Repository User Synchronization
    Error in RFC; 'Function module "/GRCPI/GRIA_USR_GET_RANGES" not f'
    User sync failed with errors
    Repository Object sync job failed with errors
    Please check SLG1 for further details
    I checked in SLG1 also, its displaying the same errors as listed above.  I have some systems added earlier which are correctly configured and working fine. I tried to match the configuration with the new systems, and everything looks fine. Not sure why this error is coming.
    Please someone can help.

    Hello,
    It seems to be a problem with the add-on in the back-en system, and a function module couldn't be found. Check the RFC connection (refer here for example GRC AC10 sync job error ) and make sure the add-on is properly installed.A simple check could be go to the back-end system, tx SE37 and check if the function modules exist.
    Cheers,
    Diego.

  • Syntax error in program "SAPLHTTPTREE " during application of SAPKB70012

    Hi everyone,
    I am applying support pack SAPKB70012 when it stopped in the XPRA_EXECUTION phase. Anybody encountered this error "Syntax error in program "SAPLHTTPTREE "? Been looking for any notes on this but haven't found anything. I already created message to SAP but even though its high, nobody's picking it up. We're using Windows NT and database MSSQL.
    Below is part of the import queue log:
    The following details help you to analyze the problem:
        -   Error in phase: XPRA_EXECUTION
        -   Reason for error: TP_STEP_FAILURE
        -   Return code: 0012
        -   Error message: OCS Package SAPKB70012, tp step R, return code
            0012
    Notes on phase XPRA_EXECUTION
    The XPRAs and after-import methods are executed in this phase. This
    phase can terminate due to the following reasons:
    o   TP_INTERFACE_FAILURE: The system was unable to call the tp
        interface.
    o   TP_FAILURE: The system was unable to execute the tp program. For
        more information, see the SLOG or ALOG log file.
    When I check SM37, I found this ABAP runtime error:
    *job: RDDEXEC
    Runtime Errors         SYNTAX_ERROR
    Date and Time          16.01.2008 19:13:09
    Short text
    Syntax error in program "SAPLHTTPTREE ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSCTS_EXE_EXP" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLHTTPTREE " in include
    "LHTTPTREETOP " in
    line 9:
    ""ICFALIAS" must be a flat structure. You cannot use internal tables, s"
    "trings, references, or structures as components ."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "SAPLHTTPTREE ".
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    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
    The following syntax error was found in the program SAPLHTTPTREE :
    ""ICFALIAS" must be a flat structure. You cannot use internal tables, s"
    "trings, references, or structures as components ."
    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 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
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    User and Transaction
    Client.............. 000
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "0224C4DC1741F1C28D9D001A4BDB2C98"
    Program............. "SAPLSCTS_EXE_EXP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "SAPLSCTS_EXE_EXP" - in
    "CALL_IMP_METHODS_IN_CLIENT".
    The main program was "RDDEXECU ".
    In the source code you have the termination point in line 351
    of the (Include) program "LSCTS_EXE_EXPF02".
    The program "SAPLSCTS_EXE_EXP" was started as a background job.
    Job Name....... "RDDEXECL"
    Job Initiator.. "DDIC"
    Job Number..... 19130500
    Source Code Extract
    Line
    SourceCde
    321
    CLEAR: sy-msgid, sy-msgty, sy-msgno.
    322
    323
    IF ps_spec_pars-with_data_file EQ 'X'.
    324
    CALL FUNCTION ps_method_call-method_fb
    325
    EXPORTING
    326
    iv_tarclient  = ps_client-client
    327
    iv_is_upgrade = pv_is_upgrade
    328
    iv_datafile   = ps_spec_pars-data_file
    329
    TABLES
    330
    tt_e071       = lt_e071
    331
    tt_e071k      = lt_e071k.
    332
    ELSEIF ps_spec_pars-with_asynch_mode EQ 'X'.
    333
    CALL FUNCTION ps_method_call-method_fb
    334
    EXPORTING
    335
    iv_tarclient    = ps_client-client
    336
    iv_is_upgrade   = pv_is_upgrade
    337
    iv_asynchronous = ps_spec_pars-asynch_mode
    338
    TABLES
    339
    tt_e071         = lt_e071
    340
    tt_e071k        = lt_e071k.
    341
    ELSEIF ps_spec_pars-with_cl_results EQ 'X'.
    342
    CALL FUNCTION ps_method_call-method_fb
    343
    EXPORTING
    344
    iv_trkorr     = pv_trkorr
    345
    iv_is_upgrade = pv_is_upgrade
    346
    it_e071       = lt_e071
    347
    it_e071k      = lt_e071k
    348
    CHANGING
    349
    it_client     = ps_spec_pars-clients.
    350
    ELSE.
    >>>>>
    CALL FUNCTION ps_method_call-method_fb
    352
    EXPORTING
    353
    iv_tarclient  = ps_client-client
    354
    iv_is_upgrade = pv_is_upgrade
    355
    TABLES
    356
    tt_e071       = lt_e071
    357
    tt_e071k      = lt_e071k.
    358
    ENDIF.
    359
    360
    361
    reset info on called method in memory.
    362
    CALL FUNCTION 'TRINT_RESET_STACK_KILLER'.
    363
    check if method call has deleted variables in global memory
    364
    and set those variables again
    365
    CALL FUNCTION 'TRINT_CHECK_VARS_IN_MEMORY'
    366
    IMPORTING
    367
    ev_ok = lv_ok.
    368
    IF lv_ok = ' '.
    369
    memory destroyed: set all clients to errornous for security
    370
    for methods of switch framework
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    2
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Execute Post-Import Methods and XPRAs for Transport Request
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    ASYNCH_IAC_PUBLISH
    SY-MSGV2
    0011
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080116
    SY-UZEIT
    191309
    SY-XPROG
    SAPLSYST
    SY-XFORM
    SYSTEM_HOOK_OPEN_DATASET
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    5 FUNCTION     SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                      351
    CALL_IMP_METHODS_IN_CLIENT
    4 FORM         SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                      351
    CALL_IMP_METHODS_IN_CLIENT
    3 FORM         SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                       87
    CALL_IMP_METHODS
    2 FUNCTION     SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPU02                      103
    TRINT_CALL_AFTER_IMP_METHOD
    1 EVENT        RDDEXECU                            RDDEXECU                              171
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       5 Ty.          FUNCTION
    Name  CALL_IMP_METHODS_IN_CLIENT
    GC_GNS_NO_DIFF
    /0*/
    2322222222
    F0AF000000
    0000000000
    0000000000
    LT_E071
    Table IT_137[21x360]
    FUNCTION-POOL=SCTS_EXE_EXPFORM=CALL_IMP_METHODS_IN_CLIENTDATA=LT_E071
    Table reference: 46
    TABH+  0(20) = B0A6D957FE07000050C8D957FE07000000000000
    TABH+ 20(20) = 2E000000890000001500000068010000FFFFFFFF
    TABH+ 40(16) = 044D0000F00B000015000000C9248001
    store        = 0xB0A6D957FE070000
    ext1         = 0x50C8D957FE070000
    shmId        = 0     (0x00000000)
    id           = 46    (0x2E000000)
    label        = 137   (0x89000000)
    fill         = 21    (0x15000000)
    leng         = 360   (0x68010000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000049
    occu         = 21    (0x15000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xF0C0E257FE070000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x10A7D957FE070000
    shmTabhSet   = 0x0000000000000000
    id           = 111   (0x6F000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 21    (0x15000000)
    lineAlloc    = 21    (0x15000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 2     (0x02000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x90C4D957FE070000
    collHook     = 0x0000000000000000
    ext2         = 0x0000000000000000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    GC_GNS_NO_SPECIFIC
    2222222222
    FAF0000000
    0000000000
    0000000000
    LT_E071K
    Table[initial]
    RELSET
    RNO
    544
    2EF
    000
    000
    PS_SPEC_PARS-WITH_CL_RESULTS
    2
    0
    0
    0
    SY-XPROG
    SAPLSYST
    5454555522222222222222222222222222222222
    310C393400000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    PS_METHOD_CALL-METHOD_FB
    SICF_AFTER_IMPORT
    544454454554454552222222222222
    3936F16452F9D0F240000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    GC_PARTNRPR_BACK_TO_STNDRD
    1A&1B&1H&1I&2I&3R
    34234234234234235
    11612618619629632
    00000000000000000
    00000000000000000
    PV_IS_UPGRADE
    2
    0
    0
    0
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PV_TRKORR
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    SYST-REPID
    SAPLSCTS_EXE_EXP
    5454545554545455222222222222222222222222
    310C3343F585F580000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    DEVC_PREFIXNS
    N
    4
    E
    0
    0
    PS_SPEC_PARS-CLIENTS
    Table[initial]
    %_PRINT
    000                                                                                0###
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PS_CLIENT-CLIENT
    222
    000
    000
    000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    No.       4 Ty.          FORM
    Name  CALL_IMP_METHODS_IN_CLIENT
    LT_E071
    Table IT_137[21x360]
    LT_E071K
    Table[initial]
    PS_SPEC_PARS-WITH_CL_RESULTS
    2
    0
    0
    0
    PS_METHOD_CALL-METHOD_FB
    SICF_AFTER_IMPORT
    544454454554454552222222222222
    3936F16452F9D0F240000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    PV_IS_UPGRADE
    2
    0
    0
    0
    PV_TRKORR
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    PS_SPEC_PARS-CLIENTS
    Table[initial]
    PS_CLIENT-CLIENT
    222
    000
    000
    000
    No.       3 Ty.          FORM
    Name  CALL_IMP_METHODS
    PV_TRKORR
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    PV_NO_WORK_FOUND
    2
    0
    0
    0
    PT_CLIENT
    Table IT_21[1x8]
    PROGRAM=RDDEXECUDATA=GT_CLIENT
    Table reference: 16
    TABH+  0(20) = B0311757FE070000000000000000000000000000
    TABH+ 20(20) = 10000000150000000100000008000000FFFFFFFF
    TABH+ 40(16) = 040000009008000010000000C1248001
    store        = 0xB0311757FE070000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 16    (0x10000000)
    label        = 21    (0x15000000)
    fill         = 1     (0x01000000)
    leng         = 8     (0x08000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000031
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x10311757FE070000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 20    (0x14000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    LS_CLIENT_H
    2222
    0000
    0000
    0000
    TTRA
    T
    5
    4
    0
    0
    SY
    ######################################f#######################################T#########  ####
    0000000000000000000000000000000000000060000000000000000000000000000000000000105000000080220000
    0000104000000000000010201000100000000060000000000000000000000000000000000000604000000000000300
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
    PV_UPDATE_LOCKFLAG
    X
    5
    8
    0
    0
    PV_CTC
    2
    0
    0
    0
    PV_STATLOG_FILE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PS_METHOD_CALL
    AFTER_IMP SICF_AFTER_IMPORT              ###Á#>#À#?###@#
    44545544525444544545544545522222222222222000C030C0309040
    16452F9D003936F16452F9D0F240000000000000000010E000F0F000
    00000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000
    PV_IS_UPGRADE
    2
    0
    0
    0
    PV_TOP_LEVEL
    2
    3
    2
    0
    0
    PS_SPEC_PARS
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PS_METHOD_CALL-CLIDEP
    2
    0
    0
    0
    PS_SPEC_PARS-WITH_CL_RESULTS
    2
    0
    0
    0
    %_VIASELSCR
    0
    4
    No.       2 Ty.          FUNCTION
    Name  TRINT_CALL_AFTER_IMP_METHOD
    IS_E070
    SAPKB70012          DRSAP       SYSTSAPUSER     20080116185743
    5454433333222222222245545222222255555455545222223333333333333322222222222222222222
    310B270012000000000042310000000039343105352000002008011618574300000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IT_E071
    Table IT_15[23207x360]
    PROGRAM=RDDEXECUDATA=E071_TAB[]
    Table reference: 10
    TABH+  0(20) = C0841857FE070000B0611757FE07000000000000
    TABH+ 20(20) = 0A0000000F000000A75A000068010000FFFFFFFF
    TABH+ 40(16) = 04000000C005000010000000C1248001
    store        = 0xC0841857FE070000
    ext1         = 0xB0611757FE070000
    shmId        = 0     (0x00000000)
    id           = 10    (0x0A000000)
    label        = 15    (0x0F000000)
    fill         = 23207 (0xA75A0000)
    leng         = 360   (0x68010000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000016
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x206E1857FE070000
    pgHook       = 0x30047F57FE070000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 14    (0x0E000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32752 (0xF07F0000)
    lineAlloc    = 23216 (0xB05A0000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0x40611757FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xD0C31F57FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    IT_E071K
    Table IT_16[6045x564]
    PROGRAM=RDDEXECUDATA=E071K_TAB[]
    Table reference: 11
    TABH+  0(20) = 20851857FE070000F0611757FE07000000000000
    TABH+ 20(20) = 0B000000100000009D17000034020000FFFFFFFF
    TABH+ 40(16) = 040000005006000010000000C1248001
    store        = 0x20851857FE070000
    ext1         = 0xF0611757FE070000
    shmId        = 0     (0x00000000)
    id           = 11    (0x0B000000)
    label        = 16    (0x10000000)
    fill         = 6045  (0x9D170000)
    leng         = 564   (0x34020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000019
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x00C49357FE070000
    pgHook       = 0x60E75357FE070000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 15    (0x0F000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 8192  (0x00200000)
    lineAlloc    = 6048  (0xA0170000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xE06F1757FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x806F1757FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    IV_CTC
    2
    0
    0
    0
    IV_DATNAME
    :D:T:S:data:F:IB70012.SAP
    3435353667634344333332545222222222222222222222222222222222222222222222222222222222222222222222
    A4A4A3A4141A6A9270012E310000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IV_SFW_CALL
    2
    0
    0
    0
    IV_STATLOG_FILE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IV_TRKORR
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    IV_UPDATE_LOCKFLAG
    X
    5
    8
    0
    0
    IT_CLIENT
    Table IT_21[1x8]
    LS_SPEC_PARS-NOT_DURING_UPGRADE
    2
    0
    0
    0
    ALLSTAT
    RNODL
    54444222222222222222222222
    2EF4C000000000000000000000
    00000000000000000000000000
    00000000000000000000000000
    LV_UPGRADE_IS_RUNNING
    2
    0
    0
    0
    TMVD
    E
    4
    5
    0
    0
    RSJOBINFO
    00000000000000                                  ##
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    <LS_METHOD_CALL>
    AFTER_IMP SICF_AFTER_IMPORT              ###Á#>#À#?###@#
    44545544525444544545544545522222222222222000C030C0309040
    16452F9D003936F16452F9D0F240000000000000000010E000F0F000
    00000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000
    LV_IS_UPGRADE
    2
    0
    0
    0
    LV_TOP_LEVEL
    2
    3
    2
    0
    0
    LV_NO_WORK_FOUND
    2
    0
    0
    0
    LS_SPEC_PARS
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SPACE
    2
    0
    0
    0
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    SCREEN
    %_17NNS0000691660_%_%_%_%_%_%_
    2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
    5F17EE30000691660F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST
    ######################################f#######################################T#########  ####
    0000000000000000000000000000000000000060000000000000000000000000000000000000105000000080220000
    0000104000000000000010201000100000000060000000000000000000000000000000000000604000000000000300
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
    GT_CLIENT
    Table IT_21[1x8]
    GS_CLIENT
    2222
    0000
    0000
    0000
    DATNAME
    :D:T:S:data:F:IB70012.SAP
    3435353667634344333332545222222222222222222222222222222222222222222222222222222222222222222222
    A4A4A3A4141A6A9270012E310000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_DATNAME_%_APP_%
    Data File Name (from TRBAT)
    467624666246662267662554452222
    4141069C50E1D50862FD0422149000
    000000000000000000000000000000
    000000000000000000000000000000
    E071_TAB[]
    Table IT_15[23207x360]
    E071K_TAB[]
    Table IT_16[6045x564]
    SY-SUBRC
    0
    0000
    0000
    GV_CTC
    2
    0
    0
    0
    GV_TRBAT_DATNAME
    :D:T:S:data:F:IB70012.SAP
    3435353667634344333332545222222222222222222222222222222222222222222222222222222222222222222222
    A4A4A3A4141A6A9270012E310000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    <%_TABLE_E071>
    <%_TABLE_E071K>
    GV_STATLOG_FILE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    COMFILE
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    SY-LANGU
    E
    4
    5
    0
    0
    SY
    ######################################f#######################################T#########  ####
    0000000000000000000000000000000000000060000000000000000000000000000000000000105000000080220000
    0000104000000000000010201000100000000060000000000000000000000000000000000000604000000000000300
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
    SPACE
    2
    0
    0
    0
    Internal notes
    The termination was triggered in function "ab_genprog"
    of the SAP kernel, in line 1476 of the module
    "//bas/700_REL/src/krn/runt/abgen.c#5".
    The internal operation just processed is "FUNC".

    Good Morning
    Did you ever get this working without restoring ?
    Kind Regards
    Marius

  • ABAP Runtime ERROR Error Code & Syntax Error in program SAPLSFES

    Hi,
    I am installing SAP XI 3.0 and as part of that I have installed the ABAP and Java WAS. I am applying SPs for the ABAP stack and I successfully applied the BASIS SPs 10 and 11(applied seperately). I was applying the SPs 12 and 13(together) and after running for some time the system crashed and I restarted the O/S and SAP to see that the SPs didn't go thru. Now when I try to log on using SAP GUI, it says "<b>ABAP Runtime ERROR Error Code</b>" which is blank and at the Bottom there is this message "<b>Syntax Error in program SAPLSFES</b>".
    Pls any one help me ,
    Kind Regards,
    Gopi.

    Hi Gopi,
       If u r applying patches, the system would be running a background job SAPLSTPA. Hence you willnot be able to login till the job is complete.
      You can check the job completion in the Windows MMC console.
    Rgds
    Ganesh

  • Errors while running Sync Jobs in GRC 10

    Dear Experts,
    I am trying to configure RAR in GRC 10. I have all required config steps and now I am trying to run Sync Jobs and I am getting below errors.
    Authorization Synch
    Program for Authorization data Synchronization
    Starting authorization sync for connector RC1 and language EN
    Error in RC1; Reason Error in RFC; 'Function module "/GRCPI/GRIA_AUTH_G
    PFCG authorization sync failed with errors
    Repository Object Synch
    Program for Repository Profile Syncronization
    Processing for connector RC1
    Error in RFC; 'Function module "/GRCPI/GRIA_PROF_GET_RANGES" not'
    Profile sync failed with errors
    Program for Repository Role Synchronization
    Processing for connector RC1
    Error in RFC; 'Function module "/GRCPI/GRIA_ROLE_GET_RANGES" not'
    Role sync failed with errors
    Program for Repository User Synchronization
    Processing for connector RC1
    Error in RFC; 'Function module "/GRCPI/GRIA_USR_GET_RANGES" not f'
    User sync failed with errors
    Repository Object sync job failed with errors
    Please check SLG1 for further details
    I appreciate your help.
    Thanks,
    Raj

    Hi Raj,
    I have a similar error for which I have put up a separate post, your input would be highly valuable.
    My RFC connection works via the test in SM59 but when executing GRAC_AUTH_SYNC I get a simiar error to your above.
    Please let me know what steps you took.
    Best regards,
    Paul

Maybe you are looking for