« Previous Next »

• 06-16-2009, 3:44 PM

  jalmto Joined on 12-05-2006, 9:08 AM Posts 2

  Publishing to WS2008 WEB, IIS 7 Problem Reply Contact Hello, I am using VS 2008 to the named server above.  I am trying to publish via a mapped drive to a shared folder.  I have always done it this way and it works very well on our 2003 boxes.  However, this beast is another story.  What happens is our projects only partly publish then some files will recieve "Not enough server storage is available to process this command."  The weird thing is, if I process the publish command like five times in a row, I will eventually get the whole thing published. I don't know if this is an IIS issue or a WS2008 issue.  Can anyone help me??

• 06-17-2009, 2:03 AM

  In reply to

  Gabriel_EUK Joined on 10-05-2008, 10:27 AM Posts 140

  Re: Publishing to WS2008 WEB, IIS 7 Problem Reply Contact Hi jalmto, this is a known issue with shared network resources and mostly you face this error message when you share a network drive :) well its easy to fix it by changing the value of IRPStackSize parameter in registry at  HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ lanmanserver \ parameters  normally its value varies from 1 to 50. Increase its value than that is set currently, reboot the box and try again. In case if the problem persist you need to increase its value again. Gabriel ---------------- ASP .NET - MSSQL WebHosting My Hosting Solution Blog

• 06-17-2009, 2:05 AM

  In reply to

  Gabriel_EUK Joined on 10-05-2008, 10:27 AM Posts 140	Re: Publishing to WS2008 WEB, IIS 7 Problem Reply Contact most importantly if IRPStackSize is not present at HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ lanmanserver \ parameters then you will need to create it manually as DWORD Gabriel ---------------- ASP .NET - MSSQL WebHosting My Hosting Solution Blog

• 06-17-2009, 9:19 PM

  In reply to

  jalmto Joined on 12-05-2006, 9:08 AM Posts 2	Re: Publishing to WS2008 WEB, IIS 7 Problem Reply Contact Hello, and thank you for your reply.  However, I added this value and have reached the MAX of decimal 50 and the problem persists. I am not sure if I mentioned it in my first post but the O/S is Windows WEB Server 2008 on a 64-bit platform. I am ready to throw this thing out the window!