Web site bindings

Legacy Uncategorised
1

Hi,

I’m deploying a “IIS web site and application pool” using it out of the box, and I don’t know why only sometimes the enabled protocol is msmq.formatname (which was enabled in the previous deployment), so when starting up the site it fails, because the only binding that exists is http in port 80.

So it looks like when redeploying, it doesn’t rewrite the enabled protocols property to set it to http.

The error I get when starting the website in octopus beforepostdeploy is:
The object identifier does not represent a valid object. (Exception from HRESUL
Error 16:52:16
T: 0x800710D8)
Error 16:52:16
At C:\Program Files\Octopus Deploy\Tentacle\Scripts\Octopus.Features.IISWebSite
Error 16:52:16
_BeforePostDeploy.ps1:68 char:10
Error 16:52:16

  •             throw <<<<

Error 16:52:16
+ CategoryInfo : OperationStopped: (:slight_smile: [], COMException
Error 16:52:16
+ FullyQualifiedErrorId : The object identifier does not represent a valid
Error 16:52:16
object. (Exception from HRESULT: 0x800710D8)

Thanks,
Miguel

2

Solved it.

I was adding more bindings after the web site install and the enabled protocols property was being set to the last binding set. In this case msmq.formatname.

So at the end of adding more bindings I just enabled the other protocols.

It’s a bug anyway that if a site is corrupt (protocol without binding enabled) octopus doesn’t delete it and create a new one.