Not enough server storage is available to process this command

  • Thread starter Thread starter Tom Penharston
  • Start date Start date
T

Tom Penharston

I have an Active Directory domain in 2000 native mode. I run all
managment tasks from a DC with Server 2003 Standard Edition. From
Active Directory Users and Computers I attempt to manage a few random
clients each day to verify the secure channel.

When I try to manage a client there are two possibilities (1) The
computer management snap-in will appear immediately if the secure
channel is okay, or (2) The machine is turned-off, disconnected from
the network, or remote connections disabled - resulting in a long delay
and an error dialog, followed by an empty msc window.

Today I have a third possiblity, (3) an error dialog immediately
appears:

Computer \\computername cannot be managed. Not enough server storage
is available to process this command. Choose connect to another
computer from the action menu to manage a different computer.

After researching this message, I find that it is only documented for
Windows NT:
http://support.microsoft.com/kb/q126401/
http://support.microsoft.com/kb/225782/EN-US/

Two of my XP clients are displaying this message. I'm not too worried
about the XP clients, because I can re-image the boxes.

In the long run I just want to know why I'm getting NT error messages
from administering XP on 2003. Are NT messages still fair game? For
Active Directory? For WMI?
 
Good question. I've seen this issue on some of our older-hardware server
systems -I don't manage clients and can't remember seeing this back when I
did. Rebooting usually sorts it out. The question is why? What is causing
it? Too be honest, I can't remember what the problems were caused by, or in
the past I've been too busy to care. There are a lot of things that can
cause such things. I've simply rebooted, adjusted the page size and checked
the event logs.
 
This could be any number of things because it simply means the box is out of
whatever resources are needed to process the command.

The only time I have seen this when using ADUC however is if the person doing it
is a member of a buttload of security groups. Never got to dig in and
troubleshoot it though.


--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm
 
Sometimes, restarting the server service resolves this problem.
I've also seen this before when connecting to a file server, and in that
case McAfee was responsible for this, but this was fixed later with a patch
from McAfee.
Rebooting the system always solves this.
Peter
 
I have an Active Directory domain in 2000 native mode. I run all
managment tasks from a DC with Server 2003 Standard Edition. From
Active Directory Users and Computers I attempt to manage a few random
clients each day to verify the secure channel.

When I try to manage a client there are two possibilities (1) The
computer management snap-in will appear immediately if the secure
channel is okay, or (2) The machine is turned-off, disconnected from
the network, or remote connections disabled - resulting in a long delay
and an error dialog, followed by an empty msc window.

Today I have a third possiblity, (3) an error dialog immediately
appears:

Computer \\computername cannot be managed. Not enough server storage
is available to process this command. Choose connect to another
computer from the action menu to manage a different computer.

After researching this message, I find that it is only documented for
Windows NT:
http://support.microsoft.com/kb/q126401/
http://support.microsoft.com/kb/225782/EN-US/

Two of my XP clients are displaying this message. I'm not too worried
about the XP clients, because I can re-image the boxes.

In the long run I just want to know why I'm getting NT error messages
from administering XP on 2003. Are NT messages still fair game? For
Active Directory? For WMI?
Click to expand...

See tip 6288 » You experience connectivity issues after you install Norton AntiVirus 7.51 on Windows 2000 Server?
in the 'Tips & Tricks' at http://www.jsifaq.com

See tip 5584 » Backup fails to complete successfully and Event ID 1450 may be logged?

Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com
http://www.jsifaq.com
 
"...this was fixed later with a patch from McAfee"

The XP clients were hung-up on McAfee. The McAfee icon in the
Notification Area displayed the strike through icon, indicating that
the product was disabled. I don't know if this connects directly to
what you described, but it seems close enough.

The clients did not restart without a fight, McAfee was trying to run
and I suspected other services. Finally I could restart; after boot
the secure channel worked through computer management without errors.

The original message still makes no sense, "Not enough server storage
is available to process this command". I really don't see the
connection. I checked the hard disks of the failed clients: hard disks
were not full.

Thanks for all of the responses.
-Tom
 
More information:

Client Computer, XP SP2
Application Log
Source:McLogEvent
Type: Warning
Event ID: 5028
VirusScan McShield service recieved an inalid filename from the
NaiFiltr device driver.
Received name = \MacDrive
Process = MACVNTFY.EXE

My logical conclusion:
This looks like a conflict between "Media Four MacDrive 6" and McAfee
Virus Scan.
-Tom
 
Back
Top