NOT ENOUGH SERVER STORAGE IS AVAILABLE TO PROCESS THIS COMMAND

  • Thread starter Thread starter RICH
  • Start date Start date
R

RICH

I HAVE A THREE COMPUTER WINDOWS XP HOME EDITION NETWORK.
I HAVE A DRIVE MAPPED AS (F:) FROM ONE OF THE PC'S TO THE
OTHER TWO. ONE OF THE PC'S CAN ACCESS THE F: DRIVE, WITH
NO PROBLEM. THE OTHER PC GETS THE FOLLOWING ERROR WHEN I
DOUBLE CLICK THE MAPPED DRIVE..."NOT ENOUGH SERVER
STORAGE IS AVAILABLE TO PROCESS THIS COMMAND". I CHECKED
LOCAL DISK SPACE, AND THE AMOUNT OF DISK SPACE ON THE
SHARED NETWORK DRIVE, BOTH HAVE OVER 4 GIGS FREE. IF YOU
HAVE AN ANSWER FOR THIS PROBLEM IT WOULD BE GREAT IF YOU
COULD HELP.
 
RICH said:
I HAVE A THREE COMPUTER WINDOWS XP HOME EDITION NETWORK.
I HAVE A DRIVE MAPPED AS (F:) FROM ONE OF THE PC'S TO THE
OTHER TWO. ONE OF THE PC'S CAN ACCESS THE F: DRIVE, WITH
NO PROBLEM. THE OTHER PC GETS THE FOLLOWING ERROR WHEN I
DOUBLE CLICK THE MAPPED DRIVE..."NOT ENOUGH SERVER
STORAGE IS AVAILABLE TO PROCESS THIS COMMAND". I CHECKED
LOCAL DISK SPACE, AND THE AMOUNT OF DISK SPACE ON THE
SHARED NETWORK DRIVE, BOTH HAVE OVER 4 GIGS FREE. IF YOU
HAVE AN ANSWER FOR THIS PROBLEM IT WOULD BE GREAT IF YOU
COULD HELP.
Click to expand...

This error indicates that you are falling foul of the IRPStackSize bug.

The problem is on the machine you are attempting to connect to,
not the machine where you see the error message.

On the computer you are attempting to connect to,
Check the event viewer for an event ID 2011.

Usual fix :
You need to fix a parameter called IRPStackSize

On the computer you are attempting to connect to,
Set the IRPStackSize back to the default (15 ).
Perform the following steps:

1. Start the registry editor (e.g., regedit.exe).
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\lanmanserver\parameters.
3. Double-click IRPStackSize
(or if this registry setting doesn't exist,create it of
type DWORD and ensure the case is correct).
4. Change the base to decimal, set the value to 15, and click OK.
5. Reboot the computer.

Norton AV is usual suspect for breaking it.

There's a KB article about this, too.

Antivirus Software May Cause Event ID 2011 (Q177078)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;177078

PS: ALL CAPITAL LETTERS IS HARD ON THE EYES!
 
Back
Top