Results 1 to 6 of 6

Thread: "Not enough storage is available to process this command"

  1. #1
    Join Date
    Oct 2005
    Posts
    80

    "Not enough storage is available to process this command"

    After performing fresh Windows 2000 updates I found that there is a error while initiating some commands. I am trying to map a shared network location first on the new updated system. It gave me a error no enough storage for command. What does that means. All the workstations on the network are able to access the same drive and not getting any kind of errors. Only the system that I am using is having this problem. Any suggestions on that will be quiet helpful.

  2. #2
    Join Date
    Sep 2004
    Posts
    151

    Re: "Not enough storage is available to process this command"

    I do not think updates has made changes to your system access on the network. There might be some other issue. I will advice you to contact your network admin and ask for help. It will provide you options to deal with issues. First all the error which you are receiving it bit weird. I am getting a similar error recently which was related to disk space. The system was not having enough space for initiating a process.

  3. #3
    Join Date
    Sep 2004
    Posts
    125

    Re: "Not enough storage is available to process this command"

    Here is a helpful KB article link that will provide you more info on what you are looking for. The problem lies with IRPStackSize. If it is set low then you get that error. And somehow Windows Updates can imply some changes to the system. The changes is done on Windows registry. The below link will provide you a method to get rid of the issue. For that you have to modify your system registry file. It is necessary that you take proper backup before doing the same.

    Error message: "Not enough server storage is available to process this command"

  4. #4
    Join Date
    Sep 2004
    Posts
    156

    Re: "Not enough storage is available to process this command"

    Thanks for that link. I was facing the same issue and it really worked. It looks to be working fine. I just want to know the exact reason. What does that IRPStackSize means. Does modifying the registry will not cause any other impact on the internal system. It can be helpful to troubleshoot this kind of issues if appear in future.

  5. #5
    Join Date
    Sep 2004
    Posts
    150

    Re: "Not enough storage is available to process this command"

    If you need to find information on IRPStackSize. The link below has detailed information on it. You can read and surely this is going to help you in future for number of issues. Somehow the changes can cause affect in the system performance. I will recommend you to check all the workstation one by one if you found this kind of error.

    Description of the IRPStackSize parameter in Windows 2000, in Windows XP, and in Windows Server 2003

  6. #6
    Join Date
    Sep 2004
    Posts
    119
    Just for once verify in disk management that the drive you are trying to connect is having enough space. You must check in the server for that. Somehow it is also due to low disk quota alloted. You must extend that to get rid of that error. That is the failsafe way to verify first before making any changes to the system registry.

Similar Threads

  1. Sharing error - Not enough server storage to process command" ???
    By Chad Gross in forum Windows XP Support
    Replies: 1
    Last Post: 21-03-2013, 03:31 PM
  2. Replies: 2
    Last Post: 20-04-2009, 09:57 PM
  3. "not enough storage is available to process this command" stops in
    By Billie in forum Vista Setup and Install
    Replies: 6
    Last Post: 17-02-2009, 07:16 PM
  4. "Not enough quota to process this command"
    By Marco in forum Vista Help
    Replies: 1
    Last Post: 12-03-2007, 11:43 PM
  5. Replies: 2
    Last Post: 07-12-2006, 05:56 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,543,562.89997 seconds with 17 queries