Note that there are some explanatory texts on larger screens.

plurals
  1. POWeb Deploy results in ERROR_COULD_NOT_CONNECT_TO_REMOTESVC
    primarykey
    data
    text
    <p>We are trying to configure continuous integration with TFS 2012. While queuing a new build, the publish fails with the error:</p> <blockquote> <p>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: <a href="http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC" rel="noreferrer">http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC</a>)**</p> </blockquote> <p>I checked all the points mentioned <a href="http://www.iis.net/learn/publish/troubleshooting-web-deploy/web-deploy-error-codes#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC" rel="noreferrer">in the IIS.NET documentation for this error</a>. Both services mentioned, Web Management Service and Web Deployment Agent Service, are running fine. A restart of those services has no change in behavior. </p> <ul> <li>Windows Server 2008 R2 with IIS 7. </li> <li>Web Deployment Agent Service is running on port 8172. </li> <li>Web Deploy 3.0 </li> <li>Windows Firewall is not blocking any port on the server. </li> </ul> <p>How can this be fixed?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload