Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On our production server we get the following message when we log in after 1 week uptime

Windows cannot load the user's profile but has logged you on with the

default profile for the system.

DETAIL - Insufficient system resources exist to complete the

requested service.

System specs

Windows 2003 SP 2 32bit
Intel Xeon E5420
PAE enabled

Our production System has a SQL Server 2005 running (~1.7GB RAM all the time) and the application consists of 40 Java processes consuming ~2.7GB
There are over 3GB of RAM free.

To get rid of the problem temporarily we have to reboot.

share|improve this question
Event ID number(s)? The only reference I'm finding off Microsoft with cursory google-fu points to this issue on Win2K with Symantec Antivirus running. Also, is anything pegged in the process monitoring, like CPU? What does Process Explorer say for interrupt usage, I/O, anything that looks to be thrashing or spinning out of control? – Bart Silverstrim Aug 10 '10 at 11:29
Are you using the /3GB switch in your boot.ini file? If you are that's the most likely cause of the problem. – joeqwerty Aug 10 '10 at 12:25
@joeqwerty /3GB is diabled – peter Aug 11 '10 at 16:01
@Bart Silverstrim ID is 1505 also there is a second entry that says that the registry can't be loaded (id is 1508) All Cores are at 50% usage max. One Java process uses 2 cores all for itself (but it has done this before the errors showed up) – peter Aug 11 '10 at 16:09
It's not a lack of physical memory, it's a lack of kernel memory. That's why I asked about the /3GB switch. If you use the /3GB switch you limit kernel memory to 1GB which can cause this problem. Since you're not using the /3GB switch then it's not the cause of your problem. I would take a look at the Pool Nonpaged bytes memory counter in perfmon and see where it's at. On a 32bit, unadulterated Windows system with more than 1GB of RAM the Pool Nonpaged bytes is limited to 256MB. The Nonpaged Pool memory is shared by the kernel, device drivers, system PTE's and the file system cache. – joeqwerty Aug 12 '10 at 12:21

These seem to pertain primarily to Terminal Services, but maybe they could help you here?

share|improve this answer
i have to try that. thanks. I'll be able to do that next week (i hope) – peter Aug 12 '10 at 11:54

I'd be interested to see what would happen with a 64bit OS.

It smacks of possibly being paged/non-paged pool related.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.