Gateway crashes – RFCs no longer possible
[car crashes] [crashes] [fastest possible] [possible]
- MSCS: Cluster Resource Monitor Crashes on W2K3 SP2Symptom After upgrading Windows Server 2003 to SP2 or while installing the MSCS services on Windows Server 2003 SP2, the SAP resource fails when you try to bring it online. In addition,...
Symptom
The SAP Gateway crashes frequently. As a result, RFC communication may no longer be possible.
The trace file of the gateway dev_rd repeatedly contains the following C stack (or similar):
C-STACK
[0] GwIsMyHost ( 0xffff6f601278, 0×100f27666, 0×40, 0xffffffffffffffff, 0×70, 0×7 ), at 0×1000f3d90
[1] GwISendConnReq ( 0×1, 0xffffffff7fff586f, 0×2, 0xffffffff7fff576a, 0xffffffff7fff571f, 0xffffffff7fff575c ), at 0x
[2] R3ALLC ( 0×1, 0×100f26fb0, 0xffffffffffffffff, 0×1, 0×1, 0xffffffff7fff586f ), at 0×100134ac0
[3] GwCommunication ( 0×1, 0×0, 0×100f26fb0, 0xffffffffffffffff, 0×4, 0×1 ), at 0×10012e878
[4] GwIHandleRq ( 0×0, 0×0, 0×0, 0×100f26fb0, 0xffffffffffffffff, 0×100f27020 ), at 0×10009fbbc
[5] GwSendToRemGw ( 0×4e1, 0xffffffff7fffeb4c, 0×0, 0xffffffff6dd55510, 0×0, 0×1 ), at 0×10015ec0c
[6] GwIHdlRqFromSapWp ( 0×0, 0×0, 0xffffffff7fffeb4c, 0×4e1, 0×1, 0×0 ), at 0×10015aad4
[7] GwHdlRqFromSapWp ( 0xffffffff7fffe900, 0×1, 0×0, 0xffffffff7fffeb4c, 0×4e1, 0×1 ), at 0×1001595ac
[8] GwReadSapWpRq2 ( 0×0, 0xffffffff7fffeb48, 0×1c, 0×0, 0xffffffff7fffeb44, 0xffffffff7ffff4c0 ), at 0×10016c42c
[9] GwReadSapWpRq ( 0×0, 0×100d89c70, 0×1, 0×0, 0×0, 0×2 ), at 0×10016c258
[10] nlsui_main ( 0×4, 0×100b8e1b0, 0×1a11e8, 0xffffffff7e9085bc, 0xffffffff7df00780, 0xffffffff7df007c0 ), at 0×10008
[11] main ( 0×4, 0xffffffff7ffff6a8, 0xffffffff7ffff6d0, 0xffffffff7e14aea8, 0xffffffff7df00700, 0xffffffff7df00740 ),
Reason and Prerequisites
This error occurs only as of a specific kernel patch level.
7.00: Patch Level 209
6.40: Patch Level 277
This error does not occur in Releases 46D and 7.01.
Solution
This problem is solved by a kernel patch. Apply a kernel patch with the number that is specified under “SP Patch Level” or with a higher number. This will be made available on SAP Service Marketplace in the course of calendar week 27.