FAQ Wiki
Page tree
Skip to end of metadata
Go to start of metadata

Symptom:

Would like to know whether an issue is reproducible with latest kernel patch, or if it is already fixed in the latest kernel patch or not. In many cases it is NOT possible to update/upgrade the kernel of a NetWeaver AS to the latest available patch , due to certain reasons (i.e. because it is a productive system or a system used by many developers). [Let's call this system " target system ".] Very often application related data is missing from an updated test system (sandbox system). The below steps are helpful if an issue can be reproduced when calling webgui directly . This is one of the most useful troubleshooting tools from ITS perspective.

This page is part of:

ITS Troubleshooting Guide

Tiny link (useful for e-mail):

https://wiki.scn.sap.com/wiki/x/VIB9Gg


  1. Update one of your test or sandbox systems to the newest kernel patch level. [Let's call this system "source system".]
    If you cannot update the complete kernel, it is enough to update the ITS related part of the kernel using the sapwebgui*.sar file
    as described in SAP Note 2412840 (Kernel Patch SAPWEBGUI.SAR) and KBA 2221289 (How to install package sapwebgui).
    (Pay attention to the exceptions listed in SAP Note 2859811 (SAPWEBGUI.SAR incompatibilities).


  2. Logon to the source system directly via WebGUI and start transaction SRFCCONN  from the source system where the newest kernel patch is used.

    (Make sure you use a user with RFC authorization.)


  3. Enter the 'Transaction Code' (in this example "SU01") you would like to test in the target system (where the issue reproducible) and the server name of the target system:

  4. In order to have the server name of the target system:
     Log into the target system via 'SAP GUI for Windows' and click on the Menu → System → Status... → Server Name.
    (This can also be identified by using transaction SM51 in the target system.)

  5. Click on execute in transaction SRFCCONN → the logon screen of the target system will appear

  6. Add the logon data for the target system and try to reproduce the same scenario with the kernel patch level which is used in the source system.



  • No labels