When logging in to my file server with Remote Desktop, I occasionally get a message saying, "Insufficient system resources exist to complete the requested service" and it fails to load my profile. I started getting this message a few months ago, at the same time that other weird and intermittent problems started occurring, like the occasional inability to open or download larger files from the server. Sometimes Remote Desktop can't connect at all, and I have to locally log into the server's console.
I've seen this message intermittently on several desktops; last year half a dozen desktops in different departments with little in common (besides the hardware and the antivirus software) all started getting this message along with general instability and graphical glitches; it went away on its own after a couple of months. Every computer that had this problem, including the file server when it first started, seemed to have lots of handles open according to Task Manager (>100k instead of the usual 20-30k). Most, though not all, were running some ancient software with lots of bugs. But now it's happening on a server that is using almost no resources: Both hard drives are less than half full; the commit charge is less than 1.5 GB on a system with 4GB RAM; the processors are <5%; the number of open handles is <20k.
What other resources are there that might be depleted? How might I find out, since the system doesn't seem inclined to tell me? Or is this a generic catch-all message meaning "I don't know what the $%^& is wrong"?
I do get an occasional event log message, a couple of times a week, saying, "The server was unable to allocate from the system paged pool because the pool was empty." It doesn't seem to correlate at all with the other symptoms, though. I have no idea what causes it, or what the system is trying to do at the moments this message appears. When I google this message, I only find vague suggestions to make sure all my software and service packs are up to date. It is. This may be related or may be a red herring, but I'm not sure how to investigate it further since windows gives no details.
That phrase makes me very uncomfortable. This computer does not match the specific specs listed, but I'm still being asked to change a registry setting which I don't understand, which microsoft doesn't explain in their own kb article about it, and which can break things very badly and immediately if it's set wrong, bringing down a critical production machine.
– Josh Oct 20 '09 at 18:54http://blogs.technet.com/markrussinovich/archive/2009/03/26/3211216.aspx
However, I'm gonna go out on a limb and guess that the limit is 128 MB, because that would mean we're running close to the limit, which supposedly we are.
To be continued, after I try the above suggestion to raise the limit and add a safety margin.
– Josh Oct 20 '09 at 19:18