Hi experts, I got "Not enough server storage is available to process this command" error on server which also cause to disappear shares, I checked all related services which are in running states. Did not get any eventid which point to irpstack issue. Even when I try to run net statistics server command I got the same error. Once I reboot the server error goes. Please can anyone provide me the permanant fix for this error as it is not possible for me to reboot server everytime. Regards, Shashi

It is most like the IRPStack issue even without the corresponding Event ID. The IRPStackSize controls the amount of number of stack locations in I/O request packets (IRPs) for applications on the OS. http://support.microsoft.com/kb/285089 I would increase the value of this to be between 30 and 50 (decimal) and reboot your server for the change to take affect. >>>Even when I try to run net statistics server command I got the same error This is an application requesting I/O....fits the IRPStack issue. >>>Once I reboot the server error goes. After a reboot you have freed your IPRStack usage. Overtime as you applications start to work, you deplete your IRPStack.

Do you have any third party applications installed on this computer? Anti-virus? Take a look at this article: http://support.microsoft.com/kb/177078 Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

Hi All, I have set the irpstack settings which did not helped me. I cannot proceed the solution provided by Wilson as my server is in production. One more thing I would like to share about the issue. I cannot browse \\servername UNC path whereas I can access the \\servername\<shared folder> from network. Regards, Shashi

Did you figure this issue out? I'm running into the exact same problem... Cheers, Ben

Does anyone found the solution for this? I am still working with the workaround of rebooting the serverShashi

Strangly enough, in my case it was an issue with firewall settings (NOD32 was not configured correctly, OK when folder sharing was allowed in the firewall settings)