Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Server Too Busy in vs2012

I've got vs2010 and vs2012 installed side by side. If I open up our MVC site in vs2010 and run it using the development web server it works fine, if I do the same thing in vs2012 I get "Server Too Busy" every single time for the first request to the site. Every request after the first request works fine.

Update: I've noticed in vs2012 it only happens of the project needs to build. If I haven't made any changes, ie the project doesn't need to build and I hit F5 to start it up and open up IE it works fine and I don't get the "Server Too Busy" message in the browser.

like image 204
ctrlalt313373 Avatar asked Dec 07 '12 21:12

ctrlalt313373


People also ask

What causes server busy?

a. The 'server busy' message is appearing because the program is trying to access the internet before the connection is completely ready.

What does server too busy mean?

RESOLUTION. The “Server Busy” message is a Windows error prompt, NOT a CuteFTP message. This message appears whenever there is a resource conflict between two processes in Windows and one of the processes will not release the required resource so that it can be used by another process.


2 Answers

I have had this problem for my ASP.Net solution as well. There were no solutions for this problem on Stack Overflow or anywhere else.

Setup:

Visual Studio 2013 (but I think it will also work for vs 2010/2012 ASP.Net web application IIS express setup).

Our production environment never had this problem because it was running on IIS.

I have tried a lot to fix it, but I found one specific solution. I set the delayNotificationTimeout to 20 seconds, instead of the default of 5, which was not enough for our solutions to conjure up everything it needed to successfully run.

<system.web>     <httpRuntime maxRequestLength="104850"                   executionTimeout="600"                   enableVersionHeader="false"                   delayNotificationTimeout="20" /> </system.web> 
like image 55
Noldy Avatar answered Sep 17 '22 17:09

Noldy


just clean the solution before you build it. Also, check the size of the folder in which the solution is, before & after clean build; you will surely find some difference. Doing this ensures that you clean/remove unnecessary dlls created after every build which is the cause of delaying the normal flow.

like image 36
Sunil Padhi Avatar answered Sep 17 '22 17:09

Sunil Padhi