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?

Are you trying Continues Integration first time? if yes, try to create a publish profile on your web project and try to web deploy manually. — suresh2, Sep 11 '13 at 12:52
Thanks for replying. I tried publishing locally on the server by creating a publish profile and tried web deploying manually, but it is still giving the same error. Also while hitting the URL - https://ServerName:8172/msdeploy.axd, I am getting the HTTP 404 file not found error. Please Help.. — Alok Dhyani, Sep 12 '13 at 10:17
Looks like, you didn't install web Deploy properly. did you follow all these steps in this link http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy ? Try Reinstall that. — suresh2, Sep 12 '13 at 12:37
No It didnt worked after following those steps mentioned in the link too. I am afraid what could be the problem. — Alok Dhyani, Sep 13 '13 at 12:01
Try https://localhost:8172/msdeploy.axd in your Webserver. Make sure its working. if it is working, check firewall port is open for 8172 in firewall settings (Web Management Service (HTTP Traffic-In)). — suresh2, Sep 13 '13 at 13:34
On Hitting https://localhost:8172/msdeploy.axd it asks to proceed for untrusted connection, and on clicking it, it gives pop up for user name/pwd to connect to Web Management Service. I gave the credentials which has administrator rights, but on proceeding it shows 404 page. — Alok Dhyani, Sep 16 '13 at 10:15
The user no need to be an administrator. The user can be a normal windows user and must be configured in the configure web deploy publishing screen in the IIS. Sorry, I am not sure what else to advise to solve this issue. uninstall everything and Try the steps again from the beginning. Try this link as well. http://forums.iis.net/p/1176267/1974277.aspx — suresh2, Sep 18 '13 at 08:40
I just spent two days on exactly the same thing. My problem was a typo. The name of my site was SampleService and in my script that called msdeploy I typed http://server:8172/msdeploy.axd?site=SampleServer (the actual names are longer making it that much less obvious). — biscuit314, Oct 12 '13 at 14:47

score 95 · Answer 1 · edited Jul 30 '21 at 10:08

95

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.

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

Fixed. /Sigh

edited Jul 30 '21 at 10:08

Caius Jard

72,509
5
49
80

answered Jan 06 '15 at 22:05

Tom Hundley

1,325
9
14

1

another nonsense/illogical bug from MS, made me wanna kill myself – Kevin Simple May 05 '16 at 01:04
1

This saved an hour at my work today. Thanks a lot. You deserve many upvotes. – Rodrigo N M Sep 14 '22 at 17:27

score 45 · Answer 2 · answered Dec 09 '13 at 19:16

45

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

enter image description here

Ben Day blogged more about it.

answered Dec 09 '13 at 19:16

p.campbell

98,673
67
256
322

I would like to add that for an application under a website, the site name becomes "Default Web Site/myapp". Took me a while to figure out. – juanferrer Jun 09 '17 at 12:20
Example of an MSDeploy Url: https://{ServerName}:8172/MsDeploy.axd?site={siteName} You get this error when the site name is incorrect. – Daniel Leach Aug 22 '17 at 11:52
I had *http://* in xxxAfter removing *http://* published worked. – Matt Fricker Aug 12 '21 at 10:01

score 17 · Answer 3 · edited Dec 14 '14 at 14:20

17

Fix that i saw on another website:

Fix it by adding “http://” to server.

In other words, when server is www.xxxx.com would get the 403 error, but when server is http://www.xxxx.com, then it works.

edited Dec 14 '14 at 14:20

CRABOLO

8,605
39
41
68

answered Dec 13 '14 at 15:06

Ella Moshe

171
1
2

1

Thank you! almost cant believe I fell over that error. – Christopher Bonitz Jan 28 '16 at 15:29
This fixed it for me... all the other solutions were not it. Thank you! – Christopher Bales Apr 23 '21 at 19:28

score 4 · Answer 4 · answered Dec 11 '13 at 06:26

4

You need also to indicate the app name e.g 'Default Web Site/MyApp'

That was my error. Once I added /MyApp, it worked.

answered Dec 11 '13 at 06:26

user3085805

581
5
3

Thanks, often it's not the computer it's your own silly self! – Richard Housham Jul 10 '20 at 12:01
and - it hurts even more when you fall for it again! – Richard Housham Mar 09 '21 at 11:04

score 0 · Answer 5 · answered Aug 10 '17 at 15:04

I got this error when using msdeploy, not TFS. In my case I needed to make sure the user msdeploy is using had permission to deploy to the website.

Find the website in IIS manager, right click and go to Deploy, then Configure Web Deploy Publishing. Find the user used by Web Deploy and setup for this website.

Fairoz · Answer 6 · 2019-04-17T13:14:35.663

0

In my case the Internet proxy was enabled on source - which made msdeploy to reach out to internet instead of local ICN.

edited Apr 17 '19 at 13:14

answered Apr 15 '19 at 15:21

Fairoz

828
2
8
21

score 0 · Answer 7 · answered Apr 30 '19 at 10:18

You should check the logs on your IIS first - see that you actually get to the server, and then you can locate the exact error here - https://support.microsoft.com/en-us/help/943891/the-http-status-code-in-iis-7-0-iis-7-5-and-iis-8-0

Uninstalling and re-installing (not repairing!) after setting up IIS did most of the magic for me.

Rafael Neto · Answer 8 · 2020-03-09T05:55:22.883

There is another possible cause of the error. IIS Managemente Service have its own configuration for IP Address Restrictions, which default value is Deny Access for unspecified clients (Windows Server 2012 R2 with IIS 8.5).

You must set this value to Allow or add access to your specific IP address/IP address range using the Allow... button.

Remember, you must Stop the Management Service previously to change this configuration.

Web Deploy results in ERROR_COULD_NOT_CONNECT_TO_REMOTESVC

8 Answers8

Linked