We just recently upgraded to OD 3.11.18.
When we login with Microsoft Internet Explorer (11.0.9600) and using the AD credentials, we are seeing an exception reported in the Configuration/Diagnostics section. Everything seems to be operating correctly and we have the appropriate rights, but it’s unsettling that we are now getting this exception.
Previously, we were using 3.4, and 3.3 before that and never saw such an error in this same IE 11.0.
If I test using this 3.11.18 and login with Chrome (31.0.1650.63) there is no error reported in the diagnostics. This only seems to happen using IE 11.0.
–v--v–v--
Unhandled exception from web server processing GET to http://octopusdeploy.americas.cshare.net/{{ ‘~/images/directory_services_signin_buttons/microsoft-logo.svg’ | resolveLink }}: An operation was attempted on a nonexistent network connection
System.Net.HttpListenerException (0x80004005): An operation was attempted on a nonexistent network connection
at System.Net.HttpResponseStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.Dispose(Boolean disposing)
at System.IO.StreamWriter.Close()
at Newtonsoft.Json.JsonWriter.System.IDisposable.Dispose()
at Nancy.Serialization.JsonNet.JsonNetSerializer.Serialize[TModel](String contentType, TModel model, Stream outputStream)
at Octopus.Server.Web.OctopusNancyHost.OutputWithDefaultTransferEncoding(Response nancyResponse, HttpListenerResponse response) in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Server\Web\OctopusNancyHost.cs:line 359
at Octopus.Server.Web.OctopusNancyHost.ConvertNancyResponseToResponse(NancyContext nancyRequest, Response nancyResponse, HttpListenerResponse response) in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Server\Web\OctopusNancyHost.cs:line 342
at Octopus.Server.Web.OctopusNancyHost.Process(HttpListenerContext ctx) in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Server\Web\OctopusNancyHost.cs:line 454
–v--v–v--
Can you offer some insight as to what this means and the ramifications? Why are we only seeing this on IE 11.0? And, how we can make it stop?
Thanks