Visual Studio 2013 publish failed max connections exceeded

Question

I was publishing using VS Express 2013 for Web and had a sockets error on one of the dlls while publishing and now I can't publish at all - I received a VS error that says The maximum number of connections for this site has been exceeded. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXCEEDED_MAX_SITE_CONNECTIONS. The url referenced in the error doesn't even address the error and I've googled with no luck. I have tried deleting everything from the host and starting from scratch and still no luck; web host has no idea how to fix. Does anyone know how to fix this? I'm getting desperate.

Answer 1

Error was caused by a 10054 socket error (basically host dropped connection). After 3 days webhost finally restarted Web Management Services and problem was fixed. Then I got 1/2 way thru publishing and got the same 10054 socket error and then max connections error. I was publishing a lot of files and it appears that host had a connection time out. I got in chat with host and asked them to restart Web Mgmt Svcs again, waited 20 mins and voila - I was able to publish again. Now I am watching publish and if I see the first socket error I cancel the publish so that it doesn't hit the max site connections error. Then I start publishing again and it picks right up where it left off. Nothing I could do on my end to fix it (believe me I tried everything).

Answer 2

Even i get this issue now and then but not necessary to reset web Management Service. You can go to azure website dashboard and reset your web site/ Application first and check.

Answer 3

I got the same error. I opened the Windows Azure item in the "Server Explorer" went to the Storage item in the tree select Blobs/wad-control-container and delete all the items in the list

Answer 4

In MS Deploy Server (IIS Server)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IIS Extensions\MSDeploy\3] "MaxSiteConnections"=dword:00000010

then reboot windows

Answer 5

Thank @LuvAspNet for saving my time.

For others who need more information, you could restart Web Management Services by creating a .bat file with this command (or run directly in cmd) and run as administrator

net stop wmsvc 

net start wmsvc 

pause