All SAP session terminating while accessing RSA1

Hi All,
All sap sessions terminating while accessing RSA1 transaction, i can access other t-codes other than RSA1 if i am entering RSA1 all R3 Session including the BW session is terminating ...
Please help...
Thanks

Hi Peter,
Even some time back i have faced the issue when ever i click on dislplay infocube or Transfer rulesor DSO
The session used to terminate
After investigation i found it is authorization issue
ask you security team to investigate on this like switching on the trace and find what object is missing
and also try with T-codes like RSA11,RSA12,RSA14,RSA15 instead trying RSA1 Directely
these are individual transactions for each screen in RSA1 like
infoarea,infoobject...
hope this helps you....
thank
kishore

Similar Messages

  • Short Dump While Accessing RSA1 in BI7.0 with SP 21

    Hi,
    The following short dump occurs, while Accessing RSA1 in BI7.0
    Runtime Errors SYNTAX_ERROR
    Date and Time 26.10.2010 10:19:35
    Short text
         Syntax error in program "CL_RSTRAN_STAT================CP ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_RSAWBN_OBJ_TRFN============CP" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program
          "CL_RSTRAN_STAT================CP " in include
          "CL_RSTRAN_STAT================CM00X " in
         line 34:
         "Der formale Parameter "E_TLOGO_MASK" existiert nicht."
         The include has been created and last changed by:
         Created by: "SAP "
         Last changed by: "SAP "
         Error in the ABAP Application Program
         The current ABAP program "CL_RSAWBN_OBJ_TRFN============CP" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
    What can you do?
        Please eliminate the error by performing a syntax check
        (or an extended program check) on the program "CL_RSTRAN_STAT================CP
        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
         CL_RSTRAN_STAT================CP :
        "Der formale Parameter "E_TLOGO_MASK" existiert nicht."
    i.e parameter E_TLOGO_MASK is not existing.
    I have gone through below old thread, but its for old SP
    Runtime Error SYNTAX_ERROR while accessing the T-code RSA1
    In our case, I guess it refers to our patch level as this SAP Note is referring to support package 17,
    but we have implemented support package 21.
    Please help <REMOVED_BY_MODERATOR> as this is blocking our next level in BI upgrade process.
    Thanks in advance.
    Regards,
    Manikandan Dhanakoti
    Edited by: Manikandan.D on Oct 29, 2010 8:37 AM
    Edited by: Pravender on Nov 1, 2010 12:30 PM

    See if below threat is any help.
    Runtime Error SYNTAX_ERROR while accessing the T-code RSA1

  • Change Mode terminates All SAP sessions

    I am having a strange and Irritating Issue.
    SAP sessions are getting closed , Whenever I get into change mode of some transaction
    It happened in SE38 and SE12.Some times it is not working for display.
    I tried to view a report in display mode but it closes all Sap sessions
    I am not able to continue with any development work.
    Plz advice.....
    Thanks,
    AJR
    Edited by: A J Raj on Sep 17, 2009 6:29 PM
    Edited by: A J Raj on Sep 18, 2009 2:16 PM

    What SAP GUI version and patch level are you using? Check for SAP note with this version and there could be a note for this to fix. Otherwise, update GUI patchlevel.

  • SESSION TERMINATED WHILE INSTALLING

    Hi All,
    We have kickked of ECC6.0 on linux  with maxdb every thing is going fine but at import abap phase the link to the ipaddress where the sap was installed has gone but any how i could login.
    But the session where sap was installed was gone
    But i saw in log files some thing was running in import abap phase
    to see the sapinstgui.
    Should i restat sapinstgui with older option continue with older options to see the current step of installation.
    OR ANY OTHER SUGGESTION TO CHECK MY CURRENT STEP OF INSTALLATION.
    PLEASE HELP ME
    Thanks!
    Vardhan.

    Hi Sunny
    Thanks for the reply and conformation.
    Even  i am able to see the current step progress from tmp directory logs  in ImportMonotor.Console.log
    Thanks!
    Vardhan.

  • Introduction of Bebo, a control pad for SAP sessions

    Hello community,
    Bebo for is a small utility to watch, navigate and control all SAP sessions of the SAP GUI for Windows. Bebo is an acronym, in long description it means Best Boy. A Best Boy is the first assistant of the lighting technician in movie production, he do all the technical work - like Bebo. With Bebo you see all sessions, which supports SAP GUI scripting, clearly arranged in a tree. Also you can direct execute a transaction or a script to one of these sessions. The available transaction codes, scripts or other actions are an easy and individual customizing in a preference file. So you can organize your favorite activities in a tree as you want - one time for all application servers. Also you see in a collection list all other sessions.
    With a simple click in the session tree or collection list you can choose the session you want and it is direct on top of all the open windows. If you click the right mouse button, it opens a popup menu and you can close the session or the connection, or you can resize the session window or or or ... And with a simple double click in the transaction tree you send a transaction code or a script to the selected session from the session tree. With the possibilities of the toolbar you can e.g. minimze all sessions with one single click, or restore it. Bebo helps you in the jungle of sessions and connections - it is a point of view.
    Bebo is freeware and you find it [here|http://www.stschnell.de/bebo.htm]. Suggestions and comments are welcome.
    Cheers
    Stefan

    Dear Aditya,
                      You may not be shame of what you seen in the wizard,because that code is not written by a single abaper and the cutomised that you have developed is what may a single abaper can do.SAP has given all flexibility to fulfill the Business Requirements,after all SAP is also a Product.As the technology is growing the amount of work increases .In order to make reduce redudant code throught  SAP .It has given all the wizards to help a Abaper to complete the work with less time.
    Regards,
    Amit Teja

  • Error while trying to access RSA1 in SAP NETWEAVER 2004 S

    HI friends,
                i am working on SAP NETWEAVER  2004s  and have created a few open hub destinations in this and when i tried to delete a  few , system is showing an error " Destination Type is not Supported"  when ever i am trying to access RSA1 .
               i will be glad if you could let me know how to overcome this,
    thanks and regards,
    sasdihar gunturu
    points will be awarded***

    Hi Gunturu,
    Do you know what sp level are you working with ?
    Here you´ll find a detail of sp level and his corrections, see the 22 page. Maybe that help you.
    https://websmp207.sap-ag.de/~sapidb/011000358700004483762006E
    Regards,
    Natalia.

  • ERROR MESSAGE sap system manager:work process restarted, session terminated

    Hi,
    i am a beginer in SAP administration, users are getting this error message and i have done all my research and not able to resolve this issue. Here are the details
    SAP Version :ideas 4.7
    Database :Oracle
    OS : windows 2003
    Module user is working on MM
    user working on it is a Super user with all the permissions
    SAP is configure to run under the  European date and decimal format.
    I have never done any database administration on it, it is a new install and has been rarely used.
    User creates a RFQ and when he tries saving it , seems like for the first time after either restarting the macine or restarting the service it might work and at time it might not, this is a very sporadic error and most of the times it crashes out with the message "sap system manager:work process restarted, session terminated" and kicks the user out of the session.
    Below are the details of the error message from ST22 :
    name of the runtime error : system_core_dumped
    below are the details of the error message and its resoltion as suggested by sap help :
    ========
    Runtime Errors         SYSTEM_CORE_DUMPED           
           Occurred on     01.02.2008 at 07:52:19
    Process terminated by signal " ".                                             
    What happened?
    The current ABAP program had to be terminated because the                     
    ABAP processor detected an internal system error.                             
    The current ABAP program "SAPLCLSC" had to be terminated because the ABAP     
    processor discovered an invalid system state.                                 
    What can you do?
                                                                                    Make a note of the actions and input which 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
    An SAP System process was terminated by an operating system signal.           
                                                                                    Possible reasons for this are:                                                
    1. Internal SAP System error.                                                 
    2. Process was terminated externally (by the system administrator).           
               Last error logged in SAP kernel                                    
                                                                                    Component............ "Taskhandler"                                           
    Place................ "SAP-Server server1_DEV_00 on host server1 (wp 1)"      
    Version.............. 1                                                       
    Error code........... 11                                                      
    Error text........... "ThSigHandler: signal"                                  
    Description.......... " "                                                     
    System call.......... " "                                                     
    Module............... "thxxhead.c"                                            
    Line................. 9555                                                                               
    How to correct the error
    The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often             
    contains a file called 'core'.                                                                               
    Save this file under another name.                                                                               
    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.............. " "                                                                               
    Application server....... " "                                                 
    Network address.......... " "                                                 
    Operating system......... " "                                                 
    Release.................. " "                                                 
    Hardware type............ " "                                                 
    Character length......... " " Bits                                            
    Pointer length........... " " Bits                                            
    Work process number...... " "                                                 
    Short dump setting....... " "                                                                               
    Database server.......... " "                                                 
    Database type............ " "                                                 
    Database name............ " "                                                 
    Database owner........... " "                                                                               
    Character set............ " "                                                                               
    SAP kernel............... " "                                                 
    Created on............... " "                                                 
    Created in............... " "                                                 
    Database version......... " "                                                                               
    Patch level.............. " "                                                 
    Patch text............... " "                                                                               
    Supported environment....                                                     
    Database................. " "                                                 
    SAP database version..... " "                                                 
    Operating system......... " "                                                 
    User, transaction...
    Client.............. " "                                                      
    User................ " "                                                      
    Language key........ " "                                                      
    Transaction......... "ME41 "                                                  
    Program............. "SAPLCLSC"                                               
    Screen.............. "SAPMM06E 0320"                                          
    Screen line......... 71                                                       
    Information on where termination occurred
    The termination occurred in the ABAP program "SAPLCLSC" in "EXECUTE_SELECT".  
    The main program was "SAPMM06E ".                                                                               
    The termination occurred in line 131 of the source code of the (Include)      
    program "LCLSCF2G"                                                           
    of the source code of program "LCLSCF2G" (when calling the editor 1310).      
    =============
    i even tried increasing the dialog processes but with no use.The same error occurs.
    I appreciate every one of help i can get, i am working on a deadline which is tomorrow evening to resovle this issue, any kind of help is highly appreciated.
    thanks
    mudessir.

    Hi
       follow correction method suggested in this dump,
    " The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
    contains a file called 'core'.  Save this file under another name."
    have you done this?
    with regards,
    raj.
    <i>pls, award points</i>

  • Hi All,  In my SAP environment, i want to give access of all SAP reports to

    Hi All,
    In my SAP environment, i want to give access of all SAP reports to my main management and if there is any role which have all SAP reports or substitute solution for it..there are more than 500 reports in every modules (SD,MM,PM...etc).
    Reports:
    S_ALR_87012183
    S_ALR_87012193
    S_PH9_46000223
    waiting ur good response???
    regards,
    majamil

    Hmm...Julius, you have given ME food for thought .. ha ha
    Since the business team would decide on the criticality of transactions, I am firing this bold statement keeping the gun of their shoulders Because, this is how we implemented this, based on their feedback!
    An initial wind blows saying these are non-critical, however , I will definately research this more (keeping in mind, I have one difficult person to convince   )
    >
    Julius Bussche wrote:
    > PS: Your "continue only" comment a while back was interesting
    >
    Which one?

  • Adobe Flash Player Plugin crashes in ALL browsers while accessing webcam

    Hi,
    I am struggling to get my adobe flash player plug-in working while accessing webcam.
    It simply crashes in all browsers. I googled this issue and realized many users are facing this issue.
    However I did not get any solution to fix this. I tried uninstalling/reinstalling plug-in multiple times but of no use.
    Following are specifications:
    OS: Microsoft Windows XP Professional (32 Bit) SP3
    Browsers: Internet Explorer (8.0), Chrome (8.0), Mozilla Firefix (3.0)
    Webcam: Dell monitor inbuilt webcam
    Flash Player version: 10,1,102,64
    Please note, the webcam is accessible through other applications (e.g. Yahoo! Messenger, Skype, Windows Explorer)
    Also, Adobe Flash player doesn’t give any trouble while playing streaming videos on YouTube etc.
    Trouble is only when flash player tries to access webcam through any browser (eg. while "Record from Webcam" on YouTube)
    An interesting observation I like to note here, the device list that appears in the plug-in window is blank for both video/audio devices (See the area encircled  RED in the image below)
    Not sure, but just suspecting could this be potential reason for crash?
    Any advice would be appreciated.
    Thanks,
    Struggler

    Hello all,
    My doubt was correct. It was all due to the blank device list. After lot of struggle I found this solution worked for me:
    1. As soon as the plug-in tries to access webcam, it will show you "Adobe Flash Player Settings" box
    2. Click Deny then Close to close it
    3. Now press tab key on keyboard. It will highlight (in yellow) and show list of devices in video device dropdown control (This could be little bit tricky and you need to put little bit more efforts to see the list). You can now select your webcam as device here.
    4. Press Tab key again to go audio dropdown and select audio device.
    5. Then right click and bring up "Adobe Flash Player Settings" again.
    6. Under Microphone and Camera tabs, make sure we select same devices we selected in 3 & 4 above
    7. Come back to privacy tab and this time chose "Allow" and then close "Adobe Flash Player Settings" box
    8. You should now see the camera images in the plug-in
    Conclusion: This is a workaround worked for me. Plug-in is quite unstable and there is definitely something here Adobe Flash Player plug-in developers need to do about.
    Hope this workaround helps many other users.
    Thanks,
    Struggler

  • Work process re-started , session terminated

    Hi Gurus,
    While i creating a purchase order (me21n) , the process runs for a while and then i am getting a SAP GUI message "Work process re - started , session terminated" and the session is closed.Can anyone give me the cause of the problem and solution for the same.
    Developers Trace File Entry:
    trc file: "dev_w0", trc level: 1, release: "640"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, M
    B B Fri Aug 31 16:09:36 2007
    B  create_con (con_name=R/3)
    B  Loading DB library 'C:\usr\sap\I04\SYS\exe\run\dbmssslib.dll' ...
    B  Library 'C:\usr\sap\I04\SYS\exe\run\dbmssslib.dll' loaded
    B  Version of 'C:\usr\sap\I04\SYS\exe\run\dbmssslib.dll' is "640.00", patchlevel (0.26)
    B  New connection 0 created
    M systemid   560 (PC with Windows NT)
    M relno      6400
    M patchlevel 0
    M patchno    25
    M intno      20020600
    M make:      multithreaded, ASCII
    M pid        1680
    M
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 1680) [dpxxdisp.c   1160]
    I  MtxInit: -2 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: JAVA is not active
    M  DpShMCreate: sizeof(wp_adm)        7456    (828)
    M  DpShMCreate: sizeof(tm_adm)        2219848    (11044)
    M  DpShMCreate: sizeof(wp_ca_adm)        18000    (60)
    M  DpShMCreate: sizeof(appc_ca_adm)    6000    (60)
    M  DpShMCreate: sizeof(comm_adm)        192000    (384)
    M  DpShMCreate: sizeof(vmc_adm)        0    (320)
    M  DpShMCreate: sizeof(wall_adm)        (22440/34344/56/100)
    M  DpShMCreate: SHM_DP_ADM_KEY        (addr: 05230040, size: 2506248)
    M  DpShMCreate: allocated sys_adm at 05230040
    M  DpShMCreate: allocated wp_adm at 052317A8
    M  DpShMCreate: allocated tm_adm_list at 052334C8
    M  DpShMCreate: allocated tm_adm at 052334F0
    M  DpShMCreate: allocated wp_ca_adm at 05451438
    M  DpShMCreate: allocated appc_ca_adm at 05455A88
    M  DpShMCreate: allocated comm_adm_list at 054571F8
    M  DpShMCreate: allocated comm_adm at 05457210
    M  DpShMCreate: allocated vmc_adm_list at 05486010
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 05486038
    M  DpShMCreate: allocated wall_adm at 05486040
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 0 initializing ....
    X  Using implementation std
    M  <EsNT> Memory Reset enabled as NT default
    X  ES initialized.
    M M Fri Aug 31 16:09:37 2007
    M  calling db_connect ...
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'C:\usr\sap\I04\SYS\exe\run\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel   0
    C    patchno      26
    C    patchcomment MSSQL: GetNextMsst1 error (754819)
    C  np:(local) connection used on IDES
    C  Using Provider SQLNCLI
    C  Provider Release:9.00.1399.06
    C  Using Provider SQLNCLI
    C C Fri Aug 31 16:09:41 2007
    C  Cache sizes: header 52 bytes, 20000 names (26720000 bytes), 1000 dynamic statements (5432000 bytes), total 32152052 bytes
    C  Using shared procedure name cache IDES_I04I04_I04_MEM initialized by another process.
    C  Connected to db server : [IDES] server_used : [np:(local)], dbname: I04, dbuser: i04
    C  pn_id:IDES_I04I04_I04
    B  Connection 0 opened
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT MAX OPT Date     Time   DBHost         B  000 000 R/3              000000000 ACTIVE       NO  YES NO  255 255 20070831 160937 IDES           C  The IRow interface is supported by this OLEDB provider
    M  db_connect o.k.
    I I Fri Aug 31 16:09:53 2007
    I  MtxInit: 0 0 0
    M  SHM_PRES_BUF            (addr: 098E0040, size: 4400128)
    M  SHM_ROLL_AREA        (addr: 68200040, size: 160432128)
    M  SHM_PAGING_AREA        (addr: 09D20040, size: 72351744)
    M  SHM_ROLL_ADM            (addr: 0E230040, size: 1602056)
    M  SHM_PAGING_ADM        (addr: 0E3C0040, size: 525344)
    M  ThCreateNoBuffer        allocated 320144 bytes for 1000 entries at 0E450040
    M  ThCreateNoBuffer        index size: 3000 elems
    M  ThCreateVBAdm        allocated 7424 bytes (50 server) at 0E4A0040
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 0 initializing ....
    X  Using implementation std
    X  ES initialized.
    B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 9
    B  dbtbxbuf: Buffer TABL  (addr: 134C00C8, size: 30000128, end: 1515C4C8)
    B  dbtbxbuf: Buffer TABLP (addr: 0F3000C8, size: 10240000, end: 0FCC40C8)
    B  dbexpbuf: Buffer EIBUF (addr: 151600D0, size: 4194304, end: 155600D0)
    B  dbexpbuf: Buffer ESM   (addr: 155700D0, size: 4194304, end: 159700D0)
    B  dbexpbuf: Buffer CUA   (addr: 0FCE00D0, size: 3072000, end: 0FFCE0D0)
    B  dbexpbuf: Buffer OTR   (addr: 159800D0, size: 4194304, end: 15D800D0)
    M  rdisp/reinitialize_code_page -> 0
    M  icm/accept_remote_trace_level -> 0
    C C Fri Aug 31 16:09:54 2007
    C  Using Provider SQLNCLI
    C  The IRow interface is supported by this OLEDB provider
    S S Fri Aug 31 16:09:55 2007
    S  *** init spool environment
    S  initialize debug system
    T  Stack direction is downwards.
    T  debug control: prepare exclude for printer trace
    T  new memory block 15EFFBD0
    S  spool kernel/ddic check: Ok
    S  using table TSP02FX for frontend printing
    S  1 spool work process(es) found
    S  frontend print via spool service enabled
    S  printer list size is 150
    S  printer type list size is 50
    S  queue size (profile)   = 300
    S  hostspool list size = 3000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 1DF30098
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 1DF302C8
    S    using messages for server info
    S  size of spec char cache entry: 165020 bytes (timeout 100 sec)
    S  size of open spool request entry: 1152 bytes
    S  immediate print option for implicitely closed spool requests is disabled
    A A  -PXA--
    A  PXA INITIALIZATION
    A  PXA: Fragment Size too small: 195 MB, reducing # of fragments
    A  System page size: 4kb, admin_size: 11476kb.
    A  Attached to PXA (address 24550040, size 400000K)
    A  abap/pxa = shared protect gen_remote
    A  PXA INITIALIZATION FINISHED
    A  -PXA--
    A A A Fri Aug 31 16:09:56 2007
    A  ABAP ShmAdm attached (addr=56AF9000 leng=20955136 end=57EF5000)
    A  >> Shm MMADM area (addr=56E610E0 leng=134752 end=56E81F40)
    A  >> Shm MMDAT area (addr=56E82000 leng=17248256 end=57EF5000)
    A  RFC Destination> destination ides_I04_00 host ides system I04 systnr 0 (ides_I04_00)
    A  RFC Options> H=ides,S=00
    A  RFC FRFC> fallback activ but this is not a central instance.
    A   A  RFC rfc/signon_error_log = -1
    A  RFC rfc/dump_connection_info = 0
    A  RFC rfc/dump_client_info = 0
    A  RFC rfc/cp_convert/ignore_error = 1
    A  RFC rfc/cp_convert/conversion_char = 23
    A  RFC rfc/wan_compress/threshold = 251
    A  RFC rfc/recorder_pcs not set, use defaule value: 1
    A  RFC rfc/delta_trc_level not set, use default value: 0
    A  RFC rfc/no_uuid_check not set, use default value: 0
    A  RFC Method> initialize RemObjDriver for ABAP Objects
    A  Hotpackage version: 38
    M  ThrCreateShObjects        allocated 9394 bytes at 0FFD0040
    N  SsfSapSecin: putenv(SECUDIR=C:\usr\sap\I04\DVEBMGS00\sec): ok
    N N  =================================================
    N  === SSF INITIALIZATION:
    N  ===...SSF Security Toolkit name SAPSECULIB .
    N  ===...SSF trace level is 0 .
    N  ===...SSF library is C:\usr\sap\I04\SYS\exe\run\sapsecu.dll .
    N  ===...SSF hash algorithm is SHA1 .
    N  ===...SSF symmetric encryption algorithm is DES-CBC .
    N  ===...sucessfully completed.
    N  =================================================
    N  MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
    N  MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
    W  =================================================
    W  === ipl_Init() called
    W    ITSP Running against db release 620!
    W    ITSP Disable Kernel Web GUI functionality
    W  === ipl_Init() returns 2, ITSPE_DISABLED: Service is disabled (sapparam)
    W  =================================================
    B B Fri Aug 31 16:10:05 2007
    B  dbtran INFO (init_connection '<DEFAULT>' [MSSQL:640.00]):
    B   max_blocking_factor =  50,  max_in_blocking_factor      = 255,
    B   min_blocking_factor =   5,  min_in_blocking_factor      =  10,
    B   prefer_union_all    =   1,  prefer_union_for_select_all =   0,
    B   prefer_fix_blocking =   0,  prefer_in_itab_opt          =   0,
    B   convert AVG         =   1,  alias table FUPD            =   0,
    B   escape_as_literal   =   0,  opt GE LE to BETWEEN        =   0,
    B   select *            =0x00,  character encoding          =SBCS / []:X,
    B   use_hints           = abap->1, dbif->0x1, upto->0, rule_in->0,
    B                         rule_fae->0, concat_fae->0, concat_fae_or->0
    I I Fri Aug 31 16:10:10 2007
    I  MPI<c>9#3 Peak buffer usage: 5 (@ 64 KB)
    S  server @>SSRV:ides_I04_00@< appears or changes (state 1)
    S  server @>SSRV:ides_I04_00@< appears or changes (state 1)
    S  server @>SSRV:ides_I04_01@< appears or changes (state 1)
    E E Fri Aug 31 16:10:11 2007
    E  Replication is disabled
    N N Fri Aug 31 16:10:28 2007
    N  login/password_change_for_SSO : 1 -> 1
    B B Fri Aug 31 16:10:38 2007
    B  table logging switched off for all clients
    B B Fri Aug 31 16:10:41 2007
    B  dbmyclu : info : my major identification is 3232245831, minor one 0.
    B  dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.
    B  dbmyclu : info : my uuid is 96AAC2654435DC46AFA4C31629BE366F.
    B  dbmyclu : info : current optimistic cluster level: 3
    B  dbmyclu : info : pessimistic reads set to 2.
    S S Fri Aug 31 16:15:55 2007
    S  found spool memory service RSPO-ACTIONS at 1DF34B50
    M M Fri Aug 31 16:20:14 2007
    M  call semaphore clean-up function ...
    M  ***LOG Q0E=> DpSigGenHandler, Exception (c0000005) [dpnttool.c   462]
    M  -
    C-STACK -
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Application exception occurred:
    Exception : c0000005 (Access Violation)
    App       : disp+work.EXE (pid=1680)
    When      : 8/31/2007 16:20:14.837
    Threads   : 2
    Computer Name       : IDES
    User Name           : SAPServiceI04
    Number of Processors: 2
    Processor Type: x86 Family 15 Model 6 Stepping 4
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 9cc
    eax=00000000 ebx=00000000 ecx=00000014 edx=00000000 esi=003860ec edi=003860c0
    eip=7c82ed54 esp=0300daa8 ebp=0300dab8 iopl=0         nv up ei pl nz ac pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000212
    function : MmxFree2
           00f35dde 2b0568e59701  sub eax,[MmxUheaderSz (0197e568)] ds:0197e568=00000010
           00f35de4 50               push    eax
           00f35de5 68dd000000       push    0xdd
           00f35dea ffb4246c010000   push    dword ptr [esp+0x16c]  ss:0300dc14=7c82f9dd
           00f35df1 e890ac1200       call    memset (01060a86)
           00f35df6 83c40c           add     esp,0xc
           00f35df9 8b4308           mov     eax,[ebx+0x8]          ds:0300d006=2bf38b08
           00f35dfc 8bf3             mov     esi,ebx
           00f35dfe 2b730c           sub     esi,[ebx+0xc]          ds:0300d006=2444890c
           00f35e01 89442418         mov     [esp+0x18],eax         ss:0601aaaf=00000000
    FAULT-> 00f35e05 f60601           test    byte ptr [esi],0x1           ds:003860ec=08
           00f35e08 7513             jnz     MmxFree2+0x4cf (00f35e1d)
           00f35e0a 8bce             mov     ecx,esi
           00f35e0c e814a7ffff       call    MmxIBlockRemove (00f30525)
           00f35e11 8b4308           mov     eax,[ebx+0x8]          ds:0300d006=08460108
           00f35e14 014608           add     [esi+0x8],eax          ds:033930f2=00000000
           00f35e17 89742414         mov     [esp+0x14],esi         ss:0601aaaf=00000000
           00f35e1b 8bde             mov     ebx,esi
           00f35e1d 8b7308           mov     esi,[ebx+0x8]          ds:0300d006=f6f30308
           00f35e20 03f3             add     esi,ebx
           00f35e22 f60601           test    byte ptr [esi],0x1           ds:003860ec=08
           00f35e25 750d             jnz     MmxFree2+0x4e6 (00f35e34)
    --> Stack Back Trace <--
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    0300e648 00746014 3cc00548 3d07d010 06751220 00000000 disp+work!MmxFree2 [mmxx.c (2440)]
    0300e668 006450a7 00000000 00000001 3cc88e78 3cc485e8 disp+work!ab_sqlsclose [absapsql.c (8104)]
    0300e690 006466c6 00000013 00750af1 00000000 000000cd disp+work!ab_popbst [abstacks.c (4763)]
    0300e698 00750af1 00000000 000000cd 00000000 01c720fa disp+work!ab_poprsql [abstacks.c (1167)]
    0300e6cc 006e0f51 00000000 3d170778 00000000 00f00105 disp+work!ab_jsqls [absapsql.c (1306)]
    0300e770 00766be4 3d1715b3 3d170778 00000000 01afb3a4 disp+work!ab_extri [abextri.c (431)]
    0300e784 007ebf1c 00000000 7c36a42b 000004b6 00571b1a disp+work!ab_xevent [abrunt1.c (261)]
    0300e794 00571b1a 3d171080 0000002e 3d170778 3d17139a disp+work!ab_dstep [abdynpro.c (460)]
    0300e7bc 005740de 3d170778 3d170778 7c36a42b 00000000 disp+work!dynpmcal [dymainstp.c (2312)]
    0300e7d4 00573680 3d17139a 3d170778 00000003 0300fdcc disp+work!dynppai0 [dymainstp.c (1043)]
    0300e7f0 00549340 3d170778 00000002 00000001 00000000 disp+work!dynprctl [dymainstp.c (350)]
    0300fdcc 004747f4 00000002 0300fe74 00000001 00497626 disp+work!dynpen00 [dymain.c (1375)]
    0300fddc 00497626 00000002 00000000 003860a8 00000002 disp+work!Thdynpen00 [thxxhead.c (4353)]
    0300feec 004979e0 00000001 7ffd4000 00000000 00000000 disp+work!TskhLoop [thxxhead.c (4117)]
    0300ff04 00421d07 00000000 00000000 0300ff60 00401059 disp+work!tskhstart [thxxhead.c (1038)]
    0300ff14 00401059 00000003 003860a8 00000001 00000000 disp+work!DpMain [dpxxdisp.c (1009)]
    0300ff60 01060bcf 00000003 003860a8 003828f8 0152d000 disp+work!main [thxxanf.c (58)]
    0300ffc0 77e523e5 00000000 00000000 7ffd4000 80a56be3 disp+work!mainCRTStartup [crtexe.c (398)]
    0300fff0 00000000 01060a8c 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
    State Dump for Thread Id d2c
    eax=0000005e ebx=00000103 ecx=00000010 edx=000719bb esi=00000000 edi=00000000
    eip=7c82ed54 esp=04a1feb0 ebp=04a1fef4 iopl=0         nv up ei pl zr na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    function : KiFastSystemCallRet
           7c82ed54 c3               ret
           7c82ed55 8da42400000000   lea     esp,[esp]              ss:04a1feb0=7c821514
           7c82ed5c 8d642400         lea     esp,[esp]              ss:07a2ceb7=????????
    --> Stack Back Trace <--
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    04a1fef4 00fc37ec 000006ac 00000000 00000000 0038cd48 ntdll!KiFastSystemCallRet
    04a1ff84 7c349565 00000000 00000000 00000000 0038cbd0 disp+work!SigIMsgFunc [signt.c (559)]
    04a1ffb8 77e6608b 0038cbd0 00000000 00000000 0038cbd0 MSVCR71!endthreadex
    04a1ffec 00000000 7c3494f6 0038cbd0 00000000 00000000 kernel32!GetModuleFileNameA
    M  -
    M M Fri Aug 31 16:20:16 2007
    M  call clean-up function ...
    M  in_ThErrHandle: 1
    M  ThSigHandler: signal (step 4, th_errno 11, action 4)
    M M  Info for wp 0
    M M    stat = 4
    M    reqtype = 1
    M    act_reqtype = 1
    M    rq_info = 0
    M    tid = 9
    M    mode = 0
    M    len = 787
    M    rq_id = 423
    M    rq_source = 1
    M    last_tid = 9
    M    last_mode = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M M  Modeinfo for User T9/M0
    M M    tm state = 2
    M    uid = 13
    M    term type = 0x4
    M    display = 0x8
    M    cpic_no = 0
    M    cpic_idx = -1
    M    usr = >ABAP1       <
    M    terminal = >DDDC393             <
    M    client = >120<
    M    conversation_ID = >        <
    M    appc_tm_conv_idx = -1
    M    imode = 1
    M    mode state = 0x12
    M    task_type = ZTTADIA
    M    th_errno = 11
    M    rollout_reason = 1
    M    last_rollout_level = 7
    M    async_receives = 0
    M    cpic_receive = 0
    M    em handle = 0
    M    roll state = 4
    M    abap state = 4
    M    em state = 3
    M    eg state = 1
    M    spa state = 3
    M    enq state = 0
    M    next hook = T-1/U-1/M255
    M    master hook = T-1/U-1/M255
    M    slave hook = T-1/U-1/M255
    M    debug_tid = 255
    M    debug_mode = 0
    M    mode type = 0x1
    M    debug = 0
    M    tcode = >ME21N               <
    M    client conversation_ID = >        <
    M    server conversation_ID = >        <
    M    lock = 0
    M    max enq infos = 9
    M    act enq infos = 2
    M    em_hyper_hdl = 57F03BD8
    M    plugin_info = NULL
    M    act_plugin_hdl = -1
    M    act_plugin_no  = 0
    M    max_plugin_no  = 0
    M M  Adresse   Offset  Data from input buffer
    M  -
    M  054A7D70  000000  00000000 00000000 01502700 00000000 |.........P'.....|
    M  054A7D80  000016  00000000 0000009f 74100623 00170000 |........t..#....|
    M  054A7D90  000032  04880131 31363000 77696e64 6f77732d |...1160.windows-|
    M  054A7DA0  000048  31323532 00100409 00033731 3010041d |1252......710...|
    M  054A7DB0  000064  00013010 040f0004 000012ad 10041900 |..0.............|
    M  054A7DC0  000080  02000010 05010016 000d0000 000d002b |...............+|
    M  054A7DD0  000096  a1001fa2 00000000 00000000 0000100c |................|
    M  054A7DE0  000112  08001000 00029f00 00047400 00029f00 |..........t.....|
    M  054A7DF0  000128  00047410 0a010009 00000000 00000000 |..t.............|
    M  054A7E00  000144  00100a03 00090100 00000000 78001f10 |............x...|
    M  054A7E10  000160  0a030009 03000900 00007800 0a100a03 |..........x.....|
    M  054A7E20  000176  00090200 00000300 75000a10 0a030009 |........u.......|
    M  054A7E30  000192  01000000 00007500 0a100a05 00090100 |......u.........|
    M  054A7E40  000208  00000000 75000910 090e00c8 00c80000 |....u...........|
    M  054A7E50  000224  00000075 00090000 23000700 0200000c |...u....#.......|
    M  054A7E60  000240  01000000 00002300 82003c00 00000003 |......#...<.....|
    M  054A7E70  000256  00070000 00070000 00000000 00000000 |................|
    M  054A7E80  000272  00000000 00000000 00020005 00020002 |................|
    M  054A7E90  000288  000c0014 00110003 0001000a 000e0005 |................|
    M  054A7EA0  000304  00060003 000a000f 000c0008 000a000c |................|
    M  054A7EB0  000320  000c0008 00030003 0002000a 0005000a |................|
    M  054A7EC0  000336  0005000a 0005000a 00050005 00011100 |................|
    M  054A7ED0  000352  11001100 11001100 11001100 11001100 |................|
    M  054A7EE0  000368  11001100 11001100 11001100 11001100 |................|
    M  054A7EF0  000384  11001100 11001100 11001100 11001100 |................|
    M  054A7F00  000400  11001100 11001100 11001100 11001100 |................|
    M  054A7F10  000416  11001100 100c0200 18000000 07000000 |................|
    M  054A7F20  000432  23000000 07000000 00000000 00000000 |#...............|
    M  054A7F30  000448  00100909 00180001 00077920 20202020 |..........y     |
    M  054A7F40  000464  20202020 20202020 31303030 0000100a |        1000....|
    M  054A7F50  000480  01000900 00000000 00000000 100a0300 |................|
    M  054A7F60  000496  09010000 00000078 001f100a 03000902 |.......x........|
    M  -
    M M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server ides_I04_00 on host ides (wp 0)
    M  *  ERROR       ThSigHandler: signal
    M  *
    M  *  TIME        Fri Aug 31 16:20:16 2007
    M  *  RELEASE     640
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          11
    M  *  MODULE      thxxhead.c
    M  *  LINE        9555
    M  *  COUNTER     3
    M  *
    M  *****************************************************************************
    M M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_DUMP
    M  TrThHookFunc: called for WP dump
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  ThrSaveSPAFields: save spa fields
    M  Entering ThSetStatError
    C  SQLBREAK: DBSL_CMD_SQLBREAK: CbOnCancel was set. rc: 1 BREAK_REQUESTED
    M  ThIErrHandle: don't try rollback again
    M  ThIErrHandle: call ThrCoreInfo
    M  ThDelEnqInfo: del enq_own >20070831161118747000000000ides............................</1
    M  ThDelEnqInfo: act enq info: 1
    M  ThDelEnqInfo: del enq_own >20070831161118747000010000ides............................</2
    M  ThDelEnqInfo: act enq info: 0
    A  TH VERBOSE LEVEL FULL
    C Fri Aug 31 16:20:17 2007
    C  SQLBREAK: BREAK_REQUESTED upgraded to BREAK_IN_PROGRESS sloledb.cpp 4187
    M Fri Aug 31 16:20:18 2007
    M  SosSearchAnchor: search anchor for 4
    M  ThIErrHandle: Entering ThReplyToMsg
    M  ThIErrHandle: Entering ThErrHdlUser
    M  ThErrHdlUser: set th_errno (11)
    M  ThErrHdlUser: save context
    M  ThSaveContext: roll out
    M  ThRollOut: roll out T9/U13/M0 (level=7, short_roll_out=0)
    M  ThRollOut: call rrol_out (1)
    M  ThRollOut: act roll state = DP_ROLLED_OUT
    M  ThRollOut: roll level <> 0, don't call ab_rollout
    M  ThRollOut: full roll out of U13 M0 I1 (Level 7) ok
    M  ThCheckEmMagic: check em magic at 3CC00A80 for T9/M0/I1
    M  ThCheckEmMagic: em magic at 3CC00A80 for T9/M0/I1 o.k.
    M  ThEmContextDetach2: detach T9/M0 from em memory (em_hdl=0, force=0)
    M  ThEmContextDetach2: reset local em info
    B  Disconnecting from ALL connections:
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT MAX OPT Date     Time   DBHost         B  000 000 R/3              000000000 ACTIVE       YES YES NO  255 255 20070831 160937 IDES           C  Rollback Work (0)
    B  Disconnected from connection 0
    B  statistics db_con_commit (com_total=149, com_tx=34)
    B  statistics db_con_rollback (roll_total=1, roll_tx=0)
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 1680) [dpnttool.c   357]
    M  return from clean-up function ...
    trc file: "dev_w0", trc level: 1, release: "640"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, M
    B B Fri Aug 31 16:20:36 2007
    B  create_con (con_name=R/3)
    B  Loading DB library 'C:\usr\sap\I04\SYS\exe\run\dbmssslib.dll' ...
    B  Library 'C:\usr\sap\I04\SYS\exe\run\dbmssslib.dll' loaded
    B  Version of 'C:\usr\sap\I04\SYS\exe\run\dbmssslib.dll' is "640.00", patchlevel (0.26)
    B  New connection 0 created
    M systemid   560 (PC with Windows NT)
    M relno      6400
    M patchlevel 0
    M patchno    25
    M intno      20020600
    M make:      multithreaded, ASCII
    M pid        2460
    M
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2460) [dpxxdisp.c   1160]
    I  MtxInit: -2 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: JAVA is not active
    M  DpShMCreate: sizeof(wp_adm)        7456    (828)
    M  DpShMCreate: sizeof(tm_adm)        2219848    (11044)
    M  DpShMCreate: sizeof(wp_ca_adm)        18000    (60)
    M  DpShMCreate: sizeof(appc_ca_adm)    6000    (60)
    M  DpShMCreate: sizeof(comm_adm)        192000    (384)
    M  DpShMCreate: sizeof(vmc_adm)        0    (320)
    M  DpShMCreate: sizeof(wall_adm)        (22440/34344/56/100)
    M  DpShMCreate: SHM_DP_ADM_KEY        (addr: 05230040, size: 2506248)
    M  DpShMCreate: allocated sys_adm at 05230040
    M  DpShMCreate: allocated wp_adm at 052317A8
    M  DpShMCreate: allocated tm_adm_list at 052334C8
    M  DpShMCreate: allocated tm_adm at 052334F0
    M  DpShMCreate: allocated wp_ca_adm at 05451438
    M  DpShMCreate: allocated appc_ca_adm at 05455A88
    M  DpShMCreate: allocated comm_adm_list at 054571F8
    M  DpShMCreate: allocated comm_adm at 05457210
    M  DpShMCreate: allocated vmc_adm_list at 05486010
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 05486038
    M  DpShMCreate: allocated wall_adm at 05486040
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 0 initializing ....
    X  Using implementation std
    M  <EsNT> Memory Reset enabled as NT default
    X  ES initialized.
    M M Fri Aug 31 16:20:37 2007
    M  calling db_connect ...
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'C:\usr\sap\I04\SYS\exe\run\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel   0
    C    patchno      26
    C    patchcomment MSSQL: GetNextMsst1 error (754819)
    C  np:(local) connection used on IDES
    C  Using Provider SQLNCLI
    C  Provider Release:9.00.1399.06
    C C Fri Aug 31 16:20:38 2007
    C  Using Provider SQLNCLI
    C  Cache sizes: header 52 bytes, 20000 names (26720000 bytes), 1000 dynamic statements (5432000 bytes), total 32152052 bytes
    C  Using shared procedure name cache IDES_I04I04_I04_MEM initialized by another process.
    C  Connected to db server : [IDES] server_used : [np:(local)], dbname: I04, dbuser: i04
    C  pn_id:IDES_I04I04_I04
    B  Connection 0 opened
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT MAX OPT Date     Time   DBHost         B  000 000 R/3              000000000 ACTIVE       NO  YES NO  255 255 20070831 162037 IDES           C  The IRow interface is supported by this OLEDB provider
    M  db_connect o.k.
    I  MtxInit: 0 0 0
    M  SHM_PRES_BUF            (addr: 098E0040, size: 4400128)
    M  SHM_ROLL_AREA        (addr: 68200040, size: 160432128)
    M  SHM_PAGING_AREA        (addr: 09D20040, size: 72351744)
    M  SHM_ROLL_ADM            (addr: 0E230040, size: 1602056)
    M  SHM_PAGING_ADM        (addr: 0E3C0040, size: 525344)
    M  ThCreateNoBuffer        allocated 320144 bytes for 1000 entries at 0E450040
    M  ThCreateNoBuffer        index size: 3000 elems
    M  ThCreateVBAdm        allocated 7424 bytes (50 server) at 0E4A0040
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 0 initializing ....
    X  Using implementation std
    X  ES initialized.
    B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 9
    B  dbtbxbuf: Buffer TABL  (addr: 134C00C8, size: 30000128, end: 1515C4C8)
    B  dbtbxbuf: Buffer TABLP (addr: 0F3000C8, size: 10240000, end: 0FCC40C8)
    B  dbexpbuf: Buffer EIBUF (addr: 151600D0, size: 4194304, end: 155600D0)
    B  dbexpbuf: Buffer ESM   (addr: 155700D0, size: 4194304, end: 159700D0)
    B  dbexpbuf: Buffer CUA   (addr: 0FCE00D0, size: 3072000, end: 0FFCE0D0)
    B  dbexpbuf: Buffer OTR   (addr: 159800D0, size: 4194304, end: 15D800D0)
    M  rdisp/reinitialize_code_page -> 0
    M  icm/accept_remote_trace_level -> 0
    C  Using Provider SQLNCLI
    S  *** init spool environment
    S  initialize debug system
    T  Stack direction is downwards.
    T  debug control: prepare exclude for printer trace
    T  new memory block 15EF7370
    S  spool kernel/ddic check: Ok
    S  using table TSP02FX for frontend printing
    S  1 spool work process(es) found
    S  frontend print via spool service enabled
    S  printer list size is 150
    S  printer type list size is 50
    S  queue size (profile)   = 300
    S  hostspool list size = 3000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 1DEF0098
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 1DEF02C8
    S    using messages for server info
    S  size of spec char cache entry: 165020 bytes (timeout 100 sec)
    S  size of open spool request entry: 1152 bytes
    S  immediate print option for implicitely closed spool requests is disabled
    A A  -PXA--
    A  PXA INITIALIZATION
    A  PXA: Fragment Size too small: 195 MB, reducing # of fragments
    A  System page size: 4kb, admin_size: 11476kb.
    A  Attached to PXA (address 24550040, size 400000K)
    A  abap/pxa = shared protect gen_remote
    A  PXA INITIALIZATION FINISHED
    A  -PXA--
    A A  ABAP ShmAdm attached (addr=56AF9000 leng=20955136 end=57EF5000)
    A  >> Shm MMADM area (addr=56E610E0 leng=134752 end=56E81F40)
    A  >> Shm MMDAT area (addr=56E82000 leng=17248256 end=57EF5000)
    A  RFC Destination> destination ides_I04_00 host ides system I04 systnr 0 (ides_I04_00)
    A  RFC Options> H=ides,S=00
    A  RFC FRFC> fallback activ but this is not a central instance.
    A   A  RFC rfc/signon_error_log = -1
    A  RFC rfc/dump_connection_info = 0
    A  RFC rfc/dump_client_info = 0
    A  RFC rfc/cp_convert/ignore_error = 1
    A  RFC rfc/cp_convert/conversion_char = 23
    A  RFC rfc/wan_compress/threshold = 251
    A  RFC rfc/recorder_pcs not set, use defaule value: 1
    A  RFC rfc/delta_trc_level not set, use default value: 0
    A  RFC rfc/no_uuid_check not set, use default value: 0
    A  RFC Method> initialize RemObjDriver for ABAP Objects
    A  Hotpackage version: 38
    M  ThrCreateShObjects        allocated 9394 bytes at 0FFD0040
    N  SsfSapSecin: putenv(SECUDIR=C:\usr\sap\I04\DVEBMGS00\sec): ok
    N N  =================================================
    N  === SSF INITIALIZATION:
    N  ===...SSF Security Toolkit name SAPSECULIB .
    N  ===...SSF trace level is 0 .
    N  ===...SSF library is C:\usr\sap\I04\SYS\exe\run\sapsecu.dll .
    N  ===...SSF hash algorithm is SHA1 .
    N  ===...SSF symmetric encryption algorithm is DES-CBC .
    N  ===...sucessfully completed.
    N  =================================================
    N  MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
    N  MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
    W  =================================================
    W  === ipl_Init() called
    W    ITSP Running against db release 620!
    W    ITSP Disable Kernel Web GUI functionality
    W  === ipl_Init() returns 2, ITSPE_DISABLED: Service is disabled (sapparam)
    W  =================================================
    M  ThCheckPrevUser: clean previous user T9/U13/M0
    M M  Modeinfo for User T9/M0
    M M    tm state = 2
    M    uid = 13
    M    term type = 0x4
    M    display = 0x8
    M    cpic_no = 0
    M    cpic_idx = -1
    M    usr = >ABAP1       <
    M    terminal = >DDDC393             <
    M    client = >120<
    M    conversation_ID = >        <
    M    appc_tm_conv_idx = -1
    M    imode = 1
    M    mode state = 0x12
    M    task_type = ZTTADIA
    M    th_errno = 11
    M    rollout_reason = 1
    M    last_rollout_level = 7
    M    async_receives = 0
    M    cpic_receive = 0
    M    em handle = 0
    M    roll state = 3
    M    abap state = 3
    M    em state = 2
    M    eg state = 1
    M    spa state = 3
    M    enq state = 0
    M    next hook = T-1/U-1/M255
    M    master hook = T-1/U-1/M255
    M    slave hook = T-1/U-1/M255
    M    debug_tid = 255
    M    debug_mode = 0
    M    mode type = 0x1
    M    debug = 0
    M    tcode = >ME21N               <
    M    client conversation_ID = >        <
    M    server conversation_ID = >        <
    M    lock = 0
    M    max enq infos = 9
    M    act enq infos = 0
    M    em_hyper_hdl = 57F03BD8
    M    plugin_info = NULL
    M    act_plugin_hdl = -1
    M    act_plugin_no  = 0
    M    max_plugin_no  = 0
    M C  The IRow interface is supported by this OLEDB provider
    M  ***LOG R47=> ThResFree, delete (001023) [thxxmode.c   1283]

    I Got the same problem but at that time i have installed GUI of lower version. WHen i have upgraded the GUI it worked fine. Better you check once the SAPGUI configuration.

  • Portal Runtime Error while accessing BW reports through portal

    Hi,
    We are facing portal runtime error(An exception occurred while processing your request. Please send the exception id to your portal administrator) while accessing BI reports through portal frequently.
    We are unable to trace the error in the 'default trace' log file and although refreshing the cache solves this issue, it is difficult to explain this to every user individually.
    After many such errors, We found one log entry, which we are now not yet sure if it is relevant. The error states:
    1.
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;&lt;BWLauncherComponent[PORTAL_URL]&gt;;jsessionid=&lt;Request.JSessionID&gt;?sap-ext-sid=&lt;ID[url_ENCODE]&gt;&amp;Language=&lt;Request.Language&gt;&amp;theme=&lt;LAF.Theme[url_ENCODE]&gt;&amp;sap-lafversions=&lt;LAF.AllVersions[url_ENCODE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;Report&gt;&amp;&lt;BusinessParameters&gt;&#39;; the problem occured at position 230. Cannot process expression &lt;LAF.AllVersions&gt;
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:540)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Content pass of Application Integrator failed.
    Component Name:       'com.sap.portal.appintegrator.sap.BWReport',
    Context Name (iView):  <iview name location>
    Top Layer:            'BWReport/TopLayer',
    Producer ID (FPN):    'null',
    System Alias:         'Sap_bw',
    2.
    The cluster server element 111111 is not added in the EP cluster context,
       because prtbridge on 111111 is stopped  or not yet started (maybe the server is starting or shuting down).
    Please suggest us if the above logs are related to the issue or not
    Kindly provide us any inputs or solutions.

    Hi All,
    We are also having similiar type of error in our portal. 
    com.sap.engine.services.prtbridge##com.sap.engine.services.prtbridge
    #######SAPEngine_System_Thread[impl:5]_13##0#0#Error#1#/System/Server#Plain###
    The cluster server element 125898350 is not added in the EP cluster context,
       because prtbridge on 125898350 is stopped  or not yet started
    (maybe the server is starting or shuting down).
    We have implemented the FPN using RRA.
    This error comes only for few users when they navigate in Portal. After clearing the cache, it works for all. Kindly help us to resolve this issue.
    Regards,
    Venkatesh

  • Error while accessing ESS Loan Request.

    Hi Experts,
    While accessing ESS Loan request for Country grouping 40 India am getting below mentioned error saying that 500 Internal Server Error.
    I have maintained the settings for Leave request and maintained Infotype 45 Loans for employee.
    But it is giving the below mentioned error.
    500   Internal Server Error
      SAP NetWeaver Application Server 7.00/Java AS 7.00 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
        at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
        at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
        at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
        at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
        at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
        ... 74 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
    Version null
    DOM version null
    Client Type msie8
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:28:44[UTC], changelist=91834, host=pwdfm256), build date: Fri Feb 11 16:31:03 IST 2011
    J2EE Engine 7.02 PatchLevel 91789.
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_28-b03, vendor: Sun Microsystems Inc.
    Operating system Windows Server 2008 R2, version: 6.1, architecture: amd64
    Session & Other
    Session Locale en_US
    Time of Failure Fri Feb 18 11:17:24 IST 2011 (Java Time: 1298008044828)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:36[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:40[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0205.20100813133737.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:08:53[UTC], changelist=91781, host=PWDFM256.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:53[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
    SapMetamodelCommon 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:28[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
    SapMetamodelCore 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:25[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
    SapMetamodelDictionary 7.0205.20100813133729.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:16:20[UTC], changelist=91777, host=PWDFM256.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0205.20100813133929.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:20:37[UTC], changelist=91833, host=PWDFM256.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
    SapWebDynproGenerationCore 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:57[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.model.loan.types.Extdl could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:268)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:231)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:761)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
         at com.sap.ess.in.loan.overview.VcOverviewESS.onInit(VcOverviewESS.java:244)
         at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESS.onInit(InternalVcOverviewESS.java:611)
         at com.sap.ess.in.loan.overview.VcOverviewESSInterface.onInit(VcOverviewESSInterface.java:162)
         at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface.onInit(InternalVcOverviewESSInterface.java:144)
         at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface$External.onInit(InternalVcOverviewESSInterface.java:220)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:876)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1355)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:357)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:597)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:870)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
         at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
         at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
         at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
         at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:260)
         ... 72 more
    Please suggest me the solution for this.
    Regards,
    Ksanj.

    Please   check that the ESS/ERP packages fit together according to
    the page
    https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACK+
    MISMATCH+ISSUES
    Please check again the componentinfo and the SPlevels of the testlandsca
    pe, that the same level is used on the prod landscape.
    So ensure you are on correct levels!

  • LDAP users Faicng Error While Accessing the ESS Iviews in Portal

    Hi,
    My Portal is SAP EP 7.0 SP20 And ECC 6.0 SP16.
    UME users able to access the ESS MSS Iviews.But only one LDAP User only access ESS/MSS Iviews Other getting the Below error.
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.     
    Please contact your system administrator     
    Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE     
    Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE:
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
                    at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit(ModelHandler.java:205)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:428)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber(FcXssMenu.java:570)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:292)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:455)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:165)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:389)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:546)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
                    at com.sap.pcuigp.xssutils.navi.FcNavigation.onInit(FcNavigation.java:314)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.onInit(InternalFcNavigation.java:358)
                    at com.sap.pcuigp.xssutils.navi.FcNavigationInterface.onInit(FcNavigationInterface.java:145)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.onInit(InternalFcNavigationInterface.java:142)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.onInit(InternalFcNavigationInterface.java:278)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
                    at com.sap.pcuigp.xssutils.roadmap.VcRoadmap.onInit(VcRoadmap.java:188)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmap.onInit(InternalVcRoadmap.java:162)
                    at com.sap.pcuigp.xssutils.roadmap.VcRoadmapInterface.onInit(VcRoadmapInterface.java:153)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface.onInit(InternalVcRoadmapInterface.java:144)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface$External.onInit(InternalVcRoadmapInterface.java:220)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
                    at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
                    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
                    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
                    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
                    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
                    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:782)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
                    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
                    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
                    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
                    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
                    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
                    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
                    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
                    at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
                    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
                    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
                    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
                    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
                    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
                    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:782)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
                    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
                    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
                    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
                    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
                    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
                    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
                    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
                    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                    at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
                    at com.sap.pcuigp.xssutils.xssmenu.model.MenuModel.hrxss_Ser_Getmenudata(MenuModel.java:171)
                    at com.sap.pcuigp.xssutils.xssmenu.model.Hrxss_Ser_Getmenudata_Input.doExecute(Hrxss_Ser_Getmenudata_Input.java:137)
                    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
                    ... 76 more
    Thanks & Regrads,
    Subba Rao

    Hi,
    Now every user facing the same error while accessing ESS Iviews from Portal.
    in ST22 Dump is created.
    What happened?                                                                                |
    Error in the ABAP Application Program
    The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "CL_XSS_CAT_BUFFER=============CP " in include
    "CL_XSS_CAT_BUFFER=============CM00C " in
    line 50:
    ""L_CATSDB" and "L_CATSDBCOMM" are not mutually convertible. In Unicode"
    " programs, "L_CATSDB" must have the same structure layout as "L_CATSDB"
    "COMM", independent of the length of a Unicode character."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
    terminated because it has
    |    come across a statement that unfortunately cannot be executed.
    What we need to resolve the above issue.
    Thanks & Regards,
    Subba Rao

  • ABAP Dump issue while accessing Gateway

    Hi
    We have recently upgraded our Gateway server to SP03. Eversince after service generation while accessing the XML/Metadata from the consumption page we get an HTTP error with Dump. Has anyone faced this problem before.
      <?xml version="1.0" encoding="utf-8" ?>
    - <error xmlns:xsi="http://www.w3.org/2001/XMLSchema-Instance">
      <code>HTTP/500/E/Internal Server Error</code>
      <message>Call of service /sap/opu/sdata/sap/Z14335_RFC_BP_1/ terminated because of an error. The following error text was processed in system AC1 : Syntax error in program /IWCOR/CL_REST_HTTP_HANDLER===CP .The error occurred on the application server njsapnet3. The termination type was: RABAX_STATE.If the termination type is RABAX_STATE, you will find more information on the cause of termination in system AC1 in transaction ST22. If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server njsapnet3 in transaction SM21. If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process in transaction ST11 on the application server njsapnet3. You may also need to analyze the trace files of other work processes. If you do not yet have a user ID, contact your system adminmistrator.</message>
      </error>

    Hi All,
    I am also facing the same issue.
    When i am executing query/read operation my service it will works properly and getting data also,but when i am trying get X-CSRF token it throws error(ABAP Dump) .Can you please help me out this issue.
    Based on the Tx: ST11..getting below log.
    A  ABAP Program /IWCOR/CL_REST_HTTP_HANDLER===CP        .
    A  Source /IWCOR/CL_REST_HTTP_HANDLER===CCIMP      Line 40.
    A  Error Code ASSERTION_FAILED.
    A  Module abassert.c.
    A  Function ab_aabAssertionFailedRabax Line 1880.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    N
    N Thu Jan 03 15:00:58 2013
    N  *** ERROR => System ID and client from ticket are not the same than mine. [ssoxxkrn.c   1065]
    N  {root-id=0050569E07B31ED295B108EAC1527575}_{conn-id=0050569E07B31ED295B108EABC707575}_1
    N  *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL (see note 1055856). [ssoxxkrn.c   1071]
    N  {root-id=0050569E07B31ED295B108EAC1527575}_{conn-id=0050569E07B31ED295B108EABC707575}_1
    i am getting based on Tx:ST22
    Category          
    ABAP Programming Error
    Runtime Errors    
    ASSERTION_FAILED
    ABAP Program      
    /IWCOR/CL_REST_HTTP_HANDLER===CP
    Application Component  OPU-FND-CCL
    Note: I am using SAP NW-GW-SP04
    Thanks,
    Syam

  • Session terminated

    Hi all ,
          In my application server 4.7ee the session is been terminated while creating a purchase order . I am getting a dump error , I had pasted the dump analysis here:
    Process terminated by signal 0.
    What happened?
    The current ABAP program had to be terminated because the
    ABAP processor detected an internal system error.
    The current ABAP program "SAPLCLSC" had to be terminated because the ABAP
    processor discovered an invalid system state.
    What can you do?
    Make a note of the actions and input which 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
    An SAP System process was terminated by an operating system signal.
    Possible reasons for this are:
    1. Internal SAP System error.
    2. Process was terminated externally (by the system administrator).
               Last error logged in SAP kernel     
    Component............ "Taskhandler"
    Place................ "SAP-Server ides01_I05_00 on host ides01 (wp 1)"
    Version.............. 1
    Error code........... 11
    Error text........... "ThSigHandler: signal"
    Description.......... " "
    System call.......... " "
    Module............... "thxxhead.c"
    Line................. 9555
    How to correct the error
    The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
    contains a file called 'core'.
    Save this file under another name.
    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....... "ides01"
    Network address.......... "172.16.0.176"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "Intel 801586 (M"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 1
    Short dump setting....... "full"
    Database server.......... "IDES01"
    Database type............ "MSSQL"
    Database name............ "I05"
    Database owner........... "i05"
    Character set............ "English_United State"
    SAP kernel............... "640"
    Created on............... "Jul 14 2004 23:11:01"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "SQL_Server_8.00 "
    Patch level.............. "26"
    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"
    User, transaction...
    Client.............. 800
    User................ "SAPUSER"
    Language key........ "E"
    Transaction......... "ME21N "
    Program............. "SAPLCLSC"
    Screen.............. "SAPLMEGUI 0014"
    Screen line......... 22
    Information on where termination occurred
    The termination occurred in the ABAP program "SAPLCLSC" in "EXECUTE_SELECT".
    The main program was "RM_MEPO_GUI ".
    The termination occurred in line 131 of the source code of the (Include)
    program "LCLSCF2G"
    of the source code of program "LCLSCF2G" (when calling the editor 1310).
    What are the steps i need to do .
    Kindly help me .
    Regards,
    Rakesh

    Hi Rakesh,
    it is in
    -> http://service.sap.com/swdc
    -> (left side) download ->support packages and patches
    -> entry by application group
    ->Support Packages and Patches
    ->  SAP NetWeaver" SAP NETWEAVER" SAP NETWEAVER 04" Entry by Component" Application Server ABAP
    -> choose 32 bit or 64 bit and unicode / non-unicode then your OS and DB
    -> pls note there is one database independend part and database dependend
        part
    The latest kernel patch level for 6.40 is 221.
    Kind regards,
    andraes

Maybe you are looking for