I was playing around with deploying an ASP.NET application to a server using Web Deploy in Visual Studio 2012 and I go this annoying little error.  I’d fill out the dialog for publishing via Web Deploy and when I’d click “Validate Connection” it would run and eventually fail.  The problem turned out to be “user error” obscured by a misleading error message.  (Scroll to the bottom for the fix.)


When I clicked on the “Failed (click for details)” link, it would show me the following:

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  The remote server returned an error: (550).


That link in the error message take you here and that page walks you through verifying that you can 1) ping the remote machine, 2) verify that the msdepsvc or wmsvc services are started, and 3) that the firewall isn’t blocking ports 80 or 8172. 

I tried pinging the server from my developer machine and it worked.


I checked the Web Deployment Agent Service (msdevsvc) and the Web Management Service (wmsvc) and they were both running.


I checked the Windows Firewall and (being someone who’s not one to leave anything to anything to chance and favors the brute force approach) turned the Firewall off entirely. 


Everything seemed to be set up properly but the error remained.  Maybe it’s user error.  Hmmm. 

The Fix.

I started looking at the values that I was typing into the dialog and that Site name one was bothering me.  Did I have that value right? 


The site name field relates to the name of the Internet Information Server (IIS) site instance name on the server.  I logged onto the target server and opened up the Internet Information Services (IIS) Manager console.

I expanded the nodes until I saw the list of sites and it turns out that it’s not “defaultwebsite” but instead it’s “Default Web Site”. 


I went back to the Web Deploy Publish Web dialog, changed the values and clicked Validate Connection.


This time it worked. 


The ERROR_COULD_NOT_CONNECT_TO_REMOTESVC error message could indicate that you’ve typed the IIS site name value in incorrectly.  Verify the site name on the target server in IIS Manager and try again.


82 Responses to "Fix: ASP.NET Web Deploy ‘ERROR COULD NOT CONNECT TO REMOTESVC’ error"
  1. Excellent Blog post Ben, I’ve spent the last few hours trying to figure this out and your blog post explained exactly what was wrong. Great Job.

  2. I had the Web Management Service installed but didn’t have the WebDeploy installed. Thanks to your great summary; I figured out which piece I was missing.

  3. Spent hours on this. I prefix my site names with an ID in IIS, and neglected to include that on the form. The error message sent me hither and yon and I never really looked at that field.

    Thanks a bunch!

  4. Thank you so much for taking the time to document your fix – not sure I would have discovered the solution otherwise. A great help!

  5. Haha thank you so much for this! I was putting my domain name in hoping that IIS would detect the matching bindings! Obviously not that smart!

  6. Spot on. In fact, the issue I had was that you have to create the web site in IIS before you can publish. I thought it would be created automatically. Thanks.

  7. Thanks for the detailed post. I was struggling to find the solution and thankfully found your post.

  8. Ben – Thank you and well done! I wasted a couple of hours checking firewalls and what not. Glad I found your post.

  9. YOU ARE A GOD!! I struggled for an hour with this, checking all kinds of firewall settings. Thank you for this post.

  10. I guess I’m one of the few people that are still getting this error, even when I changed the “Site Name” field to Default Web Site. I checked all of the issues listed above.

  11. In my case the problem was different – I have specified correct IIS site name, but I have made a mistake while specyfying the port number of remote Azure server.

  12. I have spent most of my Sunday (at least 6 hours) fighting this issue. I can’t even begin to count the number of docs I have gone thru trying to resolve this issue. Your solution fixed my issue. Many thanks

  13. Thank yo for publlishing this. The error is misleading and it did cost me moren then an hour to start looking elsewhere. I found your site and this worked. THANKS.

  14. You just resolved 3 days of troubleshooting. THANK YOU! Where’s your “Buy me a beer” link?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: