IIS 7 and Above
TFService deployment to remote server - ERROR_DESTINATION_NOT_REACHAB...
Last post Oct 09, 2013 07:19 AM by Pengzhen Song - MSFT
Oct 08, 2013 05:10 AM|michaelbinks|LINK
Getting the following error when trying to deploy from Team Foundation Service (cloud version) to our dedicated hosting platform (with rackspace).
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets (4193): Web deployment task failed. (Could not connect to the remote computer ("xxx.xx.xx.xxx"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.)
We are running on w2008R2 with IIS7.5. I have installed WebDeploy v3.5 via the msi and confirmed ALL features are installed. The deployment handler is available and requests credentials, via localhost:8172. I have also confirmed this externally. So looks like all good on the port front.
I can successfully deploy via a 'one-click' WebDeploy from VS2012 on my dev machine.
The final step is to create a build definition in VS2012 and supply it with some MSBuild arguments...and this is where the problem occurs.
I can perform a successful deployment from the command line using MSBUILD from my dev machine to our hosted platform using the same MSBuild arguments supplied in the build definition. So it seems all is well on the connection front. However this does not work from a TFS build definition.
Using the Default Build Process Template and apart from MSBuild Arguments all other build process parameters are default.
Anyone any pointers? Is this even possible from TFService?
Question originaly posted here - http://social.msdn.microsoft.com/Forums/vstudio/en-US/c8d4dc1f-b5f9-4885-b4f6-94cd0fefbf8d/webdeploy-errordestinationnotreachable?forum=TFService
Oct 09, 2013 07:19 AM|Pengzhen Song - MSFT|LINK
IIS 6 uses Web Deployment Agent Service (MsDepSvc), whereas IIS 7 usually uses
Web Management Service (WMSvc)which have different URLs (besides, you have to be an admin on the target server to execute MsDepSvc.
Can you try specifying
For more information, you can refer here
And please refer the document
#Team Build + Web Deployment + Web Deploy + VS 2010 = Goodness
Hope it can help you