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.
We've been having similar problems with our 2003 terminal server.
We receive lots of applications complaining with error message "Insufficient system resources exist to complete the requested service". And also receive events complaining about the paged pool memory.
It's been difficult however because many times the event log itself gets corrupted.
We've followed the steps at:
http://support.microsoft.com/kb/312362
The suggestions there have given us mixed results. The problem is less frequent, but not eliminated.
Presuming you're using 32 bit 2003 Server, you've depleted the paged pool in kernel address space.
If you're using the /3GB switch, removing it will help, or if you need more than 2GB of address space for an app, then use the /userva= switch to increase the amount of kernel address space as much as possible.
I understand that turning off PAE helps, but I've not tested this.
The long term solution is to migrate to a 64 bit OS. Even with the same amount of installed RAM, the problem disappears.
We had this issue with a Citrix farm. The users would not get their profile and the error "insufficient system resources exist to complete the requested service" and errors relating to the Group Policy service failing were seen.
Events 1500, 1502, 1506 in the system event log in particular.
The reason was not memory or disk resources but registry resources being depleted. The culprit was a printer driver of a particular manufacturer for a photocopier style printer. This was filling the registry .DEFAULT hive. HKEY_CURRENT_USER/DEFAULT. the file in c:\windows\system32\ should be quite small say 300mb but had inflated to nearly 2gb
The resolution was to delete the entries inflating this registry hive using regedit, then boot off a WinPE boot disk, take a backup of the .Default file and then use chkreg.exe to compress the registry hive back to normal size
Chkreg /f /c
For some reason I had to do this on another server with a copy of the .DEFAULT hive as chkreg just failed on the original server with the issue. But once transferred back and the original file overwritten and server rebooted, the problem was resolved. This just left the driver issue to be sorted before it inflated the registry again.