on 08-10-2014 12:56 PM
Hello,
We are getting the following dump in production system -SAP ECC 6.0.
The wp s are getting terminated automatically as shown in dev_disp file.
.........................................................
Sun Aug 10 12:15:38 2014
DpHdlDeadWp: W2 (pid=25722) terminated automatically
Sun Aug 10 12:16:46 2014
DpHdlDeadWp: W34 (pid=8081) terminated automatically
Sun Aug 10 12:23:45 2014
DpHdlDeadWp: W28 (pid=25734) terminated automatically
...........................................................
The dev_ms shows the following :
[Thr 139866179913568] Thu Aug 7 00:25:35 2014
[Thr 139866179913568] *** ERROR => MsSCheckConnections: no response from client C11 (161.134.204.144) after 300 secs received [msxxserv_mt. 4136]
[Thr 139866179913568] *** ERROR => MsSCheckConnections: disconnect now [161.134.204.144] [msxxserv_mt. 4140]
[Thr 139866179913568] Thu Aug 7 10:20:56 2014
[Thr 139866179913568] *** ERROR => MsSCheckConnections: no response from client C22 (144.145.30.11) after 300 secs received [msxxserv_mt. 4136]
[Thr 139866179913568] *** ERROR => MsSCheckConnections: disconnect now [144.145.30.11] [msxxserv_mt. 4140]
[Thr 139866179913568] Fri Aug 8 09:35:00 2014
[Thr 139866179913568] *** ERROR => MsSCheckConnections: no response from client C20 (139.24.138.145) after 300 secs received [msxxserv_mt. 4136]
[Thr 139866179913568] *** ERROR => MsSCheckConnections: disconnect now [139.24.138.145] [msxxserv_mt. 4140]
[Thr 139866179913568] Fri Aug 8 09:35:40 2014
[Thr 139866179913568] *** ERROR => MsSCheckConnections: no response from client C12 (139.24.138.145) after 300 secs received [msxxserv_mt. 4136]
[Thr 139866179913568] *** ERROR => MsSCheckConnections: disconnect now [139.24.138.145] [msxxserv_mt. 4140]
Last log on August 8.
What could be the reason?There are no licenses expiring..
Thanks and regards,
uday.
Hello,
The dev_rd log shows :
***LOG Q0I=> NiIRead: P=157.163.152.117:2314; L=157.163.136.149:4800: recv (104: Connection reset by peer) [nixxi.cpp 5086]
*** ERROR => NiIRead: SiRecv failed for hdl 2278/sock 128
(SI_ECONN_BROKEN/104; I4; ST; P=157.163.152.117:2314; L=157.163.136.149:4800) [nixxi.cpp 5086]
***LOG S23=> GwIDisconnectClient, client disconnected (864) [gwxxrd.c 10538]
***LOG S74=> GwIDisconnectClient, client disconnected ( DEFTHW99) [gwxxrd.c 10549]
***LOG S0R=> GwIDisconnectClient, client disconnected () [gwxxrd.c 10566]
***LOG S0I=> GwIDisconnectClient, client disconnected ( java) [gwxxrd.c 10579]
*****************************************************************************
*
* LOCATION SAP-Gateway on host / sapgw00
* ERROR connection to partner ''
* broken
*
* TIME Sun Aug 10 14:50:37 2014
* RELEASE 720
* COMPONENT NI (network interface)
* VERSION 40
* RC -6
* MODULE nixxi.cpp
* LINE 5086
* DETAIL NiIRead: P=157.163.152.117:2314; L=157.163.136.149:4800
* SYSTEM CALL recv
* ERRNO 104
* ERRNO TEXT Connection reset by peer
* COUNTER 2336695
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Udaya,
ERROR => MsSCheckConnections: no response from client
Please follow SAP Note 1532367 - MsSCheckConnections
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
The system is ECC 6.0
The dump details are as below :
Runtime Errors CALL_FUNCTION_REMOTE_ERROR
Date and Time 10.08.2014 14:40:10
Short Text
"Anmeldung nicht möglich (Fehler bei der Lizenzprüfung)"
What happened?
Error in the ABAP Application Program
The current ABAP program "/SIE/SAPLAD_Z0HBAPI_TRAVEL" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
The error occurred during an RFC call to another system.
In the target system, a short dump has been written as well.
More detailed information on the error cause can be found there.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "Anmeldung nicht möglich (Fehler "
on the called page.
How to correct the error
Please refer to the notes described in the
short dump.
System environment
SAP-Release 700
Application server...
Network address......
Operating system..... "Linux"
Release.............. "3.0.93-0.8-default"
Hardware type........ "x86_64"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 13
Shortdump setting.... "full"
Database server...
Database type..... "ORACLE"
Database name.....
Database user ID.. "SAPSR3"
Terminal................. "portal"
Char.set.... "de_DE.ISO-8859-1"
SAP kernel....... 720
created (date)... "Mar 8 2014 08:39:01"
create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 "
Database version. "OCI_102, 11.2.0.4.0, V1, default"
Patch level. 600
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
SAP database version. 720
Operating system..... "Linux 2.6, Linux 3"
Memory consumption
Roll.... 0
EM...... 2092720
Heap.... 0
Page.... 0
MM Used. 895296
MM Free. 1194848
and Transaction
Client.............. 101
User................ "CPIC_TILO"
Language Key........ "D"
Transaction......... " "
Transactions ID..... "53E7B3EC66796484E10000009DA38898"
Program............. "/SIE/SAPLAD_Z0HBAPI_TRAVEL"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "########"
Database Release.... 720
Kernel Release...... 720
Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchronous and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. "###"
User................ "############"
Transaction......... " "
Call Program........." "
Function Module..... "/SIE/AD_Z0H_BAPI_TRIP_MENU_EP"
Call Destination....
Source Server.......
Source IP Address... "
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
rmation on where terminated
Termination occurred in the ABAP program "/SIE/SAPLAD_Z0HBAPI_TRAVEL" - in
"/SIE/AD_Z0H_BAPI_TRIP_MENU_EP".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 164
of the (Include) program "/SIE/LAD_Z0HBAPI_TRAVELU09".
I am from level 1 and as per my knowledge there is no change done on the system recently.
Please guide further.
Regards,
uday.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sriram,
I can see Generic buffer swaps to be 113 in st02.
The parameter values are as below :
Buffer Name Comment
Profile Parameter Value Unit Comment
Generic key table buffer TABL
zcsa/table_buffer_area 1073741824 Byte Size of generic key table buffer
zcsa/db_max_buftab 200000 Max. number of buffered objects
Uday
Hi,
Also , from RZ20 , it is seen that
Screen
DirectoryUsed 42 % , Green 10.08.2014 , 15:18:09
SpaceUsed 95 % , Yellow 10.08.2014 , 15:18:09
HitRatio 100 % , Green 10.08.2014 , 15:18:09
Swap 0 /min, Green 10.08.2014 , 15:18:09
and this is also sowing the same reason..the GENERIC KEY BUFFER SWAPS.
Hi Uday
Could you refer the SAP note for the Error message "Anmeldung nicht möglich (Fehler bei der Lizenzprüfung)"(German) = "Unable to login (error in license check)" (English)
1512766 - Most common reasons for error message: "Logon not possible (error in license check)"
BR
SS
Share dev_ms and dev_w0.
Also, check your kernel and file system.
Did you made any changes to your system?
Also, tell us os/db Kernel and product details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Referhttp://service.sap.com/sap/support/notes/1695293
Check your kernel and dbsl. Also tablespace.
If possible revert back changed you have done to your system.
Hello Sriram,
As said in the note 1532367 , the hourglass is shown for the last half an hour while checking the dev_w* logs from the system-se38.
The RDISP/TRACE_LOGGING parameter info as per the system:
rdisp/TRACE_LOGGING
Short Description (Engl.) Switch on/off trace logging
Application Area General system
Parameter Type Character String
Changes allowed Change generates warning
Valid for Operating Sys. All operating systems
Default Value on, 50 m
Profile Value on, 50 m
Current Value on, 50 m
Thanks,
uday
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.