Fix: ASP.NET Web Deploy ‘ERROR COULD NOT CONNECT TO REMOTESVC’ error

Posted · 62 Comments

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.)

image

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 http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.  The remote server returned an error: (550).

 image

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.

image

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

image

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. 

SNAGHTML3f140ac

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? 

image

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”. 

image

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

image

This time it worked. 

Summary

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.

-Ben


62 Responses to "Fix: ASP.NET Web Deploy ‘ERROR COULD NOT CONNECT TO REMOTESVC’ error"
  1. Paul says:

    Hey thankyou so much for publishing this. Saved me so much time. Such a simple change.

  2. Ian Day says:

    Thanks Ben – that fixed my issue.

  3. Param says:

    Thanks 🙂 Worked like a charm!

  4. Marcel says:

    Thousand thanks! You saved me! The MS documentation could be much better on this.

  5. Nick says:

    Thank you, I’ve been trying to figure this out all night.

  6. zipor says:

    Great article, plain and simple, and most important – it helped!

    Thanks!

  7. 100000000 says:

    thanks 🙂

  8. Ricky says:

    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.

  9. Gustavo says:

    Thanks! I’ve been struggling with this error for a couple days.

  10. Sunny says:

    Big thanks, really saved my time digging through the various sites and Googling a lot!

  11. Marc Ziss says:

    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.

  12. Michael says:

    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!

  13. SunnyCase says:

    Very great article, spent hours on this.

  14. Ronak says:

    Thanks lot More than handy.
    spent lot of time behind on this finally resolved
    God bless.

  15. Ken says:

    Thanks! That helped me out!

  16. Pawel says:

    Great Article! Thanks! It has saved a lot of troubleshooting!

  17. Alexander says:

    Thank you very much. I spent 2 hours until found your article.

  18. Mike Godfrey says:

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

  19. Adam Bull says:

    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!

  20. Mike says:

    Thank You, Thank You, Thank You!!!!

  21. Sangeeth says:

    Thanks a lot! I had the same issue!!

  22. M says:

    Thanks for this …

  23. JOrdi says:

    Thanks so much guy!! I had the same issue U_U.

  24. Vincent Saelzler says:

    Thanks so much!
    Had the exact same issue and this fixed it.

  25. Lord Ayvar says:

    You save me from about three months of failed builds 🙂
    Thank you!!

  26. Luke says:

    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.

  27. YL says:

    This helps a lot! I had same exact issue. Saved me tons of time! Thank you!

  28. RJ says:

    Awesome job, Ben! Thanks for your help!

  29. Gracias! Last thing I tried before I got it to work 🙂

  30. huib says:

    thx! worked and saved me a lot of time!

  31. Frank says:

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

  32. Tony says:

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

  33. The Dawg says:

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

  34. chessnute says:

    Thanks Man! great tip!!!

  35. Rick Guillen says:

    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.

  36. Luis Fernando Sousa Santos says:

    Thank you!!

  37. Dimitar says:

    You’re the man!

  38. Hugo says:

    You’re the man! I had to add the site name after Default Web Site\sitename and voila.
    Thanks

  39. Rafal says:

    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.

  40. Mariano says:

    Thanks a lot!! it’s save mi a lot of time…
    As we say here in argentina “You are groso!”

  41. alex says:

    sweat~

    u saved my life

  42. DrJ says:

    Thanks for the tip.
    I couldn’t figure out what was wrong.
    You saved me a lot of time !

  43. Matt says:

    Thank you!!!!!!!

  44. rafal says:

    Thx very much 🙂
    You saved me a lot of time and time and time ! 🙂

  45. Harleen says:

    Thank You !

  46. Álvaro says:

    Thanks from Spain.

    You saved me more time.

    Regards.

  47. tailSpike says:

    Thank you thank you thank you!

  48. Steve Perry says:

    Thanks, you rock!

  49. David R says:

    The post that keeps on giving. Your 2013 post lives on and benefits many. Thank you

  50. Semih says:

    Thanks worked, you save my time !

  51. ThankYou says:

    Thank you for this!!!

  52. Filippo says:

    Thank you for your really useful tip!!!

  53. Jose Casal says:

    Thanks a lot man. Finally after 5 hours looking around.

 

© 2016 Benjamin Day Consulting, Inc.
Brookline, MA
617-645-0188
info@benday.com | |