Avatar of fisher_king
fisher_king
 asked on

Resource-Exhaustion-Detector Event 2004 on Server 2008R2

I am helping a client with a software upgrade on their server. One of the updates failed and when I tried to re-install it I got an error that the C drive was full. I decided to move the page file to the D drive to free up space - I originally configured it with 800 MB on the C drive and System Managed on the D drive. I did not know it until later today, but that triggered regular Resource-Exhaustion-Detector Event 2004 errors in the System log:

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: sqlservr.exe (3016) consumed 749858816 bytes, dns.exe (2140) consumed 247664640 bytes, and dsm_om_connsvc64.exe (4860) consumed 220897280 bytes.

It is always the same 3 programs, but none are using a significant amount of space. I have tried moving the page file back to C, making it system managed, static size, and specified range. I have set it to have no page file, deleted the page file, then re-created it more than once. Currently (after deleting the page file), it is set to 800 MB on the C drive and 32-48 GB on the D drive - and I have verified the size and presence of the page files using SpaceSniffer. The server has 32 GB of RAM and 4 x 100 GB SSD in Raid 5. It is used for AD, SQL 2008, and file server.

How can I resolve the issue without re-installing Windows?

Thanks in advance
Windows Server 2008Microsoft SQL Server 2008

Avatar of undefined
Last Comment
fisher_king

8/22/2022 - Mon
Robin CM

SOLUTION
Robin CM

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
ASKER CERTIFIED SOLUTION
fisher_king

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
fisher_king

ASKER
I used process monitor, but it did not reveal SQL to be using all the virtual memory - it was only by disabling the service that I discovered the cause.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23