Search This Blog

Wednesday, April 2, 2014

SAP Note 1378659 - NWBC known issues & what to check when opening a ticket


Symptom
Known issues of Netweaver Business Client >=3.0 (NWBC) and what to check when you open a support ticket on BC-FES-BUS*

Other Terms
accelerated ticket processing

Reason and Prerequisites
Incomplete error description
Be aware that most of the mentioned "errors" are not really a software bug (support) but missing/wrong configuration (consulting).
Based on our support experience we still mention them in here in order to give you a chance to correct this quickly.
But bear in mind that this does not automatically qualify it to a support case <->ticket.

We added well issus which are caused/miss configured outside of NWBC (does not indicate any responsibility of NWBC itself).

Solution
BEFORE A TICKET IS OPEND:

Try to reproduce with the most current Patch Level of your client version:
NWBC CLIENT versions:
  • download links:
  • NWBC 4.0 Desktop version:
    http://goo.gl/saiyA
  • NWBC 3.5 Desktop version:
    http://goo.gl/9dfVv
  • NWBC 3.0 Desktop version:
    http://goo.gl/oJlzl
  • NWBC HTML version:
    -not relevant since all server side-
  • patch level descriptions:
  • NWBC 4.0 Desktop version:
    https://service.sap.com/sap/support/notes/1707626
  • NWBC 3.5 Desktop version:
    https://service.sap.com/sap/support/notes/1559188
  • NWBC 3.0 Desktop version:
    https://service.sap.com/sap/support/notes/1353593
  • NWBC HTML version:
    -not relevant since all server side-
  • what´s new with NWBC 4.0:
  • http://youtu.be/V9dFB9qsYIo
  • http://goo.gl/7VoNc
  • http://goo.gl/5CcgS
  • general NWBC information:
  • Introduction to NWBC:
    http://www.youtube.com/watch?v=AAQRzKbNa1s
  • NWBC community on SCN:
    http://scn.sap.com/community/netweaver-business-client
  • FAQ:
    https://service.sap.com/sap/support/notes/900000
NWBC SERVER side (runtime based on SAP_BASIS):
  • check note 1353538
  • apply the highest patch mentioned in there
  • you can´t apply any of those?
  • or you run against the portal - ABAP patches are not applicable.

Background information:
  • After that you will have the most current NWBC runtime available and you don´t have to read further in this sub chapter:

    especially important to update your NWBC runtime if:
  • your problem/fix is already mentioned in note 1353538
  • you run on a rather old NWBC runtime-

    check your current runtime patch level (PL) according to
    https://service.sap.com/sap/support/notes/1864151
    and compare the notes (PL) with the ones mentioned in note 1353538

    if your runtime PL is lower than: current PL (see note 1353538) minus 2 -> apply the highest PL mentioned in note 1353538 in order to get to a current NWBC runtime.
Does the error occur as well without NWBC?
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/5b14a697817513e10000000a42189b/content.htm?frameset=/en/66/48a793bc2f4ec5bdb8e7e93ea6cd9f/frameset.htm
  • For instance if you have integrated:
  • the portal:
    Does the same error occur already if you call the Portal directly/standalone (without NWBC on top)?
  • sap gui transactions:
    Does the same error occur already if you call the sap gui transaction in the classical sap gui/directly/standalone (without NWBC on top)?
Hint:
NWBC as a top layer will not fix problems which do occur already on lower layers
  • quick test:
  • http://goo.gl/aNfsr
  • if the problem occurs in the standalone case (without NWBC) as well -> open the ticket on the respective application component.


WHEN OPENING A TICKET:


Attach:
  • Traces type 2:
  • https://service.sap.com/sap/support/notes/1883689
    you might be requested later for other trace types
  • Reproduction description:
  • Screenshots/navigation/click path
  • SID/CLIENT/URLs
  • in case of NWBC DESKTOP:
  • which NWBC version you are using including Patch Level (PL)
  • retest with the most current PL (download links - see at the beginning of this note)
  • does the same issue occure as well in NWBC for html (browser only).


error numbers:
compare with trace type 1 or 4 from: https://service.sap.com/sap/support/notes/1883689

403 (Forbidden) error:
  • Most probably the appropriate SICF service has not been activated (troubleshoot with note 1883689 type 1 OR 4)
  • an example how to activate a SICF node:
    note 1109215 (application dependent)
404 file not found (mimes/images are not displayed) - or looping at login
  • often ITS / web gui related
  • test a plain/standalone (no nwbc involved) webgui based transaction -> same/similar problems there?
  • verify https://service.sap.com/sap/support/notes/1308846
  • still 404's ? check note 808347 and/or open ticket on BC-FES-ITS
500 error in the client:
  • ITS / web gui related?:
    open a ticket on BC-FES-ITS
  • RABAX:
    UNCAUGHT_EXCEPTION CX_FQDN / An exception occurred that was not caught.
    make sure fully qualified domain names are used: https://service.sap.com/sap/support/notes/654982 &https://service.sap.com/sap/support/notes/773830


NWBC on WTS/Citrix:
NWBC 3.0:
  • Installation:
  • use >=PL6 of NWBC 3.0
    http://goo.gl/oJlzl
    PL description: note 1353593
  • Missing Taskbar Buttons:
  • https://service.sap.com/~sapidb/012003146900000583532011E/Taskbar_Buttons_missing.pdf

NWBC 3.5:
  • second login required (not occurring in non citrix environment).
  • use >=PL4 of NWBC 3.5:
    http://goo.gl/9dfVv
    PL description: note 1559188
SSO or Login related errors:
SSO2 configuration is MANDATORY for NWBC usage
Error:
  • popup on the frontend:
  • EN: 
    "SSO logon not possible; logon tickets not activated on the server"   OR:

    "SSO logon not possible; no logon ticket due to incorrect configuration"  OR:

    "SSO logon not possible; browser logon ticket cannot be accepted"   OR:

    "Please check your configuration of the SAP Logontickets (MYSAPSSO2-Cookie)
  • DE: 
    "SSO-Anmeldung nicht möglich: Anmeldetickets nicht auf Server aktiviert"   ODER:

    "SSO-Anmeldung nicht möglich: Kein Anmeldeticket wegen fehlerhafter Konfig"   ODER:

    "SSO-Anmeldung nicht möglich: Browser-Anmeldeticket wird nicht aktzeptiert"  ODER:

    "Prüfen Sie Ihre Konfiguration des SAP-Anmeldetickets (MYSAPSSO2-Cookie)
  • the following log entries in NWBC DESKTOP traces indicate the same problem:
  • C:\Users\<user name>\AppData\Local\SAP\NWBC\Traces\NWWBCTrace.log
    "MYSAPSSO2 cookie missing after logon"

What to do:
  • Please read chapters "NWBC and Authentication" and "Logon Tickets" of the NWBC documentation where we explain some background information about the absoutely necessary MYSAPSSO2 cookie. (http://goo.gl/ngM7b)
    To check whether HTTP requests contain the MYSAPSSO2 cookie you can use e.g. Fiddler as an HTTP sniffer (note 1883689).
  • above SSO errors do indicate an incomplete / incorrect (server side) sso configuration (consulting):
  • https://service.sap.com/sap/support/notes/817529
  • https://service.sap.com/sap/support/notes/1055856


Further SSO related configurations/errors:
  • error displayed:
    "the system is unable to interpret the sso ticket received"
  • https://service.sap.com/sap/support/notes/701205
  • open a ticket on BC-SEC-LGN
  • troubleshoot SSO:
  • check whether the user is a "DIALOG" user - service and system users never get SSO tickets (https://service.sap.com/sap/support/notes/622464 for more details)
  • https://service.sap.com/sap/support/notes/1257108
  • https://service.sap.com/sap/support/notes/1638715
  • open a ticket on BC-SEC-LGN
  • integrated SAP GUI -when SNC transport layer encryption is active- SSO does not work at all (permanently prompting for user/password):
  • https://service.sap.com/sap/support/notes/1690531
HTTPS/SSL & client certificates are in place:
some of the clients can´t login the following is displayed (popup) & traced in type 2 of:
https://service.sap.com/sap/support/notes/1883689
  • error code: 0x80090326 and/or the following error text:
  • EN: The message received was unexpected or badly formatted
  • DE: Das Format der empfangenen Nachricht war unerwartet oder fehlerhaft
                    caused outside of SAP-code: check relation to http://support.microsoft.com/kb/933430/en-us for verification you can open a ticket on BC-SEC-SSL

Warning@Login:
switch to https:
  • EN: No switch to HTTPS occurred, so it is not secure to send a password
  • DE: Es erfolgte kein Umschalten auf HTTPS, Kennwort senden ist daher unsicher
  • https://service.sap.com/~sapidb/012006153200000000422012E/SSLsetup.pdf
    (Document eventually as well helpful in case you have load balancers / web dispatcher in place).

multiple login warning:
  • EN: ' you are already logged on to the system in the following sessions '
  • EN: ' Sie sind im System bereits mit folgenden Sessions angemeldet '
  • https://service.sap.com/~sapidb/012006153200001041092013E/you_are_already_logged_on.pdf
Security Warning:
  • EN:
  • SAP Netweaver Business Client has identified a potential security concern.
    (This location is not explicitly marked as safe/whitlisted)
  • DE:
  • SAP Netweaver Business Client hat ein mögliches Sicherheitsrisiko entdeckt.
    or
  • SAP Netweaver Business Client hat ein potentielles Sicherheitsrisiko identifiziert.
    (Folgender Ort ist nicht explizit als sicher gekennzeichnet)

see http://help.sap.com/saphelp_nw73ehp1/helpdata/en/c5/18826ad1e944dfb39aa1d0fe3a188a/content.htm?frameset=/en/66/48a793bc2f4ec5bdb8e7e93ea6cd9f/frameset.htm
Welcome message configured but does not appear:
Table: NWBC_CFG parameter WELCOME_MESSAGE (see http://goo.gl/Dxz9tZ) is not taken into account
  • apply the highest patch mentioned in note 1353538
  • & retest.
System Messages with strange characters@Login page:
           http://goo.gl/iYOs7

Browser not supported error:
" You are calling this web site with a browser that is not supported "
  • update your Unified Rendering by following this article:
  • http://wiki.scn.sap.com/wiki/x/2oQCFQ
  • If issue still persists:
    Check in the Product Availability Matrix
    https://service.sap.com/sap/support/pam
    if the browser in use is supported with your Basis Release
  • --> Display All Product Versions --> search for basis version --> display Technical Release Information --> Web Browser Platforms
  • your browser is in that list: open a ticket BC-WD-UR
Login Page - when tabbing (keyboard) from user to password field - curser is not set correctly.
  • only occurs on SAP_BASIS 7.31 based backends
  • update your Unified Rendering by following this article:
    http://wiki.scn.sap.com/wiki/x/2oQCFQ
  • in case of problems open a ticket BC-WD-UR
NWBC does not start up at all (no splash shown)- although configuration is o.k.:
  • Try on a different PC
    most probably it is NOT a customer wide problem
  • Does it work for other users?
    check for a corrupt windows user profile



Total Crash of your NWBC:
  • retest with the most current NWBC version:
  • NWBC 3.0: http://goo.gl/oJlzl
  • NWBC 3.5: http://goo.gl/wYgry
  • check the windows event logging on the client at the time of the crash.
  • un+reinstall your .NET framework and your NWBC client
    (especially if other PC´s don´t have the same issue).
Troubleshoot NWBC related performance issues:
  • important:
    update your current NWBC runtime (note 1353538) + use most current NWBC client (download links@start of this note) -> retest
  • https://service.sap.com/~sapidb/012003146900000698932013E/PerformanceIssues.pdf
  • Special Cases:
  • Zoom Slider changed:
    https://service.sap.com/~sapidb/012003146900000307472012E/FontSizeSliderPerformance.pdf
  • OBN resolution is slow:
    https://service.sap.com/sap/support/notes/1630904
POWL:
  • locks sessions and displays error:
  • EN: ' Query <name of the Query> is already open in another session '
  • DE: ' Query <Name der Query> ist bereits in anderem Modus geöffnet '
  • check: https://service.sap.com/sap/support/notes/1433603
  • html client only: second (opening) window shows:
  • Error: "the specified application configuration was not found"
  • apply: NWBC runtime patch >=PL17
    https://service.sap.com/sap/support/notes/1353538
  • change+save of child window does not update the POWL in the father window
  • apply: https://service.sap.com/sap/support/notes/1778521


Connection failures:
  • NWBC- fails with:
  • EN: " The NetWeaver Business Client is only supported with the NetWeaver 7.02 and 7.20 and further releases"
  • DE: " NetWeaver Business Client für Desktop wird nur ab Release NetWeaver 7.02 und 7.20 unterstützt "
  • install highest patch level metioned in note 1353538
    background information: note 1368177
  • saprouter connection string fails:
  • https://service.sap.com/sap/support/notes/1310185
  • Proxy <->NWBC related Error:
  • Popup@Login:
    The proxy configuration within Internet Explorer cannot provide a proxy for this server

    -> see http://goo.gl/zUArw

    Internet Explorer is configured to use an automatic proxy based on a file protocol 'e.g.: <(file//c:\windows\proxy.pac)>, only URLs based on HTTP can be supported

    -> see http://goo.gl/855g8
  • Parser related issues:
  • Popup@Login:
                     EN: The backend connection for <connection name> generated a critical error: Parsing for server response is impossible.
                     DE: Backend der Verbindung <Verbindungsname> lieferte einen schwerwiegenden Fehler zurück: Parsing nicht möglich für Serverantwort
  • TRACE ENTRIES (note 1883689 type 2):
    runtime\NWBCTrace.log:
                     "CreateDOM: failed to create XML parser instance (hr=0x80040154(Class not registered))"
                    OR:
                     "readDirectoryXML: failed to create XML parser instance (hr=0x80070015(The device is not ready.))"
  • see http://goo.gl/RFWK3



SAP GUI <-> NWBC related issues:
first of all: test the same issue with the most current sap gui:
see note 1053737 + most current NWBC client (download links@start of this note).

specific errors:
  • web gui is used although sap gui for windows is expected to show up.
  • Environment:
    - load balanced SM59 remote destinations are in use
  • Troubleshooting:
    - https://service.sap.com/sap/support/notes/1883689 trace type 3
    - unpack zip and search in: \runtime\NWBCTrace.log
    = result in the trace:
    "URL is not complete to start Wingui (~service missing)"
  • Solution:
    - configure the RFC against an application server. (Load Balancing = No)

    - To achieve group login use SAP Logon Descriptions as described in
    https://service.sap.com/~sapidb/012003146900000346922011E/Multi_System_SapLogon_Config.zip (Front end load balancing)
  • SCENARIO:
    SAP GUI transaction running NWBC integrated with PFCG (other node details) configured "Target System" based on SM59 (remote destinations)
  • ISSUE:
    at runtime it can happen that an integrated SAP GUI session is pointing towards the wrong system.
  • SOLUTION:
    note 1827027
  • sap gui connection error popup: WSAECONNREFUSED: Connection refused
  • SCENARIO:
    message server is used as well for http traffic load balancing, several app servers are in place
    initial logon to NWBC -> integrated SAP GUI Transactions works on the first attempt
    NWBC logoff and login again=works: but it randomly occurs that integrated sap gui connections get refused with error popup.
  • solution:
    make sure you run the most current NWBC patch levels.
    NWBC 3.0 >= PL71
    NWBC 3.5 >= PL10
    NWBC 4.0 >= PL07
    download locations see note 900000
  • NWBC SAP GUI Integrator information popup:
    With the current installation, all transactions will be started with SAP GUI for HTML
    = Warning that no SAP GUI is installed on this client - to get rid of this warning:
  • install SAP GUI for Windows
  • if SAP GUI for Windows is not wanted but SAP GUI for HTML: http://goo.gl/f2HVY
  • SAP GUI for Windows is installed but still get this warning
    check note 1527068
  • get rid of annnoying popup:
  • EN: "Unsaved data will be lost. Do you want to log off?"
  • DE: "Nicht gesicherte Daten werden verlorengehen. Möchten Sie sich abmelden?"
           https://service.sap.com/sap/support/notes/1508133
  • not NWBC but web gui related:
  • Popup of type:
    "Sent URL
    /sap(<long string>)/bc/gui/sap/its/webgui/?<parameters>" sample & solution:https://service.sap.com/~sapidb/012006153200000426282011E/sent_URL_popup.pdf
  • fired URLs too long:
    https://service.sap.com/sap/support/notes/1459135
    (and it´s realted notes)
  • NWBC 4.0 does not show 'SAP GUI status messages' after ending certain (mainly business) SAP Gui Transactions (e.g. confirmation of successful saving or list couldn't be retrieved etc.)
  • Cause:
    Calling "default screen transaction" S000 triggers the "browser" to close the tab, and the status messages are "posted" afterwards -> tab already closed, message cannot be catched.
  • NWBC 4.0 works as designed:
    tabbed browsing - the opened tab is closed if there is a return to the default SAP Gui transaction (S000 - default screen). In this case this behavior is automatically triggered by the application itself and there is no technical solution to catch the status message at the moment. Works currently only with NWBC <4.0 (different navigation paradigm) or alternatively with web gui integration.
    We keep this in mind with further improvments of SAP GUI integration in upcoming NWBC releases.

  • NWBC navigation to sap gui transaction:
    EN: ~"error: Transaction <TA>%20<PARAMETER> is unknown"
    DE: ~"Fehler: Transaction <TA>%20<PARAMETER> ist unbekannt"
  • https://service.sap.com/sap/support/notes/1587833
  • + >=PL6 (http://goo.gl/oJlzl)
  • EN: "SAP GUI failed to start transaction <TACode>"
    DE: "SAP GUI konnte Transaktion <TACode> nicht starten"

    Scenarios:
  • long running sap gui transactions <-> navigate away:
    https://service.sap.com/sap/support/notes/1832849
  • if fails immediately:
    http://goo.gl/Pb1Rjp
  • EN: "SAPGUI has closed the communication channel. All sessions are lost"
    DE: "SAP GUI hat den Kommunikationskanal geschlossen. Alle Modi gehen verloren."
  • https://service.sap.com/sap/support/notes/1592316
  • yellow arrow icon (Log off -Shift+F3) ends in blank sap gui screen and final "SAP GUI has closed transaction <transaction>."
    use NWBC 3.5 (http://goo.gl/9dfVv) instead of 3.0


OBN (object based navigation) errors:
IMPORTANT:
apply the highest available runtime patch mentioned in
https://service.sap.com/sap/support/notes/1353538

  • still failing with "failed to resolve Object Based Navigation target"? ->

Special OBN error: "Error in Calling Up Application"
  • Scenario:
  • NWBC connected to a Portal
  • Webdynpro ABAP application is integrated into a portal PAGE
  • iView is assigned to this PAGE & page (OBN target) to the role
  • Workaround:
  • eliminate the PAGE and assign the iView (OBN target) directly to the role
other obn errors:

Portal <-> NWBC
Popup@Logon: "Could not open the logon window for the server with the supplied URL"
  • in NWBC.exe#*.1.log (see note 1883689 Trace type 2):

    <Timestamp> [Runtime] E    DoXmlGzipRequest failed  Exception
    WebException: The remote server returned an error: (500) Internal Server Error.   at System.Net.HttpWebRequest.GetResponse()   at com.sap.nw.nwbc.csruntime.implementation.navigation.core.CsNavigationVirtualRoot.DoGZIPRequest(String url, String requestData, String& responseData, Boolean addSapClientAndNwbcContext)
    [Runtime] E  Body of error response is EMPTY
    CreateUriAndDotEscape: uri=http://<full qualified host name>:<portal-port>/ConfigurationWS/ConfigurationWSConfig?wsdl&style=document&mode=standard
  • Solution:
    https://service.sap.com/sap/support/notes/1832862



"DSM: XHR Status was 500, not able to deliver PRO54-DSM data"
  • 10% case:
    NWBC Runtime not current:
  • apply the highest patch note of:
    https://service.sap.com/sap/support/notes/1353538



FOR THE REST(90%) USE FRONTEND VERIFICATION TO ANALYZE THE PROBLEM:
https://service.sap.com/sap/support/notes/1883689
  • 30% case:
    not correctly maintained RFC destinations:

    Sometimes not correctly maintained RFC destinations in the scenario are used and/or relevant SICF nodes are not active:
    Check the problematic request/response in the http traffic and verify the
  • corresponding RFC destinations (IF used in your scenario)
    TA: SM59

    Possible problems: e.g. forgotten to adjusted the server definitions after a system copy?

    or server definitions for system aliases are incorrect?
    background information: http://goo.gl/vJCvb
  • relevant SICF nodes - active?
    TA: SICF
  • 30% case:
    customer specific network/landscape issues:
  • e.g. wrong DNS resolution, wrong URL´s in the roles, blocking firewall, miss functional reverse proxy
  • 15% case:
    POWL caused:
  • check with trace type 1 OR 4 of note 1883689 -> 500 error in:
    http(s)://<full qualified host>:<port>/sap/bc/webdynpro/sap/fitv_powl_assistantcheck with BC-MUS-POW support - most probably note 1902580 & 1909714 can help.
  • 10% case:
    if ITS / WEBGUI related:
  • http://goo.gl/TsNP7
  • frontend traces: (note 1883689 type 1 or 4)
    in case of 403 errors in the ITS and/or mimes area
    -> check the respective SICF nodes (activated?).
    example for SICF node activation:
    note 1109215 (application dependent - this note is for webdynpro not ITS)
  • verify note 1611466
  • 5% case:
    other reasons:
  • open a ticket include traces:
    https://service.sap.com/sap/support/notes/1883689
    type 1 AND 2 OR 4
Timeout when logging into NWBC:
  • Error popup at login:
    The backend of connection <system> returned a fatal error: Request has timed out (12002)
  • solution/troubleshooting:
    https://service.sap.com/~sapidb/012006153200000487922011E/Request_has_timed_out.pdf



APPLICATION INTEGRATION:

General:
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/5b14a697817513e10000000a42189b/content.htm?frameset=/en/66/48a793bc2f4ec5bdb8e7e93ea6cd9f/frameset.htm


Rendering problems:
  • Close button is missing in the (Web-dynpro)-application:
  • https://service.sap.com/sap/support/notes/1353538 (>=PL17)
  • https://service.sap.com/sap/support/notes/1507477 (when SAP_BASIS 7.02 SP<=7)
  • https://service.sap.com/sap/support/notes/1526176
  • if NWBC 3.0 DESKTOP version then it needs to be >=PL5
    http://goo.gl/oJlzl (patch history: note 1353593)
  • NWBC HTML <-> IE9:
  • Rendering problems in IE9
    https://service.sap.com/sap/support/notes/1579105
  • Branding image / Logo not displayed
  • double check your configuration again!
    Here some examples:
    https://service.sap.com/~sapidb/012006153200000159042012E/branding.pdf


BEx Web:
  • Popups or F4 help hangs (e.g. looping wheel or script error)
  • e.g. when entering values into fields
  • check https://service.sap.com/sap/support/notes/1764448

cProject:
  • webdynpro based search fails:
    https://service.sap.com/~sapidb/012003146900000418672011E/SearchCprojectsFailsWebdynpro.pdf
  • launchpad issue: document is not loaded in external window
    works with NWBC html but not with NWBC Desktop.
  • keyword in dump:
    The ASSERT condition was violated
    in method:
    GET_DOCUMENTS_FOR_BASEOBJ

    apply:
    https://service.sap.com/sap/support/notes/1353538 (>=PL19)
  • mail workflow: URL link attachment opens cProjects but fails with dump due to a semicolon in the URL:
  • https://service.sap.com/~sapidb/012003146900000371472012E/cProjectMailsDump.pdf
  • Gantt chart overlaps embedded popup window
  • apply steps under section 'Exceptons' of
    https://service.sap.com/sap/support/notes/1753381

Session handling in the canvas area:
EN: "User session (HTTP/SMTP/..) closed after timeout"
DE: "Benutzer-Session (HTTP/SMTP/..) nach Timeout abgebaut"

main reasons for these timeouts:
  • https://service.sap.com/sap/support/notes/882548
  • https://service.sap.com/sap/support/notes/1364845
  • https://service.sap.com/sap/support/notes/1578632

less often the reason for these timeouts:
  • https://service.sap.com/sap/support/notes/1169817
  • https://service.sap.com/sap/support/notes/1240592
  • https://service.sap.com/sap/support/notes/1379678


non of the above scenarios do apply?
  • open a ticket on BC-CST-IC and attach ICM trace:
    During reproduction raise ICM trace level 3 (TA SMICM).



ROLE / MENU related issues:
generally be aware of:
  • https://service.sap.com/sap/support/notes/1321829
  • https://service.sap.com/sap/support/notes/1246860
Standard SAP Menu / Area Menu not shown entirely:
  • https://service.sap.com/sap/support/notes/1885214
ERROR: "The user menu tree for user <user> is empty."
expected menu entries don´t show up
(partially missing or completely empty)
  • generally that indicates that simply
  • no role is assigned to the user -> PFCG
  • role is assigned but folder is defined as a "link collection" instead of a "service map" - see:
    http://goo.gl/OEq9qa
  • OR check the following application specific chapters:
Work Center (top level navigation) is not shown in NWBC for HTML:
  • https://service.sap.com/sap/support/notes/1879939


NWBC <-> GRC:
  • https://service.sap.com/sap/support/notes/1604326
  • not directly NWBC related:
  • https://service.sap.com/sap/support/notes/1653405
  • error: "There are no task available to you yet"
    https://service.sap.com/sap/support/notes/1708513
    https://service.sap.com/sap/support/notes/1681453
NWBC<->solution manager + other products in general:
  • menu partially missing - or:
  • no menu entries at all - ERROR:
    "The user menu tree for user <user> is empty." or "No content available":
    Possible root causes:
  • Scneario: Running load balanced e.g. webdispatcher
    apply >=PL30 (see note 1353538)
    check HTTPURLLOC http://goo.gl/xp85T (alternatively check keyword: x-sap-webdisp-ap & wdisp/handle_webdisp_ap_header in http://goo.gl/RFZo7
    in case of SAP GUI content: http://goo.gl/oQaCW "Multi System Sap Logon Configuration"

    Additional information: Beside the "no content available" popup @Login this load balanced scenario could cause as well a second login prompt in the content area -> fixed with the same approach as mentioned above
  • other products are used on top of a solution manager
    https://service.sap.com/sap/support/notes/1346050
  • generally certain applications do use additional menu filters (BAdIs) which manipulate (remove+resort) the menu result AFTER the NWBC runtime "menu calculation" & BEFORE send to the NWBC client - example:
    https://service.sap.com/sap/support/notes/1647153
    another example - SRM see next chapter:
  • solman is dummping
  • https://service.sap.com/sap/support/notes/1601983
  • "There is no iView available for system"
  • if solman related: note 1709545
  • if obn related apply PL>=30  -> see note 1353538
    + in case DESKTOP client is used - retest with most current version:
    3.0:
    http://goo.gl/oJlzl  or
    3.5:
    http://goo.gl/9dfVv
EN: "FPM application <web dnypro application> was started without configuration"
DE: "FPM-Anwendung <web dnypro Anwendung> wurde ohne Konfiguration gestarted"
  • apply the hihgest patch level mentioned in note 1353538
    (miniumum PL26)

NWBC<->SRM:

Popup at login: "no content available - contact your Administrator"
  • special case of SRM:
    "Portal Independent Navigation Frame" (NWBC instead of Portal) further SRM customizing is required:
    SPRO (path depends on SRM version):
  • SAP SRM > SRM Server  > Technical Basic Settings  > Portal Independent Navigation Frame.
    activate switch "SRM_700_LOCAL_MENU" for NWBC navigation. (other related terms & responsible component: SRM-EBP-WFL-AC:rabax:
    CX_NWBC=>RAISE
    ...
    /SAPSRM/CL_URL_SERVICE=>GENERATE_ACCESS_URL )

other SRM related note:
  • Menu enries missing:
    https://service.sap.com/sap/support/notes/1529553
  • Supplier Self-Services (SRM-SUS) multiple logons when navigating
    https://service.sap.com/sap/support/notes/1665564
    https://service.sap.com/sap/support/notes/1651708
  • Popup:
    "Object or set with GUID 00000000000000000000000000000000 does not exist"
    https://service.sap.com/~sapidb/012003146900000308222012E/ObjectOrSetWithGUID.pdf
  • catalog <-> SRM:
    apply note 1746597 + highest Patch Level mentioned in note 1353538 for following errors:
  • dumping e.g. with error 'Parameter "" has an invalid value "". Possible values are:"".'
  • SRM does not 'resume' out of 'suspension' when coming back from catalogs.
  • catalog -> SRM =endless loop
    root cause:
    http<->https unwanted/incorrect protocol switch
  • SRM-Dump in NWBC when catalog items are transfered back to SRM
                    Check if the Dump refers to /SAPSRM/CL_CH_WD_INBOUND_HDLR
                    Switch off Inbound Handler as mentioned in:
https://service.sap.com/sap/support/notes/1294571
                    or implement:
https://service.sap.com/sap/support/notes/1903250
  • general Dump in NWBC canvas & ST22 dump fails in "check_invalid_chars url"
  • https://service.sap.com/sap/support/notes/1506161
Blank screen/no data transfer back to SRM/NWBC after external catalog item selection:

Scenario:
    1. Item selection in an external catalog:
    a) Catalog opens in an separate (NWBC-)window.
    b) User selects an (several) item(s) out of the external catalog.
    2. when transferring the Shopping Cart back to SRM (for placing the order) - NWBC shows an empty page instead of transfering the data successfully.

Check:
  • https://service.sap.com/sap/support/notes/1603168
  • still not working? - open a ticket on SRM-EBP-CAT


PDO Layer error:
https://service.sap.com/~sapidb/012003146900000494452011E/PDO_Layer_error.pdf


NWBC for HTML:
  • unwanted behavior: selection screens getting skipped - immediate results showing up.
  • https://service.sap.com/sap/support/notes/1766764
  • Content not showed properly / no proper behavior with Internet Explorer 10 (browser dependencies):
  • update your Unified Rendering by following article:
    http://wiki.scn.sap.com/wiki/x/2oQCFQ
  • If issue still persists:
    Check in the Product Availability Matrix
    https://service.sap.com/sap/support/pam
    if the browser in use is supported with your Basis Release

    --> Display All Product Versions --> search for basis version --> display Technical Release Information --> Web Browser Platforms

    your browser is in that list: open a ticket BC-WD-UR

NWBC 3.5 ONLY:
  • side panel does not show up
  • use >=PL5 of NWBC 3.5
    http://goo.gl/9dfVv


ADDITIONAL INFO if applicable:

Frequency of problem occurrence:
  • Occurs on all tested desktops?
  • Occurs only on certain desktops?
  • Is there a pattern recognizably (e.g. only with certain browser versions or operating systems)
  • Not client/desktop related at all -> server related only?

Remote access
  • optional prepare a remote connection: - https://service.sap.com/sap/support/notes/494980
  • Generally we recommend a WTS connection to a client with SAP GUI and NWBC installed.
  • Http connects are o.k. as well especially for javascript and http error code debugging sessions.
  • don't forget a short description how to reproduce the error URLs, navigation path, transaction, users/credentials...




troubleshooting part of the documentation:
Posted by at

3 comments:

  1. AnchalNovember 2, 2015 at 11:48 PM

    Its really helpfull and informative , Amazing work
    Online Business Directory

    ReplyDelete
    Replies
    1. AnonymousMarch 25, 2022 at 12:57 AM

      Sap Basis And Security: Sap Note 1378659 - Nwbc Known Issues And What To Check When Opening A Ticket >>>>> Download Now

      >>>>> Download Full

      Sap Basis And Security: Sap Note 1378659 - Nwbc Known Issues And What To Check When Opening A Ticket >>>>> Download LINK

      >>>>> Download Now

      Sap Basis And Security: Sap Note 1378659 - Nwbc Known Issues And What To Check When Opening A Ticket >>>>> Download Full

      >>>>> Download LINK ZS

      Delete
  2. AnonymousMarch 25, 2022 at 12:57 AM

    Sap Basis And Security: Sap Note 1378659 - Nwbc Known Issues And What To Check When Opening A Ticket >>>>> Download Now

    >>>>> Download Full

    Sap Basis And Security: Sap Note 1378659 - Nwbc Known Issues And What To Check When Opening A Ticket >>>>> Download LINK

    >>>>> Download Now

    Sap Basis And Security: Sap Note 1378659 - Nwbc Known Issues And What To Check When Opening A Ticket >>>>> Download Full

    >>>>> Download LINK

    ReplyDelete

Subscribe to: Post Comments (Atom)