Actually,I got error when I deploy use "MSDeployUseChecksum" ,if remove "MSDeployUseChecksum", deploy will successed. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4295,5): msdeploy error ERROR_PROXY_GATEWAY: Web deployment task failed. (Could not connect to the remote computer ("dev-cms.scm.didix-dev-ase.p.azurewebsites.net") using the specified process ("Web Management Service"). This can happen if a proxy server is interrupting communication with the destination server. Disable the proxy server and try again. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_PROXY_GATEWAY.
pubxml file
Related
When I try to publish code using Web Deploy method I am getting the following error
ERROR_DESTINATION_NOT_REACHABLE: Web deployment task failed. (Could not connect to the remote computer ("xxxxx.xxxxxxx.xxx.xxxx"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started
On my server,I have web deployer 3.5 install and web management service is also running.
There is no firewall issue also.
I have restarted the web management service still no luck
If you want to publish a site on a remote server you could follow the below steps:
Go to the Start menu and right-click the cmd.exe and then select Run as Administrator.
Enter the following in the command prompt:
winrm quickconfig
winrm set winrm/config/client #{TrustedHosts="*"}
On the target server, open a command prompt as an Administrator and
enter the following:
winrm quickconfig
winrm set winrm/config/client #{TrustedHosts="IP_ADDRESS"}
where IP address is the IP address of your remote server.
make sure you installed Management service.
-after doing all the above things open iis.
carete site with a blank folder at the destination (remote server)
go back to the server from which you want to publish a site and select Publish.
On the Publish page, click the icon labeled IIS, FTP, etc.
In the Publish Method list box, select Web Deploy:
or if you want to publish as an application under any site:
no need to create site at the destination server.
enter your site name in the site name and enter your application name after /.
Regards,
Jalpa
Error image Unable to Remote Deploy my Webservice on to the remote machine from local machine. I have two servers that i would be needing to enable web deployment from local system to remote server Windows 2012 system. Upon searching multiple resources i found below steps that need to be ensured before performing the remote deploy using MsDeploy from Local to Remote .
Also Package works fine which is built from Visual Studio if i copy the files on to the remote server and run the command file it is able to deply the windows service on to IIS locally . But i would need this to be deployed from my local machine to remote server*
Steps I tried :
Ensure Web Deploy is installed.
Remote Services are running.
Under Management Service in IIS ensure Enable Remote connections
is enabled.
Ensure 80 and 8172 Ports are enabled and running ( ran the below steps )
Web Deploy is installed on the server that i'm trying to deploy the
package.
I try running the below code and it returns below error :
Command I provide :
C:\Users\xxxxx>net start wmsvc
The requested service has already been started.
C:\Users\xxxxxx>net start msdepsvc
The requested service has already been started.
Command I provide :
C:\Program Files\IIS\Microsoft Web Deploy V3>msdeploy.exe -verb:sync -source:package="C:\Users\xxxxxx\Desktop\" -dest:auto="",ComputerName="https://serveripaddress:8172/MsDeploy.axd",UserName='domain/user',Password='password',AuthType='Basic' -allowUntrusted
Info: Using ID 'someinfoid like : 92c-da-sd-2398as823...... is generated' for connections to the remote server.
Error Code: ERROR_DESTINATION_NOT_REACHABLE
More Information: Could not connect to the remote computer (""). 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.
Error: The remote server returned an error: (404) Not Found.
Error count: 1.
Installed Web Deploy Components
Ensured the Services are enabled ( Web Deploy / Remote Services )
Remote Server : Windows 2012
Local System : Windows 10
When I'm trying to publish using Web Deploy (Visual Studio 2017 for Windows) to a Linux app service hosted in Azure the following error occurs:
Could not connect to the remote computer ("my-linux-api.scm.azurewebsites.net") 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: (405) Method Not Allowed.
The link in the error description seems to refer windows based hosts.
The service is up and running and responds to my request:
How can I fix that?
There is no Web Deploy on Linux. That's a Windows/IIS thing.
Push with git instead. The .scm. service (Kudu) knows how to handle the ASP.NET Core deployment on Linux.
We have a web farm environment running IIS 7.5 on Windows 2008R2. We use shared configuration and web storage replication.
We tried to install Web Deploy (v3.5) on one of the servers but receive an error message saying that Web Deploy is not supported with Shared Configuration.
Is it possible to run Web Deploy in a shared configuration environment? If so how?
NOTE: We have figured this out so I am posting the answer here. There is little to no documentation that we could find on this topic so I thought it best to host the info here so the rest of the world can easily find it.
Yes Web Deploy can be installed on an IIS server using Shared Configuration. Here are the step we used to get it to work. Any comments, improvements or considerations are welcome.
Open IIS and select the server node in the tree.
Open the Shared Configuration in the Management section.
Uncheck Shared Configuration select Yes to copy the configuration to the local storage.
Do this to ALL servers that have been sharing configuration as you need to rebuild the configuration once Web Deploy is installed and reattach each server.
Install Web Deploy 3.5 (or newer) via the Web Platform Installer found here:
http://www.microsoft.com/web/gallery/install.aspx?appid=WDeploy
Installing Web Deploy will modify the authentication rules which will cause issues in a Shared Configuration environment so these rules need to be manually updated.
Open IIS and select the server node in the tree.
Open the Management Service Delegation module in the Management section (this module appears once Web Deploy is installed).
Edit the following rules and set the credentials to the a user that has access to the Shared Configuration. Typically a new account can be made that can be granted access to the Shared Configuration storage or use IIS service account. This will enable the web deployment agent to access the shared configuration with a domain account instead of the default local account.
createApp
recycleAPP
appPoolPipeline,appPoolNetFx
backupSettings
Restart the Web Deployment Agent service.
Restart the Web Management service.
Restart the IIS service.
Make sure you have disabled shared configuration on all servers.
Now to re-enable shared configuration, open IIS and select the server node in the tree.
Open the Shared Configuration in the Management section.
If this is the first server you need to export the configuration using the following steps (if not skip to next step):
Click Export Configuration...
Set the Physical Path to the shared configuration location and enter the appropriate encryption key.
You should see a success dialog if the export was successful.
Check Enable shared configuration.
Set the Physical Path to the shared configuration location and click Apply.
Enter the appropriate encryption key and click Ok.
Restart the IIS service.
You will then need to perform these steps again for each server using the shared configuration except you can skip step #14.
We have 1 new DEV and 1 new QA server that I am configuring for automated deploys. I got the DEV deploys working. My problem is that the deploy to QA is giving me the below error.
Our build server contains the controller and drop folder. The error occurs when the Invoke deploy command is issued. I have ensured that the Web Management service is running on the web servers.
What could be causing the follow error message?
Error Code: ERROR_DESTINATION_NOT_REACHABLE
More Information: Could not connect to the destination computer ("myWebServer").
On the destination computer, make sure that Web Deploy is installed and that the
required process ("Web Deployment Agent Service") is started.
Error: The remote server returned an error: (404) Not Found.
Error count: 1.
Here is my deploy command:
\\myBuildServer\Builds\MyApp - Deploy to QA\myApp - Deploy to QA_20120827.1\_PublishedWebsites\AppName.UI.Web_Package\Appname.UI.Web.deploy.cmd /M:http://myWebAddress/MsDeployAgentService/ /U:myDomain\tfsUID /P:MyPassword "-setParam:name='IIS Web Application Name',value='MyWebAppName'" /Y
If you're on IIS 7, ensure that WMSvc is installed (add or turn on Windows features) running, that it is configured correctly and enabled in IIS Manager under "Management Service" and that port 8172 is open - try telnet-ing into it.
If IIS 6, install the Web Deploy agent.
For IIS 7 using WMSvc, you should use http://svr:8172/MsDeploy.axd and for MsDepSvc you are already using the right URL (see your /M param).
I've found the whole remote publishing to be a total ballache.
When you install Web Deploy, make sure to select Custom and check all components. This is what solved the issue for me.
Source: Could not reach the Web Deploy endpoint on the specified virtual machine