drive not accessible not enough server storage is available to proccess this command

drive not accessible not enough server storage is available to proccess this command

Post by Jon Strau » Wed, 08 Feb 2006 16:52:41


I don't think the error really points to the problem. I looked it up on
interned and tried many of the solutions with no avail.

the key is that the share of the drive that is shared on computer 1 is not
accessable through my network places on computer 1 nor any other computer.
yet all of the other computers shared drives are accessible. and the
printers are accessible from computer 1.

back ground. I have a domain. with server sms 2003. and all computers on
xp professional.

i've check all permissions and security settings. I'm logging on to other
computers as same user an admin of domain.

If I create a new share on additional drive, I have same problem.

only on this one computer. shared drives are not accessible by itself or
any other computer.

It may be related to fact I can't alter firewall setting on this computer.
seems to be controlled by server 2003, even though server firewall is not
setup because I didn't have 2 nic cards.

any suggestions.

thanks

jon
 
 
 

drive not accessible not enough server storage is available to proccess this command

Post by Hans-Georg » Wed, 08 Feb 2006 17:37:55


Jon,

check http://www.yqcomputer.com/ :

I get the error message: Not enough server storage is available
to process this command. Not enough memory to complete
transaction. Close some applications and retry.

I cannot access network shares. On the Windows server the system
event log may contain Event ID: 2011, Source: Srv

Hans-Georg

--
No mail, please.

 
 
 

drive not accessible not enough server storage is available to proccess this command

Post by Jon Strau » Thu, 09 Feb 2006 01:39:25

interesting site. but no help. this lead to what I have already found.
there are two registry points that have been mentioned in forums.
IRPStackSize and PagedPoolSize.

I have checked both of these and they are set correctly.

I also ran across someone who have this problem and found that it was caused
by a raid card.

I have raid 1 for my main drives. I can check I have other drives that are
not in the raid array.

thanks

Jon