Skip to Content
author's profile photo Former Member
Former Member

ITSSM_sendSessInfo returns "Session not fail-safe"

Dear all,

We upgraded to ITS 6.20 PL20 here with R/3 4.7 and in both IE 6 SP2 and Mozilla Firefox 1.5.0.7 sessions are terminated after a message "Session not fail-safe" appears in the status bar of the browser (the message actually only appears in IE, not in Firefox. Session is terminated all the same though). The usual "Invalid Session

You have tried to use a WWW session that has already been terminated." is displayed.

I've established that the message is triggered by JavaScript FM ITSSM_sendSessInfo, but can't explain why this suddenly happens. ~timeout (60) and ~usertimeout (.1) are fine and never caused a problem in earlier tests.

If someone could point me into the right direction, please.

Kind regards,

Michael Koch

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Oct 17, 2006 at 02:48 PM

    In th meantime, I found the following SAPNet note on this:

    918265 - SAP GUI for HTML in EP: /!\ Session not fail-safe /!\

    <i>If you use the SAP GUI for HTML of the NetWeaver ITS plug-in in the SAP Enterprise Portal, the message "/!\ Session not fail-safe /!\" sometimes appears in the status line of the browser.

    While this message refers to an internal problem, it is not critical in the case of the SAP GUI for HTML in the portal.</i>

    We are not using SAP EP here, but running bespoke web templates for IACs. In our case sessions are terminated after the status message appears.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 17, 2006 at 03:26 PM

    Hello Michael,

    maybe note 918265 is helpful.

    The message "Session not fail-safe" is displayed in case the current service running in the browser can not communicate with some management code in another hidden frame.

    When the ITS service was started in the Portal (EP) the Portal takes care of session management. Mostly the message "Session not fail-safe" can be ignored when running an ITS service inside the EP.

    On the other side, when the service runs standalone (outside the EP) the ITS manages the session and provides its own frontend session management with a hidden frame. Now, when this message appears, something went wrong. This could be

    - the hidden frame (or frameset) was destroyed by

    custom code (e. g. from an IAC)

    - the frame the service runs in is not allowed to communicate cross-frame with the hidden frame.

    - seldom a browser error

    - the session was terminated before (timeout etc.)

    Did you check in SM04 if the session was really closed?

    With best regards,

    TJ

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Thorsten Domsalla

      Hi Thorsten,

      > I don't understand. You have an IAC with service

      > files containing ~webgui set to 1 (activating SAP GUI

      > for HTML)? In that case it not an IAC anymore but

      > something in between IACs and SAP GUI for HTML ...

      > undefined.

      >

      That's exactly what we have got here. It's a bunch of transactions, some with custom web templates, some without (they therefore drop right into the WebGUI, as ITS is in mixed mode here).

      > The ITS' frontend session management is activated per

      > default in SAP GUI for HTML. And it is deactivated in

      > all other services (IAC) since there is no generic

      > DHTML environment. However, frontend session

      > management can be activated with parameter

      > ~disconnectonclose for IAC (see note 689291) but this

      > on customer's risk.

      Isn't this what also the ~webgui does? Since I switched it off the JavaScript includes are not copied in anymore on my templates and the HTML title is actually what I named it in my HTML code.

      Anyroad... it seems to be sorted now.

      Many thanks again,

      Michael Koch

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.