MSDeploy WMSVC Not Working

Question

I have a build / test server that Jenkins is currently running for my continuous integration, and it also acts as my test server, where the code will be deployed to once built (I hope to fix this and separate them later, when the budget allows)

I have a .NET web solution (nothing complicated, just Umbraco) that I have in SVN, and now Jenkins is building correctly. Now I want to deploy it on the same server using MSDeploy. When the build is complete, the package is created, but the deployment fails

Error ERROR_DESTINATION_NOT_REACHABLE: Problem with network deployment. (Cannot connect to the remote computer ("xxxxx.xxxxxxx.xxx.xxxx"). On the remote computer, make sure that Web Deploy is installed and the required process is running ("Web Management Service")

Here are my msbuild options that Jenkins uses

/P:Configuration=Release /P:DeployOnBuild=True /P:MSDeployPublishMethod=WMSVC /P:DeployTarget=MSDeployPublish /P:PublishProfile=GetSomePixels /P:MsDeployServiceUrl=https://build.######## /P:AllowUntrustedCertificate=True /P:CreatePackageOnPublish=True /P:UserName=####### /P:Password=######## 

I checked the server and the web management service is started and it starts manually

I also went into IIS 8 Manager (Server 2012) and checked the "Allow remote connections" checkbox in the "Management Service" section. Restarting IIS and WMSVC and still not working.

If I go to https://myserver.co.uk:8172/MsDeploy.axd in the browser, it resolves (gives a warning about an untrusted certificate) and then displays a blank page.

Anyone have any ideas on what I can do? I thought this might be due to the firewall, and although he added an exception for the Windows Firewall for 8172, I turned off the entire firewall to fully manage this and still had no luck.

Launched it on the server to check its listening on the correct port

C: \ Users \ Administrator> netstat -a | findstr 8172 TCP 0.0.0.0:8172 GSP-BUILD: 0 LISTENING TCP [:]: 8172 GSP-BUILD: 0 LISTENING

Answer 1

Agree with the comment.

We had a similar problem. The initial installation, even after activating the web management service, was incomplete. In our case, despite the fact that the service stated that it was running, we were not able to achieve a green tick when testing the connection from the Publish dialog box when defining a profile.

Reinstalling WebDeploy 3.6 made it function properly.

Answer 2

Ok, I solved it. It seems you need to activate the web management service first and then install the web deployment, and I did it the other way around. I uninstalled WebDeploy and reinstalled it, restarted the server and its operation