Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

VS to Azure Publish failure: Socket Error 10054

I've seen a few posts around on this, none have solved my issue.

I'm trying to complete a web deploy to an Azure site but whilst updating the files I get warnings:

MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4270,5) Warning : Retrying the sync because a socket error (10054) occurred Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10.

In the web publishing wizard the connection can be successfully validated.

I saw mentioned somewhere that I should enable untrusted certificates, however I can't see this option in the web deploy settings in VS2013.

Important notes:

  • I can deploy other projects (so I don't think it's a firewall issue).
  • My colleague can perform the web deploy with an old version of my project (so Azure is working fine).
  • I can't perform the web deploy using that same old version of the project.

It also doesn't work with an FTP publish either, although it doesn't give me the socket error warning. What could it be?

JK

like image 716
JonnyKnottsvill Avatar asked Apr 17 '15 10:04

JonnyKnottsvill


2 Answers

For any others who have this problem, I contacted Azure support and an engineer grabbed traces from their network end and mine to assess.

All he was able to deduce was that data packets were being intercepted somewhere between my machine and Azure's services resulting in timeout errors at both ends.

The problem lies with my work network, and I can successfully publish from other networks after testing...

Contact your network provider and have them investigate the issue, and in the mean time, if it is an option, make sure you test your publishing capability on other networks as it worked for me.

like image 148
JonnyKnottsvill Avatar answered Sep 20 '22 12:09

JonnyKnottsvill


I know this is an old one. But this might help someone.

For me it was the syncing processes for One Drive and Drop Box. Once i paused all the syncing the issue was resolved.

like image 42
Andrew Avatar answered Sep 22 '22 12:09

Andrew