Not enough server storage is available to process this command

  • 61 Views
  • Last Post 17 September 2015
MikeLeone posted this 17 September 2015

I have a Win2008 R2 DC, it's a physical box. It became unresponsive,
couldn't do anything with it but power cycle it. When it came back up,
I found a lot of Event ID 2004, Resource-Exhaustion-Detector errors.

When it rebooted, it did come back up normally. AD did start. However,
it's not replicating, with the error message

Not enough server storage is available to process this command

Searching around, I find KB recommendations to increase IRPStackSize,
or to set PagedPoolSize to 0. However, these are all really old
solutions, for Win 2003. And I don't know if they are still
applicable.

It's not disk space, I have 30G free. So it has to be some sort of
memory setting.

I just need this DC to be stable for a little while longer, then I can
gracefully demote it. Problem is, my phone system is set to reference
this DC (for DNS, WINS, etc), and I'm still waiting for my telecom
guys to fix this.

So: what would be the recommended course here? PagedPoolSize?
IRPStackSize? Something else I haven't found while searching?

show

Order By: Standard | Newest | Votes
ethierbach posted this 17 September 2015

Michael -- you didn't mention this, so I will, but I expect you've already checked it.
Does the server still have all the memory it used to?  I've seen servers lock up due to memory errors, then at reboot the server took the bad memory offline. Might be worth a check.
-Ed-


show

MikeLeone posted this 17 September 2015

Huh. I waited about an hour (had a meeting to go to), when I came
back, the replication errors had disappeared. Poof! All DCs
replicating fine.

Ed,I saw no memory errors during POST (not that that means anything,
of course), and it seems to have all the memory it used to.

Well, time to become the telecom folks yet again, before this happens
again. Of course, I could schedule a reboot every couple days, this DC
doesn't really do anything. And I have 3 others in that site ...

And once it's gone, I can raise the domain and forest levels. WooHoo! :-)
.

show

rwf4 posted this 17 September 2015

Did this just start happening? What changed???

There should be a good deal of detail in the 2004 event, look for in the xml

You can also look at the Windows Resource Exhaustion Detector (Resource-Exhaustion-Detector) under Applications and Services Logs for additional detail (
)

You should be able to determine exactly what's being bumped up against by reviewing that output

Assuming it's some sort of resource constraint, I'd look for what is starving the resources(think drivers, services, AV etc),

If something's leaking, by tweaking a setting, you may have just moved the threshold to failure if you don't know root cause.

show

MikeLeone posted this 17 September 2015

On Thu, Sep 17, 2015 at 2:45 PM, Free Jr., Bob wrote:

show

Close