Can't get my EC2 Windows Server 2008 (Web stack) instance to receive publishings of my website

Question

I installed a fresh AMI for EC2 (http://aws.amazon.com/amis/Microsoft/5147732567196848) and have installed Web deploy 2.1 on it.

The web deploy 2.1 service is runnin

Answer 1

I contact Microsoft directly about this problem and they had an immediate answer for me.

From MS guy:

It looks like your Web Management Service not contactable. I have seen this before when the certificate for the service is invalid. Can you run the attached script on your server?

1. Start a PowerShell prompt elevated
2. Run set-executionpolicy unrestricted –force
3. Run .\00_Certificate.ps1
4. Net stop wmsvc
5. Net start wmsvc

Does this fix the problem?

---

The script he is referring to is available here

Answer 2

This error can also occur when you specify the end point in the wrong format.

For example when selecting to publish an application Visual Studio gives examples of the end point format such as https://RemoteServer:8172/MsDeploy.axd

Turns out it actually wanted this without the http prefix e.g. 0.0.0.0:8172/MsDeploy.axd

If you get an error about certificates after this you just need to check the box allow untrusted certificates in the publish screen.

Agrahahah!

Answer 3

I had this same problem with Web Deploy when it was installed by the Web Platform Installer. After manually uninstalling and reinstalling Web Deploy directly (NOT using Web PI) it worked fine...

Answer 4

I get the same error when i tried to deploy a website.

In the EventViewer (Windows Logs/System) i had an error log, that the log file of the Web Management Service could not be created ("Unable to create log file D:\Logfiles\WMSVC\W3SVC1\u_ex131126.log. Make sure that the logging directory is correct and this computer has write access to that directory.".

I just removed the readonly flag of the log folder and all worked fine again.

Answer 5

Some very helpful answers for an error message with many causes. I had this error and it turned out that the "IIS Web site/application" name used for the destination server was wrong.

So, causes for this could include:

• Bad username or password
• Incorrect web site name for destination (In Visual Studio, this is set on the Package/Publish Web tab of a web project's properties)
• SSL cert for web management (for example if your server was sysprepped after IIS was installed)