Can the Event ID 2004, Resource Exhaustion cause a problem in RDP? RRS feed

  • Question

  • Yesterday we were moving on to a new App Server (A SAP-Like ERP) version and during the Upgrade phase of the App, we got more than 50 times, the message about: Windows successfully diagnosed a low virtual memory condition. The message has repeated during a 13 hours period, while developers were working actively at  the upgrade, changing binaries, etc

    Some minutes ago, developers reported a lack of access. ping and SMB/CIFS wwa OK, OS was ok, but RDP it was not responding properly. After typing the password, the MSTSC client screen has been closed to type the password again, no clear error message. At first, we tought it was rebooting, but after some time, we saw the 2004 ID messages, regarding low memory, 3 main .EXEs eating up 25% more than the available RAM (dynamic pagefile allocation)

    The questions is:

    It´s possible to co-relate the lack of RDP access with the low memory condition? It´s reasonable to think about OS neglecting RDP access as a form to deal with the low memory condition?

    If so... WHy was RDP Ok, in the first 12 hours of low-memory conditions, no one complained about RDP problems, and only in the last 30 minutes of the low-memory condition, developers were suffering RDO problems?

    Maybe because they were already connected to RDP  and only after trying new RDP connections, the problem arises?

    Full mesage, 16 GB of RAM Server, fully patched and very (very) good availability over the year

    The following programs consumed the most virtual memory: dbaccess64.exe (4212) consumed 11759382528 bytes, ctsrvr.exe (560) consumed 6648963072 bytes, and appserver_TI.exe (3668) consumed 4486569984 bytes.

    • Edited by KayZerSoze Saturday, April 20, 2019 6:07 PM typo
    Saturday, April 20, 2019 6:03 PM