Problem deploying 4.0 ASP.NET Application with WCF under IIS 7.5


We are testing out Octopus Deploy and are running into a problem. The deployment appears to be failing trying to set a authorization configuration property in IIS with the error “The configuration section ‘standardEndpoints’ cannot be read because it is missing a section declaration”. If I go into IIS and change the bindings (they are at on port 81) the site starts up fine with the web.config. The web.config is also more or less in use else where.

I can go into the IIS manager GUI and update attributes without a problem.

This is on a windows server 2008 r2 box running IIS 7.5 (IIS 6.0 is also installed on the box). The website is ASP.NET 4.0 with WCF. The standardEndpoints configuration is used for WCF.

I have included the error below and the section of the web.config.

Any help would be appreciated,



2014-01-12 22:51:30.6363 INFO Beginning deployment…
2014-01-12 22:51:33.6787 INFO Apply Web.Release.config
2014-01-12 22:51:33.6787 INFO Transforming ‘C:\Octopus\Applications\EC2Staging\SIRCLE.SecureSite\\Web.config’.
2014-01-12 22:51:33.6943 INFO Apply Web.EC2Staging.config
2014-01-12 22:51:33.6943 INFO Transforming ‘C:\Octopus\Applications\EC2Staging\SIRCLE.SecureSite\\Web.config’.
2014-01-12 22:51:33.8035 WARN (63:4) No element in the source document matches '/configuration/system.web/httpHandlers’
2014-01-12 22:51:33.9907 INFO Copy files to C:\inetpub\wwwroot\Staging_2
2014-01-12 22:51:33.9907 INFO Extracting package contents to 'C:\inetpub\wwwroot\Staging_2’
2014-01-12 22:51:40.7151 INFO Octopus.Features.IISWebSite_BeforePostDeploy.ps1
2014-01-12 22:51:41.9164 INFO Application pool “Staging_2” already exists
2014-01-12 22:51:41.9164 INFO Set application pool identity: ApplicationPoolIdentity
2014-01-12 22:51:42.9618 INFO Set .NET framework version: v4.0
2014-01-12 22:51:44.0695 INFO Site “Staging_2” already exists
2014-01-12 22:51:44.0695 INFO Assigning website to application pool…
2014-01-12 22:51:44.2723 INFO Anonymous authentication enabled: True
2014-01-12 22:51:44.4439 ERROR Set-WebConfigurationProperty : Filename: \?\C:\inetpub\wwwroot\Staging_2\web.c
2014-01-12 22:51:44.4439 ERROR onfig
2014-01-12 22:51:44.4595 ERROR Line number: 272
2014-01-12 22:51:44.4595 ERROR Error: The configuration section ‘standardEndpoints’ cannot be read because it
2014-01-12 22:51:44.4595 ERROR is missing a section declaration
2014-01-12 22:51:44.4595 ERROR At C:\Program Files (x86)\Octopus Tentacle 2.0\Agent\Scripts\Octopus.Features.I
2014-01-12 22:51:44.4595 ERROR ISWebSite_BeforePostDeploy.ps1:111 char:29
2014-01-12 22:51:44.4595 ERROR + Set-WebConfigurationProperty <<<< -filter /system.WebServer/security/authent
2014-01-12 22:51:44.4595 ERROR ication/anonymousAuthentication -name enabled -value “$enableAnonymous” -locati
2014-01-12 22:51:44.4595 ERROR on $WebSiteName -PSPath "IIS:"
2014-01-12 22:51:44.4595 ERROR + CategoryInfo : NotSpecified: (:slight_smile: [Set-WebConfigurationProperty]
2014-01-12 22:51:44.4751 ERROR , COMException
2014-01-12 22:51:44.4751 ERROR + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Micr
2014-01-12 22:51:44.4751 ERROR osoft.IIs.PowerShell.Provider.SetConfigurationPropertyCommand
2014-01-12 22:51:44.5844 FATAL Script ‘C:\Program Files (x86)\Octopus Tentacle 2.0\Agent\Scripts\Octopus.Features.IISWebSite_BeforePostDeploy.ps1’ returned non-zero exit code: 1. Deployment terminated.
2014-01-12 22:51:44.5844 ERROR Error running conventions; running rollback conventions…



Hi John,

Thanks for the error report; this is a bug introduced in one of our recent releases; ETA on a fix should be inside a week. If you are blocked you can downgrade to version 2.0.8, but taking a backup first is advised.

Issue to track it here:


Hi John, after a bit further investigation it seems this is more likely an issue involving compatibility between the app and the App Pool chosen. I’ve added a few more possibilities to the ticket linked above. Appreciate any further info you turn up. Regards,

Hi Nick,

I think we have ruled out all of those items (the fact that the website works with appropriate bindings). Please see the details on the github ticket. It appears to be a command failing internal to Octopus Deploy when it is trying to change an IIS attribute. If you could let me know the exact command, we could try it manually and see where that gets us.