IIS 7 and Above
Web deployment task failed. Max number of connections
Last post Jun 12, 2018 10:20 PM by ManojPanwar
Oct 29, 2013 01:21 PM|Tor Krattebol|LINK
On a new Windows 2012 Server installation we have got the following error when users did Web Publish from Visual Studio 2012:
Web deployment task failed. (The maximum number of connections for this site has been exceeded.Learn more at:
It occurred when a number of Web deployments had been done. IIS restart did not remove the error. Restart of server did remove the error for some time before it occurred again.
The reference to the Learn More link does not list this error.
Oct 30, 2013 05:27 AM|Terry Guo - MSFT|LINK
Please try to refer to this thread:
Hope it helps.
Oct 30, 2013 12:07 PM|Tor Krattebol|LINK
Thank you for your reply. I have seen the StackOverflow item. It seems that the problem that is described there is a static one. That means it does not work initially. Our problem is a dynamic fault. We have several users doing successfully deployments and
suddenly every one gets the error and no one can deploy any more. After a reboot of the server, deployments can continue.
Nov 12, 2013 04:45 AM|CraigMellon|LINK
Did you resolve this issue, i've just started getting the same issue, after a number of deployments i'm getting the EXCEEDED_MAX_SITE_CONNECTIONS error
Nov 12, 2013 05:29 AM|CraigMellon|LINK
I have managed to fix this on my server by restarting the Web Management Service
Mar 16, 2014 09:55 PM|MarValUS|LINK
Did you ever get this fixed. I am getting same error on one of my sites after publish had a socket error.
Sep 16, 2014 10:32 AM|Tor Krattebol|LINK
No we have not solved this problem. After we started publishing again the problem still exists and we have not found any solution.
Sep 22, 2015 03:05 AM|yongfa365|LINK
In MS Deploy Server (IIS Server)
Windows Registry Editor Version 5.00
Mar 29, 2017 08:26 AM|Webio|LINK
I'm wondering does setting this param in registry fixes this problem? I'm managing shared hosting environment and I'm still getting this errors and only thing which can fix it is restarting deployment service.
Apr 07, 2017 06:49 PM|karban01|LINK
I am also wondering it this is a fix or a band-aid on the problem.. Does anyone have a reply or is the restarting the service seem to be the only reported fix?
Our environment is a shared Dev environment with hundreds of sites on a single IIS server and no one else seems to be complaining about this error but one project. So is it site/project specific or is server wide and no one else is reporting it?
Jun 12, 2018 10:20 PM|ManojPanwar|LINK
This is happening over and over and the 'fix' is a temporary one. Is there going to be a permanent fix for this? !!
6/13 - Getting this with EVERY publish now. Multiple times a day.