Hi All,

I have a large website developed using VS2013 MVC. Development has been on going for more than a year, The site is published once or twice day, until yesterday.... 

Nothing has has changed that might affect the publish process, but when its published the following errors appear in the build log:-

1>------ Publish started: Project: WebFrameBuilder, Configuration: Release Any CPU ------
1>Transformed Web.config using C:\Users\AirBear\documents\visual studio 2013\Projects\WebFrameBuilder\WebFrameBuilder\Web.Release.config into obj\Release\TransformWebConfig\transformed\Web.config.
1>Insert additional EFCodeFirst Database Deployment Transformed obj\Release\TransformWebConfig\transformed\Web.config into obj\Release\InsertEFCodeFirstDeploy\transformed\Web.config.
1>Auto ConnectionString Transformed Views\Web.config into obj\Release\CSAutoParameterize\transformed\Views\Web.config.
1>Auto ConnectionString Transformed obj\Release\InsertEFCodeFirstDeploy\transformed\Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
1>Copying all files to temporary location below for package/publish:
1>obj\Release\Package\PackageTmp.
1>Start Web Deploy Publish the Application/package to https://waws-prod-XXX-003.publish.azurewebsites.windows.net/msdeploy.axd?site=XXXX...
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4253,5): Warning : Retrying the sync because a socket error (10054) occurred.  
1>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10.
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4253,5): Warning : Retrying the sync because a socket error (10054) occurred.  
1>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 2 of 10.
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4253,5): Warning : Retrying the sync because a socket error (10054) occurred.  
1>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 3 of 10.
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4253,5): Warning : Retrying the sync because a socket error (10054) occurred.  

..... more retrys.... XXX=obfuscation

If left to run the publish/build eventual fails after 10 attempts. Each attempt to publish takes over an hour to fail. 

Yesterday, my fourth publish attempt WORKED! after only 3 attempts to serialize. Nothing was changed apart from restarting publishing between each attempt.

I have Googled every possible combination of the error messages, most advice is focused around the publish path being incorrect. I have dismissed this as the cause as the the publish will randomly succeed.

Microsoft obviously expect the serialization to fail as they reattempt it 10 times before abandoning the build. But there is no indication as to why each attempt fails.

Can anyone please offer advice as to what I can do to resolve these publishing problems as this has stopped all development on this site?

Thanks

AirBear

Update - The final build error after an hour is "Remote connection forcibly closed by remote host"

• Edited by AirBear 21 hours 34 minutes ago

Hi,

I suggest you to follow the below articles which suggests about Publishing to Website

http://azure.microsoft.com/en-in/documentation/articles/web-sites-dotnet-get-started/

http://azure.microsoft.com/en-us/documentation/articles/web-sites-deploy/

Hope this helps !

Regards,

Sowmya

Hi,
  According to my Research on actual cases dealing with same issue, it could be due to.
  1)Firewall dealing with large files being sent.
  2)Network connectivity issues or Processing delay on server locally
  3)Certificate issues
   etc.
  
  If you have ruled out above causes (or atleast the first 2)
  You can use KUDU from github to check deployment error logs. (refernce)
 
  you can try the troubleshooting steps from the below stackoverflow article:
  http://stackoverflow.com/questions/5841370/cant-get-my-ec2-windows-server-2008-web-stack-instance-to-receive-publishings
 
  If this is affecting your Production, I would strongly suggest you create a Support ticket for this issue at :
  http://azure.microsoft.com/en-in/support/options/
 
Regards,
Nithin Rathnakar

Hi,

Unfortunately, the above links show how to deploy, they do not give advice on what to do when the remote server keeps closing the port. Which does seem to be what is happening.

Is there any way to get more details as to why the port is closed. I have looked for publish logs using KUDU Services https://XXX.scm.azurewebsites.net  I am unable to find anything relevant.

This problem is killing me!

AirBear