Web Deploy results in ERROR_COULD_NOT_CONNECT_TO_REMOTESVC

Question

We are trying to configure continuous integration with TFS 2012. While queuing a new build, the publish fails with the error:

Build FAILED. "C:\src\ProjectName.sln" (default target) (1) -> "C:\src\Website\ProjectName.csproj" (default target) (2) -> (MSDeployPublish target) -> C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(4377,5): msdeploy error ERROR_COULD_NOT_CONNECT_TO_REMOTESVC: Web deployment task failed. (Could not connect to the remote computer ("ServerName") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC)**

I checked all the points mentioned in the IIS.NET documentation for this error. Both services mentioned, Web Management Service and Web Deployment Agent Service, are running fine. A restart of those services has no change in behavior.

• Windows Server 2008 R2 with IIS 7.
• Web Deployment Agent Service is running on port 8172.
• Web Deploy 3.0
• Windows Firewall is not blocking any port on the server.

How can this be fixed?

Answer 1

If you install Web Deploy 3.x BEFORE Web Management Tools are installed, you'll have to re-install Web Deploy. I beat my head against the wall for hours on this.

1. Install the Web Management Services ("Turn Windows Features On/Off"/Roles -> Web Server -> Management Tools -> Management Service)
2. Then uninstall Web Deploy (repair didn't work) via the usual Add/Remove Programs control panel
3. Install Web Deploy 3.x again using Web Platform Installer.

Fixed. /Sigh

Answer 2

Double check in your Web Deploy settings that the name of the website is exactly that of what's in IIS.

Ben Day blogged more about it.