2584074 - Update requests stuck in sm13, enqueue lock entries remain after end of session on Windows | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2584074 - Update requests stuck in sm13, enqueue lock entries remain after end of session on Windows

Symptom

  • Some enqueue locks in SM12 are not released automatically, though the enqueue owner already logged out. These enqueue locks block other business transactions.  
       
  • Lots of update requests in sm13 in ‘Initial’ status and cannot be processed. Enqueue keys belong to the update requests can be detected in sm12 enqueue lock list. And if you manually repeat these ‘Initial' status requests, then these requests might be pending on 'Started' status or 'Auto(dia)'. 
  • Find Update server from 'Update Header' of update request. Select the update request, find menu 'Goto' -> 'Update header' or click 'Top Hat' icon to see update server as follow:
       
    update header2.jpg
    Figure 1: Update Header

    Update Sever.jpg
    Figure 2: Update Server

    Then go to the update server and find corresponding update work process trace, you might see following log:

    M SosICreateNewAnchorArray: created new imode anchor array for T24_U1008_M0_I0 with 11 slots at 0x000007DFBAE02DD0
    X [esnti.c 2926]MapViewOfFileEx(27c,34,0,1275068416,4194304,000007DE99A00000) returned 0000000000000000
    X Mon Jan 29 18:49:58:360 2018
    X *** ERROR => <EsNT> error: [esnti.c 2926]MapViewOfFileEx(27c,34,0,1275068416,4194304,000007DE99A00000) returned 0000000000000000
    (lastError = 1455) [esnti.c 3541]
    X {root-id=FA163E4942951ED8819C4454E325842F}_{conn-id=00000000000000000000000000000000}_0
    X *** ERROR => <EsNT> MapViewOfFileEx size=4194304 ptr=000007DE99A00000 HighPart=0 LowPart=1275068416 MapHandle=000000000000027C error=1455 [esnti.c 2939]
    Y *** ERROR => dyInitSpa: EmAlloc failed [dyimode.c 2703]
    M ***LOG R1U=> Error in EmAlloc& [dyimode.c 2709]

    Next, follow-on errors of the following type usually occur in the same work process trace.

    X  [esnti.c 2893]VirtualFree(000007DE99A00000,0,32768) returned 0
     *** ERROR => <EsNT> error: [esnti.c 2893]VirtualFree(000007DE99A00000,0,32768) returned 0
    (lastError = 487) [esnti.c      3541]
    X  {root-id=FA163E4942951ED8819C461526FB442F}_{conn-id=00000000000000000000000000000000}_0
    X  *** ERROR => <EsNT> VirtualFree error=487 Slot=324 LocMapSlot=0 address=000007DE99A00000 [esnti.c      2901]
    Y  *** ERROR => dyInitSpa: EmAlloc failed [dyimode.c    2703]
    M  ***LOG R1U=> Error in EmAlloc& [dyimode.c    2709

    In this case, error code 487 means:
    C:\>net helpmsg 487
    Attempt to access invalid address.
    From the trace, session initialization has an error due to Extended Memory allocation failed.

  • The external symptom is the same with symptom described in KBA 2322108, but reason is different. It will happen even if we have reserved Extended Memory for session initialization. It’s only occurs on Windows operating system platform. Repeating 'Initial' requests cannot resolve the issue.

Read more...

Environment

NetWeaver Kernel 7.4x

Product

SAP NetWeaver 7.4 ; SAP NetWeaver 7.5

Keywords

LOAD_NO_ROLL, STORAGE_PARAMETERS_WRONG_SET, enqueue not released, update in ‘Initial’ status, 'Started', EM dump, Init, block, lock, windows, paging file exhaust , KBA , BC-OP-NT , Windows , BC-CST-UP , Update , BC-CST-EQ , Enqueue , BC-CST-MM , Memory Management , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.