"Not enough storage is available to process this command ". Again.

  • Thread starter Thread starter Hilarious
  • Start date Start date
H

Hilarious

I have just started getting this error message on a W2000 workstation
startup after being told that my mapped connection to a shared drive
cannot proceed. When I attempt to connect from Explorer it says that
"<workgroup> is not accessible" for the same reason.

The third message in the event log said:
"Description:
The browser was unable to retrieve a list of servers from the browser
master \\MOTLEY on the network \Device
\NetBT_Tcpip_{F3EBA155-9F91-4CF1-9F50-F7A10D7652E0}. The data is the
error code.
Data:
0000: 08 00 00 00"
.... which must have given rise to this problem. \\Motley is alive and
well and in use across the network as I write.

I have read many threads and MS Support articles but no proposed
changes stopped the message.
It also appeared when I restarted in 'Safe with networking' mode which
surprised me as I thought that windows' various caches/heaps/handle
counts would be very low indeed and wouldn't trigger this error.

Can someone help me get this sorted, please?

Hil
 
When you view the logged events in Event Viewer (double-click them in the
right-hand pane) in the upper right corner, third button down is a copy to
clipboard, then you can paste in the body of a reply message.

Please do so for each of the different System Log events (that are a Type:
'Error' or 'Warning') since last boot so we can see all of the event detail.

Also check Device Manager for error codes and or non-starting devices.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Solved: The error arose from the shared machine being unable to
respond due to a VAST Wireshark logging file hogging all its memory
and pagefile space. It was responding very slowly to keypresses and
it took a partial (arrested) shutdown to close WS down. After this a
(now) quick look at the Task Manager showed the tail end of a dramatic
reduction in MEM usage...

Many thanks for helping me with this. I'm sorry if I wasted your
time.
 
Back
Top