Self Service: Sporadic 'Invalid Encoding' Errors After Session Timeout

(Doc ID 1984647.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Service - Version 8.1.1.9 [23016] to 8.1.1.14 [IP2014] [Release V8]
Information in this document applies to any platform.

Symptoms

Preparation
- have a standard environment 8.1.1.11 + Patch Set 9
- have two or more languages installed, e.g. ENU and PTB
- for SServiceObjMgr_enu and SServiceObjMgr_ptb set following OM parameters
  HighInteractivity="True", EnableOpenUI="True"
  restart the 2 components
- in eapps.cfg to shorten the test cycles:
  reduce GuestSessionTimeout from 300 to 120
  reduce SessionTimeout from 900 to 300
  restart IIS service
- launch a browser, e.g. Chrome
- login once to Self Service ENU, and once to Self Service PTB

The repro steps
01- login to one of the Self Service languages
02- navigate to SRs, leave the application idle for 6 minutes
03- try to navigate to the home page
04- acknowledge the session timeout message
05- now automatically navigated to the login view where username/pwd can be
entered
06- enter the URL of the other language of Self Service
07- acknowledge another session timeout message
08- enter username/pwd and click Submit
09- now 4 "Invalid encoding" messages appear
10- terminate them with the x button top right
11- click Submit again, now in the application
12- navigate to SRs, leave the application idle for 6 minutes
13- continue with step 03

With above steps the Invalid encoding can be reproduced again and again

The same error can be obtained when using only one language and same steps:
log in, wait until  session timeout is reached, try to navigate to Service
Requests, acknowledge the "Session has ended" message, and log in again.
However, with only one language the reproduction rate is much lower. I could
reproduce once every few hours.
With the two languages the "Inavild encoding" message is 100% reproducible.

The behavior here should not be confused with that of bug 17028194 - Session Timeout No Working For OpenUI. There also an 'Invalid encoding' happens, but the message bar is involved

Here we have an error which occurs with 8.1.1.11 Patch Set 9, and message bar
is not involved. Here we have the Standard Interactivity "Self Service"
application, which is out of the box prepared for Open UI. SI applications do
not have a message bar.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms