Msdeploy mvc to Windows7 gets ERROR_DESTINATION_NOT_REACHABLE and 404

Question

I am trying to make msdeploy an MVC application in a msdeploy command line window. And kept getting this error:

Error code: ERROR_DESTINATION_NOT_REACHABLE Additional information: Failed to connect to the destination computer ("192.168.xxx.xxx"). On the destination computer, verify that Web Deploy is installed and the required process is running (Web Management Service). Error: An error occurred on the remote server: (404) Not found. Number of errors: 1.

I checked both Wmsvc (it seems this is being used) and MsDepSvc. And the firewall is off. In the browser, when I am https://192.168.xxx.xxx:8172/msdeploy.axd , I got a 404 server error, it seems a little further than where the command line is stopped.

I can find most of the instructions for configuring IIS7 and web deployment on the Internet for MS Servers. Both my local machine and the Windows7 machine have the same version of Msdeploy.

Answer 1

For non-server operating systems (i.e. Windows 7), publishing Web Deploy through the web management service is not supported. Instead, you will have to use the remote agent service; this is an administrator-only publishing service. Further information can be found at http://technet.microsoft.com/en-us/library/dd569059(v=WS.10).aspx .

Answer 2

I had the same issue with a VM on Azure, and the solution was to enable IIS Management Service first and then install Web Deploy (I used the web platform installer). The installation order seems to matter. You can find the blog entry I wrote about it here http://davidjrh.intelequia.com/2012/10/configurando-web-platform-installer-y.html

Answer 3

I had the same problem as MSDeploy to deploy my web application to a remote IIS 7.5 web server with Windows 7. I just figured out how to solve the problem today after reading the Sayed message, so I want to post my solution here for everyone who would run into a problem like me. Try the following:

• Enable IIS Management Service (in Control Panel → add or remove functions → add or remove Windows functions)
• Install Web Deployment ( http://www.iis.net/downloads/microsoft/web-deploy )
• Open cmd with administrative privilege, enter "net start msdepsvc" to start "Web Deployment Deployment Agent".
• Check this link in your browser: http://serveraddress/MsDeployAgentService/ , if it asks for a username and password, MsDeployAgentService is running on the server, go to the next step.
• In VS, enter http://serveraddress/MsDeployAgentService/ in the service URL when creating the publication instead of https://serveraddress:8172/MsDeploy.axd and click on the test connection. Everything should be fine now.

Answer 4

After checking the correct installation of the management service and web deployment 3.0, I found that (at least from VS2012) the service URL also matters, so trying to publish any of the following does not work for me:

• FQDN (localmachine.domain.local)
• Domain IP Address (172.22.xxx.xxx)
• Loop-back IP Address (127.0.0.1)

While the following DID works:

• local
• NetBIOS name (localmachine)