Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

MsDeploy fails for webdeploy

I am trying web-deploy.

Because I wanted to be able to reproduce this, i used a test system

Windows 2008 RC, IIs 7.5 + Deployment package I configured deployment using http://learn.iis.net/page.aspx/516/configure-the-web-deployment-handler/ Enabled tracing http://technet.microsoft.com/en-us/library/ff729439(v=ws.10).aspx

I created a new WCF Service Application, (changed nothing) compiled it and tried to deploy

I get the following response(after a few min)

------ Build started: Project: WcfService1, Configuration: Debug Any CPU ------
  WcfService1 -> C:\Development\BrandShield\Services\WcfService1\bin\WcfService1.dll
------ Publish started: Project: WcfService1, Configuration: Debug Any CPU ------
Transformed Web.config using Web.Debug.config into obj\Debug\TransformWebConfig\transformed\Web.config.
Auto ConnectionString Transformed obj\Debug\TransformWebConfig\transformed\Web.config into obj\Debug\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Debug\Package\PackageTmp.
Start Web Deploy Publish the Application/package to http://dev1:8172/msdeploy.axd/MSDEPLOYAGENTSERVICE ...
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): Error : Web deployment task failed.(Could not complete the request to remote agent URL 'http://dev1:8172/msdeploy.axd/MSDEPLOYAGENTSERVICE'.)
This error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network settings on this computer and on the server computer are configured properly, and the appropriate services have been started on the server.
Error details:
Could not complete the request to remote agent URL 'http://dev1:8172/msdeploy.axd/MSDEPLOYAGENTSERVICE'.
The underlying connection was closed: An unexpected error occurred on a receive.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Publish failed to deploy.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========

and no logs (at all) on the dev1 server side.

I have tried many variations, but this is the simplest, easiest thing to reproduce. and it is failing.

any ideas?

like image 690
Mickey Perlstein Avatar asked Jun 05 '12 09:06

Mickey Perlstein


People also ask

Is Webdeploy secure?

Web Deploy is secure. Web Deploy supports transfer over HTTPS. Note that variants of FTP such as SFTP and FTPS are also secure.

How do you check Webdeploy is installed or not?

Is Web Deploy installed? You can verify web deploy is installed by going to the "Programs and Features" control panel and looking for "Microsoft Web Deploy 2.0" in the list of installed programs.

Does web Deploy work by pushing or pulling data?

You can use the Web Deployment Tool to synchronize a Web site from a source to a destination on IIS 6.0, or IIS 7 or above. You can do this by "pushing" data to a remote destination or by "pulling" data from a remote source.

Can't connect to remote server web Deploy?

This error indicates that you cannot connect to the server. Make sure the service URL is correct,firewall and network settings on this computer and on the server computer are configured properly,and the appropriate services have been started on the server.


1 Answers

I found the issue.

instead of "http://" dev1:8172/msdeploy.axd I used dev1:8172/msdeploy.axd

this is actaully the same as "https://" dev1:8172/msdeploy.axd, which for some reason is where the deployment agent listens.

From here, you will get a new error:

Could not complete the request to remote agent URL 'https://dev1:8172/msdeploy.axd?site=Default web site'. 
The underlying connection was closed: 
Could not establish trust relationship for the SSL/TLS secure channel.
The remote certificate is invalid according to the validation procedure.

This is because you don't have a certificate for SSL.

In the publish profile window, You need to check the "Allow untrusted certificate" checkbox

and the publish should succceed. good luck

like image 65
Mickey Perlstein Avatar answered Sep 23 '22 10:09

Mickey Perlstein