We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-basis] my production server is getting restarted

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by Kumar
on 06/15/2009 02:44:00 AM

Thanks ,I have open the message with sap .Please let me tell you in details
On last Friday suddenly prd server restarted and in the event log bze of some process .And a mail form the server of HpEventLog: Watchdog timer expired - hard reset (2E0H)
Sorry of very long details error and log paste.
SNMP Trap: 736
Date time: 06/09/2009 01:14:54 PM
Computer:
Source: HpEventLog
Type: Error
Category: (0)
Description:
Watchdog timer expired, and a hard reset of the system occurred. Some process took longer than it should. Identify that process and contact the vendor of that application.
Than I start facing problem in sap.There server up but in sap the work process are getting stop
In the sm50 almost all work process are in stop process and if I restart it will stop again.
If we restart the application server manly it will work fine for only 10 to 12 hr than again the same problem will come.
And in night when there is no one to restart the application server manly it will restart automaticity in 1 to 2hr time fram
in this time period if some only try to run any t-code than it will get an ABAP dump.
Runtime Error MESSAGE_TYPE_X, START_CALL_SICK and TEXTENV_UNICODE_LANGU_INVALID.
Please find the details log of, Sm21 and log. Please suggest.
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 6/15/2009
Time: 10:42:08 AM
User: N/A
Computer: #####
Description:
Faulting application svchost.exe, version 5.2.3790.1830, faulting module netapi32.dll, version 5.2.3790.2769, fault address 0x00000000000987e0.

Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6013
Date: 6/13/2009
Time: 12:00:00 PM
User: N/A
Computer: #####
Description:
The system uptime is 56299 seconds.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011
Date: 6/13/2009
Time: 7:58:10 PM
User: N/A
Computer: #####
Description:
Timeout (30000 milliseconds) waiting for a transaction response from the SAPPRD_00 service.

Event Type: Error
Event Source: SAPPRD_00
Event Category: None
Event ID: 35712
Date: 6/15/2009
Time: 10:42:34 AM
User: N/A
Computer: #####
Description:
SAP Basis System: Operating system call recv failed (error no. 10054)
Event Type: Information
Event Source: EventSystem
Event Category: None
Event ID: 4625
Date: 6/15/2009
Time: 10:43:14 AM
User: N/A
Computer: #####
Description:
The EventSystem sub system is suppressing duplicate event log entries for a duration of 86400 seconds. The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\EventSystem\EventLog.

Event Type: Information
Event Source: SAPSGP_35
Event Category: None
Event ID: 0
Date: 6/15/2009
Time: 10:43:22 AM
User: N/A
Computer: #####
Description:
The description for Event ID ( 0 ) in Source ( SAPSGP_35 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: SAP Service SAPSGP_35 has been stopped successfully..

Event Type: Error
Event Source: SAPPRD_00
Event Category: None
Event ID: 35716
Date: 6/15/2009
Time: 10:43:40 AM
User: N/A
Computer: #####
Description:
SAP Basis System: Message server disconnected

Event Type: Error
Event Source: SAPPRD_00
Event Category: None
Event ID: 0
Date: 6/15/2009
Time: 10:43:49 AM
User: N/A
Computer:
Description:
SAPRC: System died. Reason: (null)

Event Type: Information
Event Source: SAPPRD_00
Event Category: None
Event ID: 0
Date: 6/15/2009
Time: 10:43:50 AM
User: N/A
Computer:
Description:
SAP Service SAPPRD_00 has been stopped successfully.

Event Type: Information
Event Source: SAPPRD_00
Event Category: None
Event ID: 0
Date: 6/15/2009
Time: 10:43:55 AM
User: N/A
Computer:
Description:
SAP Service SAPPRD_00 successfully started.

---------------------------------------------------
trc file: "dev_disp", trc level: 1, release: "640"
---------------------------------------------------
Mon Jun 15 09:04:02 2009
kernel runs with dp version 138000(ext=102000) (@(#) DPLIB-INT-VERSION-138000-UC)
length of sys_adm_ext is 524 bytes
sysno 00
sid PRD
systemid 561 (PC with Windows NT)
relno 6400
patchlevel 0
patchno 247
intno 20020600
make: multithreaded, Unicode, 64 bit
pid 5084

Mon Jun 15 09:04:03 2009
***LOG Q00=> DpSapEnvInit, DPStart (00 5084) [dpxxdisp.c 1110]
shared lib "dw_xml.dll" version 247 successfully loaded
shared lib "dw_xtc.dll" version 247 successfully loaded
shared lib "dw_stl.dll" version 247 successfully loaded
shared lib "dw_gui.dll" version 247 successfully loaded
shared lib "dw_mdm.dll" version 247 successfully loaded
Mon Jun 15 09:04:08 2009
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3882]
MtxInit: -2 0 0
DpSysAdmExtInit: ABAP is active
DpIPCInit2: start server >#####_PRD_00 <
DpShMCreate: sizeof(wp_adm) 57104 (1464)
DpShMCreate: sizeof(tm_adm) 35937968 (17960)
DpShMCreate: sizeof(wp_ca_adm) 80000 (80)
DpShMCreate: sizeof(appc_ca_adm) 160000 (80)
DpShMCreate: sizeof(comm_adm) 1248000 (624)
DpShMCreate: sizeof(vmc_adm) 0 (512)
DpShMCreate: sizeof(wall_adm) (416064/346352/64/192)
DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000D440050, size: 38252832)
DpShMCreate: allocated sys_adm at 000000000D440050
DpShMCreate: allocated wp_adm at 000000000D441C30
DpShMCreate: allocated tm_adm_list at 000000000D44FB40
DpShMCreate: allocated tm_adm at 000000000D44FB70
DpShMCreate: allocated wp_ca_adm at 000000000F695A20
DpShMCreate: allocated appc_ca_adm at 000000000F6A92A0
DpShMCreate: allocated comm_adm_list at 000000000F6D03A0
DpShMCreate: allocated comm_adm at 000000000F6D03C0
DpShMCreate: allocated vmc_adm_list at 000000000F800EC0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 000000000F800EF0
DpShMCreate: allocated wall_adm at 000000000F800F00
MBUF state OFF
Mon Jun 15 09:04:09 2009
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation flat
<EsNT> Memory Reset disabled as NT default
<ES> 1226 blocks reserved for free list.
ES initialized.
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 2.6 2.6 4.0) [dpxxdisp.c 1496]
***LOG Q0K=> DpMsAttach, mscon ( #####) [dpxxdisp.c 10467]
use SAPLOCALHOST=<#####> as internal hostname
DpStartStopMsg: send start message (myname is >#####_PRD_00 <)
DpStartStopMsg: start msg sent
Mon Jun 15 09:04:10 2009
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
CCMS: Checking Downtime Configuration of Monitoring Segment.
Mon Jun 15 09:04:11 2009
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 6400, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]
DpMsgAdmin: Set patchno for this platform to 247
Release check o.K.
Mon Jun 15 09:04:34 2009
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
Mon Jun 15 09:13:09 2009
*** ERROR => DpWPCheck: max_hold_time W0 exceeded (T45=HO ) [dpxxdisp.c 13343]
Mon Jun 15 09:34:49 2009
DpHdlDeadWp: restart wp (pid=5160) automatically
DpHdlDeadWp: restart wp (pid=616) automatically
DpHdlDeadWp: restart wp (pid=3100) automatically
DpHdlDeadWp: restart wp (pid=3104) automatically
DpHdlDeadWp: restart wp (pid=5772) automatically

Mon Jun 15 09:47:04 2009
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 793]
Network error of client T65, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Mon Jun 15 09:47:09 2009
Client address of T65 is 172.16.1.40(HODT155)
***LOG Q04=> DpRTmPrep, NiBufReceive (141) [dpxxdisp.c 10138]
RM-T65, U141, 600 , H5, 09:46:19, M0, W1, MIGO, 2/1
Mon Jun 15 09:50:59 2009
*** WARNING => NiAddrToHost took 6 seconds [dpxxdisp.c 17273]
Client address of T68 is 115.240.210.180(115.240.210.180)
***LOG Q04=> DpRTmPrep, NiBufReceive (68 pc1 ) [dpxxdisp.c 10138]
RM-T68, U162, 6 , pc1, 09:45:52, M0, W1, , 2/0
Mon Jun 15 09:54:49 2009
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 793]
Network error of client T68, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Mon Jun 15 10:04:11 2009
Client address of T73 is 115.240.210.180(115.240.210.180)
***LOG Q04=> DpRTmPrep, NiBufReceive (pc1 ) [dpxxdisp.c 10138]
RM-T73, U192, 600 , pc1, 09:58:57, M0, W5, MIGO, 2/1
Mon Jun 15 10:05:11 2009
DpHdlDeadWp: restart wp (pid=5608) automatically
DpHdlDeadWp: restart wp (pid=1236) automatically
DpHdlDeadWp: restart wp (pid=6008) automatically

Mon Jun 15 10:24:16 2009
*** ERROR => multiple send of tid 44 ( , M1) [dpxxdisp.c 10283]
Network error of client T44, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Client address of T44 is 192.168.13.228(h9.#####)
***LOG Q04=> DpRTmPrep, NiBufReceive (275) [dpxxdisp.c 10138]
RM-T44, U275, , 10:23:27, M1, W0, FBL3, 2/1
*** ERROR => DpRqCheck: mode 1 in status CANCEL [dpxxdisp.c 6055]
***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 4797]
*** ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5383): [dpxxdisp.c 4799]
-IN-- sender_id REMOTE_TERMINAL tid 44 wp_ca_blk 0 wp_id -1
-IN-- action SEND_TO_WP uid 275 appc_ca_blk -1 type DIA
-IN-- new_stat NO_CHANGE mode 1 len 33 rq_id 62366
Mon Jun 15 10:30:59 2009
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 793]
Network error of client T49, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Mon Jun 15 10:31:12 2009
*** WARNING => NiAddrToHost took 13 seconds [dpxxdisp.c 17273]
*** WARNING => DpAddrToHost: Disabling reverse name lookup [dpxxdisp.c 17275]
Client address of T49 is 115..72(.72)
***LOG Q04=> DpRTmPrep, NiBufReceive (323 49 pc1 ) [dpxxdisp.c 10138]
RM-T49, U323, 6 , pc1, 10:25:42, M0, W4, MIGO, 2/1
Mon Jun 15 10:31:32 2009
DpHdlDeadWp: restart wp (pid=4828) automatically

REgards,
Kumar
__.____._

Copyright © 2009 CEB Toolbox, Inc. and message author.

Toolbox.com
4343 N. Scottsdale Road
Suite 280
Scottsdale, AZ 85251

1 comments:

Nikitha said...

With the extensive use of the internet worldwide, we use different browsers to visit various web pages. Amidst this browsing, you might have come across the message that says “This Site Can’t Be Reached” or “The Connection Was Reset”. When Google Chrome or any other browser is redirected to some website, it could be due to several reasons. This “Connection Reset Error” creates trouble, causing interruption to work, thereby breaking our workflow. Sometimes by simply refreshing the page or restarting Chrome helps to overcome this Err_Connection_Reset error. err connection reset - fixingerror.com
But in certain cases, issues are not resolved and need to be worked out in-depth. Adopting some of these methods can be your saviour and allow you to work uninterruptedly.

Post a Comment

T r a n s l a t e to your language