Tentacle causes AddressAlreadyInUseException Exception after installing .Net Framework 4.5


One of the tentacles required an upgrade to the .Net 4.5 Framework. After installation, the health of the tentacle was red with Security Error:

2013-05-02 00:07:06 ERROR System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party

When attempting to login to the machine and start the tentacle manually in an elevated command prompt I received the error:
C:\Program Files (x86)\Octopus Tentacle\Agent>tentacle.exe

  • Tentacle

System.ServiceModel.AddressAlreadyInUseException: HTTP could not register URL http://:10934/. Another application has already registered this URL with HTTP.SYS. —> System.Net.HttpListenerException: Failed to listen on prefix 'http://:10934/’ because it conflicts with an existing registration on the machine.
at System.Net.HttpListener.AddAllPrefixes()
at System.Net.HttpListener.Start()

This was working perfectly before the framework upgrade.
Does this have anything to do with: http://paulstovell.com/blog/should-have-written-it-in-java . hehe

Please help if you have any ideas… Uninstalling the framework may not be an option.
Thanks in advance.

Hi Dean,

Have you restarted the machine since installing 4.5? Also, can you check
the clocks are in sync between the Octopus server and Tentacle?

The Windows event viewer on the Octopus and Tentacle servers should provide
more details about the error if you can look there.


Paul Stovell
Octopus Deploy
W: octopusdeploy.com | T: @octopusdeploy http://twitter.com/octopusdeploy

Restarted both machines and still happening, even tried different ports to no avail.

Checking the event viewer did help a little though and found a bunch of these issues occurring for ServiceModel Audit

Message authentication failed.
Service: http://devfoweb01:11562/
Action: http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT
MessageSecurityException: The security timestamp is invalid because its creation time (‘2013-05-02T01:03:32.566Z’) is in the future. Current time is ‘2013-05-02T00:53:44.691Z’ and allowed clock skew is ‘00:05:00’.

Spot on about the time. Didn’t think to check the event log (noob mistake). Damn WCF errors never give enough / accurate detail about the actual issue.

All working again.
thanks mate!