SBL-SMI-00126: The session has timed out
Applies to:
Siebel System Software - Version 7.8.2.5 [19227] and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.5 [19227]
Database: Oracle 10.1.0.4
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-3388527211.
""""Checked for relevance on 23-MAY-2012""""
Symptoms
The connections from webMethods to Siebel are intermittently failing
with an error code 8234 on webMethods. Here is a sequence of events
observed in logs:
1. webMethods attemps to login and open a connection.
2. a new session is instantiated in Siebel and waits, but does not proceed with authentication.
3. webMethods request reports 8234 with a timeout after 2 mins.
4. webmethods opens another connection. This goes through successfully.
5. The first Siebel session terminates with a timeout after 45 mins.
The siebel log prints the typical parameters for the session and then the following two statements:
2021
2007-06-28 16:21:23 2007-06-28 17:06:24 -0400 0000014a 001 003f 0001 09
eMediaObjMgrWM_enu 25802 4040 6004
D:\sea78\siebsrvr\log\eMediaObjMgrWM_enu_25802.log 7.8.2.5 [19227] ENU
TaskConfig TaskCfgParamInit 4 0 2007-06-28 16:21:23 The Parameters for the current task are :
TaskConfig TaskCfgParamInit 4 0 2007-06-28 16:21:23 Enterprise : SiebelINT
TaskConfig TaskCfgParamInit 4 0 2007-06-28 16:21:23 Server : SBINT2
TaskConfig TaskCfgParamInit 4 0 2007-06-28
16:21:23 Siebel Home :
D:\sea78\siebsrvr
....
prints other parameters
...
TaskConfig TaskCfgParamInit 4 0 2007-06-28 16:21:23 Eligibility Display Mode : 1
TaskEvents TaskCreation 3 0 2007-06-28 16:21:23 Created
context for task 25802 with session timeout = 2700 (thrdId 6004,
timestamp 1183062083)
TaskEvents TaskTimeout 3 0 2007-06-28 17:06:24 SBL-SMI-00126: The session has timed out.Further investigation in the Webmethods logs showed the following errors:
2007-06-28 13:02:12 EDT [ISC.0066.0024V5] FSMTValuesHash.getEntryLock(): id=24381839 lock request granted
2007-06-28 13:02:14 EDT [ART.0114.1007E] Adapter Runtime: Error Logged.
See Error log for details. Error: [ADA.448.1000]
SiebelJavaConnection.connectFromValues -
dataBean.login(siebel.tcpip.none.none://sbwsint01:2321/SiebelINT/eMediaObjMgrWM_enu)
threw a SiebelException: code(8234), msg(Logon Request 394 was
abandoned after 68991 ms. Connection: 6481 due to connection shutdown
request Connection timed out (SBL-JCA-303) )
2007-06-28 13:02:14 EDT [SCC.0126.0119E] An error occurred while
attempting to create connections for
IEEEBMSConnections.Siebel:Siebel_eMedia
2007-06-28 13:02:14 EDT [SCC.0126.0106E] An error occurred while
attempting to retrieve a connection from
IEEEBMSConnections.Siebel:Siebel_eMedia
2007-06-28 13:02:14 EDT [SCC.0126.0202V1] SCC ConnectionManager pool IEEEBMSConnections.Siebel:Siebel_eMedia reset
2007-06-28 13:02:14 EDT [ART.0114.1007E] Adapter Runtime: Error Logged.
See Error log for details. Error: [ART.118.5053] Adapter Runtime
(Connection): Unable to get a connection to resource
IEEEBMSConnections.Siebel:Siebel_eMedia.
[ADA.448.1000] SiebelJavaConnection.connectFromValues -
dataBean.login(siebel.tcpip.none.none://sbwsint01:2321/SiebelINT/eMediaObjMgrWM_enu)
threw a SiebelException: code(8234), msg(Logon Request 394 was
abandoned after 68991 ms. Connection: 6481 due to connection shutdown
request Connection timed out (SBL-JCA-303) )
2007-06-28 13:02:14 EDT [ART.0114.1007E] Adapter Runtime: Error Logged.
See Error log for details. Error: [ART.117.4012] Adapter Runtime
(Adapter Service): Unable to run adapter service. Error occurred when
connecting to resource IEEEBMSConnections.Siebel:Siebel_eMedia.
[ART.118.5053] Adapter Runtime (Connection): Unable to get a connection to resource IEEEBMSConnections.Siebel:Siebel_eMedia.
[ADA.448.1000] SiebelJavaConnection.connectFromValues -
dataBean.login(siebel.tcpip.none.none://sbwsint01:2321/SiebelINT/eMediaObjMgrWM_enu)
threw a SiebelException: code(8234), msg(Logon Request 394 was
abandoned after 68991 ms. Connection: 6481 due to connection shutdown
request Connection timed out (SBL-JCA-303) )
Cause
This customer was using a connector developed by webmethods, which
uses the underlying technology of "Siebel Java Data Beans" to connect to
the siebel object manager.
A thorough review of java data beans timeout settings has not helped.
Java Data Beans timeouts are described at
Transports and Interfaces: Siebel Enterprise Application Integration
> Integrating with Java > About Running the Java Data Bean >Connection Parameters for the SiebelDataBean
They did not help though.
PLEASE NOTE: siebel.properties file is not the first in precedence.
If the java code provides values for these parameters, they are used.
If the java code does not provide values, the next step is to look up siebel.properties. If found, it is used.
If not found, then default values described in the above bookshelf reference apply.
See also Utilizing the siebel.properties did not succeeded in our J2EE application (Doc ID 536387.1)
The customer network experts further investigated the issue and found
out there were timeout settings at a firewall between the 2
applications:
"We worked with our network team to install a sniffer, capture tcp
traces on the webMethods servers, review them along with the logs from
Siebel and webMethods.
The traces show retransmissions and a reset on the tcp ports at times of
failure and the problem seems to be with either webmethods
adapter/Siebel java data bean trying to communicate on tcp ports that no
longer have an active Siebel session on the other end or our network
configuration with a firewall and two routers in between these two
servers blocking reuse of the tcp ports.
We seem to run into this condition because webMethods adapter does not
honor the expire timeout and close the connection nor recognize the
termination of the target Siebel session."
Conclusion :
"the connections are getting dropped due to a timeout setting on our
firewall. We have not seen any connection failures after we increased
the timeout."
Applies to:
Siebel Wireless - Version: 7.8.2 [19213] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-3106277661.
Symptoms
SBL-SMI-00126Dear Supportweb,
We’re dealing with loss of information during synchronization in our
environment. Please see attached log file (CGCEObjMgr_esn_24409.log). As you can see, for some
reason the connection was interrupted (error SBL-SMI-00126) after 30 minutes.
Analyzing
the log file, we can see that some Orders were uploaded, but one Receipt (BC UH Receipt) and
another Order were lost.
Problems:
1) This loss of information is unacceptable.
Orders and Receipts are critical in Unilever operations;
2) No errors were raised during
and after synchronization, in the iPaq or at the server. No errors were reported in the
Administration – Server Management -> Sessions and in the Administration – Mobile ->
Session Administration. Error was discovered because the user noticed that the receipt wasn’t at
the server.
This SR is being logged with maximum priority because we cannot guarantee that
errors like this aren’t occurring for other users. Also, no errors are raised in Administration
Views.
Regards,
Felipe Lazaretti
Cause
Change Request 12-1FLGF8L
Solution
Message 1
Following behavior has been observed.
User runs batchsync selecting uploadonly.
- Transactions are uploaded and are written to the Prevtxns.txt.
- GetEventList is fired.
- Time out occurs.
- OM is trying to process the transactions but there is no Commit statement.
- User tries to run full sync
- OM starts extracting database with no upload transactions.
- SynSummary.txt shows LastTranId as the last transaction that is uploaded and processed.
- OM assumes that all these transactions have uploaded and committed and therefore starts extracting database.
- Records are lost.
This has been determined to be product defect. Change Request 12-1FLGF8L
has been logged to address this defect in future release.
Also, FR 12-1FW1G29 and FR 12-1FLGF9Y have been logged to address this defect in 7.8.2.3 QF and 7.8.2 QF respectively.
Thank you
Applies to:
Siebel System Software - Version: 7.7.2.1 SIA [18353] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2.1 [18353] ESN Com/Med
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-2663369531.
Symptoms
SBL-DAT-00398, SBL-SMI-00126Hello support,
we have installed eSales Application with LDAP authentication. We would
like to know how to enable the "Forgot your password" functionallity. When we click the link
forgot your password we find SBL-UIF-00335 error in object manager log file.
We followed
the indications regarding adding the group of views to the user responsability but this does not
work either.
User Registration Forget Pwd Info View
User Registration Forget Pwd
Challenge Ques View
User Registration Forget Pwd Confirm View
User Registration Forget Pwd
Challenge Answer Error View
User Registration Forget Pwd Decline View
Thanks in
advance
David
Cause
Configuration/ Setup
Solution
Message 1
For the benefit of other users:
After enabling a group of workflows the customer got the problem resolved
User Registration Initial Process
User Registration Forgot Password Process
User Registration Process
CUT Exception Handling Process
LOY User Registration Member Process
User Registration SubProcess
Thanks and Regards,
Siebel Technical Support
Applies to:
Siebel System Software - Version: 8.0 [20405] to 8.1 [21039] - Release: V8 to V8
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Oracle 10.2.0.1
Application Server OS: Novell SUSE Linux Enterprise 9.0
Database Server OS: Novell SUSE Linux Enterprise 9.0
This document was previously published as Siebel SR 38-3325861536.
*** Reviewed for relevance on 7-Mar-2012 ***
Symptoms
After installation of Siebel 8.0, subsequent Object Manager login sessions appear to hang until they ultimately
timeout, resulting in error message SBL-NET-10407.
Eventually the Object Manager session reported the following message :
MessageFlow MsgFlowDetail 4
0000000d461d2f53:0 2007-04-11 11:10:47 1302858672: Returned from
SessionHandleMsg(1514) for task 11534352, pErrStack = 0x0940d3e0
TaskEvents TaskTimeout 3 00000603461d23d9:0 2007-04-11 12:10:51 SBL-SMI-00126: The session has timed out.
MessageFlow
MsgFlowDetail 4 00000603461d23d9:0 2007-04-11 12:10:51
1302858672: Calling SessionCleanup for task 11534352, pErrStack =
0x0940d3e0
Solution
On further investigation it was established that the customer was
running with a modified HTTP port due to the port access restrictions
for non-root users.
For further information on this please Refer to the Siebel Bookshelf for
your specific version: 'Siebel Installation Guide for UNIX: Servers,
Mobile Web Clients, Tools > Installing the Siebel Web Server
Extension > Postinstallation Tasks for the SWSE > Granting User
Permissions on the Web Server'.
In addition to make the change to the httpd.conf file it was necessary to modify the HTTPPort setting within the eapps.cfg
file on the web server. Once this change was made the customer was able
to establish a connection to the Object Manager and establish a single
session. Subsequent sessions would then receive 'Server Busy' messages.
In order to investigate this behavior an analysis was made of both the
Web Server logs and of the SWSE logs and the following error messages
were evident:
(Web Server Logs)
[Mon May 21 12:36:55 2007] [error] [client
xxx.xxx.xxx.xxx] File does not exist:
/siebel/sweapp/public/enu/images/aGIF, referer:
http://xxxx.xxxx.xxxx.xxxx:nnnn/sales_enu/start.swe?SWECmd=GetViewLayout&SWEView=Server%20Server/Compgroup%20View&SWEVI=&SWEVLC=0-1_Siebel%2bSales%2bEnterprise_43%257c1166247115%257c0_0_20405_00_L
The above message occurs a few times and concerns me a little less than the error below :
[Mon May 21 12:37:14 2007] [warn] child process 25541 still did not exit, sending a SIGTERM
OSDWaitTid: pthread_create failed: Cannot allocate memory
[Mon May 21 12:37:14 2007] [notice] caught SIGTERM, shutting down
(SWSE Logs)
SisnapiLayerLog Trace 3 0000062a465139af:0 2007-05-21
12:37:05 1133542320: [SISNAPI] Creating SISNAPI Async Thread for
connection (0x8af81f0)
SisnapiLayerLog Error 1 0000062a465139af:0 2007-05-21
12:37:05 1133542320: [SISNAPI]: connection (0x8af81f0)
OSDCreateThread() failed with errCode = 852173 sysError 12
SisnapiLayerLog Trace 3 0000062a465139af:0 2007-05-21
12:37:05 1133542320: [SISNAPI]: releasing connection (0x8af81f0),
refCount = 1
SessMgr ConnOpen 3 0000062a465139af:0 2007-05-21
12:37:05 [SMCONN] Hello handshake to
(siebel.TCPIP.None.None://xxxx.xxxx.xxxx.xxxx:nnnn/SBA_80/SSEObjMgr_enu/RR)
failed in 0 secs
GenericLog GenericError 1 0000062a465139af:0 2007-05-21
12:37:05 (smconn.cpp (318) err=1180695 sys=0) SBL-NET-01047:
Internal: failed to create async listener thread
These errors suggested memory shortages on the web server and so a
review was made of the configuration and memory consumption. During this
review checks were made for the recommended settings in the httpd.conf file and it was established that there was a difference within the <IfModule worker.c> section :
<IfModule worker.c>
ThreadLimit 1000
ServerLimit 10
StartServers 1
MaxClients 1000
MinSpareThreads 1
MaxSpareThreads 1000
ThreadsPerChild 1000
MaxRequestsPerChild 0
</IfModule>
The customer had configured a ServerLimit of 10 whereas the recommended settings within the Siebel Bookshelf were for StartServers and ServerLimit to be set to 1.
Once this change was made and the Web Server restarted the customer was
able to connect to their Siebel 8.0 environment on the first and
subsequent connection attempts.
Applies to:
Siebel System Software - Version: 7.5.3.13 SIA [16275] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3.13 [16275] Auto
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 2.8
Database Server OS: Sun Solaris 2.8
This document was previously published as Siebel SR 38-3289921981.
Symptoms
SBL-DAT-00144, SBL-EXL-00145, SBL-DAT-00306, SBL-DAT-00315,
SBL-DAT-00322, SBL-DAT-00501, SBL-OSD-00204, SBL-SVR-04000,
SBL-SVR-01004, SBL-SMI-00034, SBL-SMI-00126, SBL-GEN-09103,
SBL-NET-01023, SBL-NET-01201, SBL-NET-01204Our thin clients are presenting error "page can not be displayed” after loggin and doing
some
navigation.
We first thought this is because of the SRF, so we have changed the SRF also.
But still the same error persists.
I am attaching the log files of the Web server and
Siebel eAutomotive object manager.
Some of the errors from the log files
are:
----------------------------------------------------------------------------------------------------
SBL-NET-01204:
Internal: recv() failed: Connection timed out
SBL-SMI-00034: Internal: Error (null) reading a
message from the client
[SWSE] New anon session open failed
SWSE] Could not get an anon
session...PROBLEM
[SWSE] after the timeout/broken anonymous connection impersonate failed.
Could not open repository file '%1'.\n\nFile does not exist or may be in use by another
process?
-----------------------------------------------------------------------------------------------------
We
already tried by recycling the whole environment also.
Cause
Configuration/ Setup
Solution
Message 1
For the benefit of other readers:
After extensive troubleshooting with Resonate environment variables,
Resonate password variables in Unix OS and comparing errors in the web
server and OM logs, customer was able to identify the server which was
presenting the behavior.
Customer had three load balancers in the environment (A, B, C). Due to
some activities they were not using the C load balancer. When shutting
down the A LB, where only B LB was running, the thin client worked
properly without any issue.
When we shut down B and put only A LB up. At that time started getting same error for the thin client.
Customer resolved the issue by removing the defecting node from Resonate and added it back.
It also found that CFGClientRootDir for the defective node was set to
%SIEBEL_ROOT% while searching Siebns.dat. This value was also changed.
Thank you and best reagrds,
Applies to:
Siebel CRM - Version: 7.7.2.4 [18365] to 7.7.2.6 [18372] [Release: V7 to V7]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.7.2.6 [18372]
Database: Oracle 9.2.0.7
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 2.6
This document was previously published as Siebel SR 38-3205106281.
Symptoms
SBL-DAT-00808, SBL-UIF-00296, SBL-UIF-00501, SBL-UIF-00314, SBL-SMI-00126
Hello,
We have a hyperlink to our Siebel Application on a Web Portal Application.
This
functionality was working fine with 7.7.2.3 Fix Pack level, but now we
are getting a Session Timeout error message after upgrading to 7.7.2.6.
We need immediate attention since users in production environment are affected.
Thanks!
Cause
On Siebel 7.7.2.4 and later versions, the session gets closed at AOM
level when clicking the “X” button, so after clicking the link for the
second time, the user can successfully open a new Siebel session, but he
always gets the “Your session timed out because you were idle for too
long” message first.
Clicking “File > Log Out” in these versions
is working fine, but the "X" button is expected to work just like “File
> Log Out”, which is not happening.
Change Request #
12-1HCLZNP (“Reusing shortcut with SWECmd=GotoView after X-ing the first
session gives session timeout error”) has been logged to address this
issue.
When a product defect or enhancement request is logged, it is
reviewed, prioritized, and considered for incorporation into a future
maintenance or major release.
Solution
Message 1
For the benefit of other readers:
The end user accesses a Web Portal Application.
The
home page of this Portal contains a “New Activity” hyperlink, which
opens a new web browser window and successfully takes the user to a new
Siebel session.
The “New Activity” hyperlink is defined in the following format:
<html>
<a
href="http://hostname/callcenter_enu/start.swe?SWECmd=GotoView&SWEView=Activity+List+View&SWERF=1&SWEHo=hostname&SWEBU=1&SWEApplet0=Activity+List+Applet+With+Navigation"
target="_blank">New Activity</a>
</html>
This hyperlink works fine only for the first time.
After
completing the task with Siebel Application, the user clicks the “X”
button on the web browser window to exit the Siebel Application.
At this stage, he does not use “File > Log Out” menu option to exit the Siebel Application.
When
the user clicks the “New Activity” hyperlink again on the original Web
Portal Application browser window, the following error message is shown
in a pop-up dialog box:
“Your session timed out because you were idle for too long. Please log in again to resume.
If
you had a Siebel attachment open, your changes may have been lost.
Please save the file locally, close it, and reattach it to the
appropriate record.”
After clicking the “OK” button, the Siebel Application is launched normally.
End users started noticing this behavior after applying 7.7.2.6 Fix Pack on top of Siebel Version 7.7.2.3.
According
to Change Request # 12-PUDQB1 (“X-ing out browser window should
terminate a session on OM”), an Enhancement Request was implemented in
7.7.2.4 Fix Pack (Fix Request # 12-10GRFKR) and 7.8.2 Version (Fix
Request # 12-T8C4UR), which causes the “X” button in the web browser
window to behave just as if the user was clicking “File > Log Out”
menu.
This information can be found in the Maintenance Release Guide for Siebel 7.7.
If the user closes the first Siebel session by going to “File > Log Out” menu, he gets successfully logged out.
Then, if he clicks the link again on the same Web Portal page, he does not get the “Session Timeout” message.
Customer
environment uses Web Single Sign-On, so the “File > Log Out” menu
should not be enabled when using Web SSO, and the user must use the “X”
button in this case.
This behavior can be reproduced on a
standard environment, regardless of the Security Adapter being used,
even with Database Authentication without SSO.
We could reproduce
this behavior with a pure HTML file containing a simple HREF link to the
Siebel URL, but only on some environments, and only if the hyperlink
includes the “start.swe?SWECmd=...” part of the URL.
If the URL in
the hyperlink does not contain a “SWECmd” string, everything works as
expected, and no error is shown after closing the session through either
“File > Log Out” or the “X” button.
After performing
further tests, we noticed that the session does get successfully closed
in the Application Object Manager at Siebel Server level after clicking
the “X” button on the web browser window when using Siebel Version
7.7.2.4 or later.
On Siebel Versions prior to 7.7.2.4, the session keeps open until it times out, as expected.
On
Siebel 7.7.2.3 and earlier versions, the session is not closed at AOM
level when clicking the “X” button, since this functionality was
implemented in 7.7.2.4.
So after clicking the link for the second
time in those versions, the following error message used to be
displayed, and users had to click the hyperlink again to open another
Siebel session:
“Your Siebel shortcut cannot be opened in this window.
Please
drag and drop your Siebel shortcut to a window where Siebel is already
running. If you want a second Siebel window, please select the Internet
Explorer Browser icon from your Desktop or select the Internet Explorer
Browser option from your Programs list to create a new window. You may
then drag and drop the Siebel shortcut to this new window.”
This
behavior has been resolved by Siebel Engineering on Fix Request #
12-1HPGG7Z, and a patch is available on Siebel Version 7.7.2.6 [18372]
QF0682.
Customer applied Quick Fix 0682 on top of 7.7.2.6 Fix Pack, and now the application behaves as expected.
Thank you
Applies to:
Product Release: V7 (Enterprise)
Version: 7.5.2.211 [16061]
Database: Microsoft SQL Server 2000 SP 2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 3
This document was previously published as Siebel SR 38-992780051.
Symptoms
SBL-SMI-00126In SI mode: I Logged out using the Ctrl + Shift + X and when I log back in using the same login
page that was served after the logout, it shows the session time out mesage. However, If I log
out by going to the File menu in the Application Menubar and choosing Log out and then log back
again, this problem does not happen.
Here what I found. After logging out using Ctrl +
Shift + X, if I close the login window that is served by the logout and start a new page and
login, it works fine..
Here are the links that is returned after the
logouts.
Logging out using File menu returns this
http://10.15.122.107/system_std/start.swe?File=SWESubmitForm%28document.SWEAppMenuForm%2Cc_14%2C%22%22%2C%22%22%29&Edit=&View=&Help=&SWECmd=Logoff&SWEMethod=*Browser**Logoff**&SWEVI=&SWEView=&SWEApplet=&SWEField=&SWERowId=&SWERowIds=&SWEReqRowId=&SWESeq=&SWESP=&SWETargetView=&SWETVI=&SWETA=&SWEM=&SWEH=&SWEW=&SWEContainer=&SWEPOC=&SWENeedContext=&SWEKeepContext=&SWEService=SWE+Command+Manager&SWEDIC=&_sn=9jnYBu0uPDWNVlkzUP5PomMUgdi6OtIiT1fid8k.qUM_
Logging
out using Ctrl + Shift + X returns this
http://10.15.122.107/system_std/start.swe?File=&Edit=&View=&Help=&SWECmd=KeyCode&SWEMethod=11088&SWEVI=&SWEView=&SWEApplet=Salutation+Applet+%28WCC+Home%29&SWEField=&SWERowId=&SWERowIds=&SWEReqRowId=&SWESeq=&SWESP=&SWETargetView=&SWETVI=&SWETA=&SWEM=&SWEH=&SWEW=&SWEContainer=&SWEPOC=&SWENeedContext=&SWEKeepContext=&SWEService=&SWEDIC=&_sn=pr9Rq93W8-tY0FMd34319QLoRaUZI8LE4KmJPMstjKU_
Thanks
Aabid
Solution
Message 1
For the benefit of other users:
This problem was reproduced as follows:
1) Set in uagent.cfg:
[SWE]
HighInteractivity=FALSE
2) Restart Siebel server.
3) Login - SADMIN\SADMIN
4) Log out using the Ctrl + Shift + X,
5) Log back in - SADMIN\SADMIN
6) You get a session time out error
when you log back in using the same login page that was served after the logout, it shows the session time out mesage:
"The session timed out because you were idle for too long. Please log in again to resume"
7) If you log in again everything is fine.
Repeat the above test using File > Log out rather than Ctrl + Shift +
X and the time out error is not seen. Change Request 12-GII41X has been
raised to address this Product Defect.
תגובות
הוסף רשומת תגובה