Manager Server 20.2.48 crashes shortly after startup

Good morning. Has anybody noticed that the newest Manager Server (server edition) crashes immediately or shortly after start up? ( @lubos )

Unhandled Exception:
System.NullReferenceException: Object reference not set to an instance of an object
  at ManagerServer.Extensions.HttpHandlerExtensions.GetCurrentUser (ManagerServer.HttpHandler httpHandler) [0x001d7] in <86967e81cb114fbcb641363f20907220>:0 
  at ManagerServer.HttpHandlers.Template.Get () [0x002c2] in <86967e81cb114fbcb641363f20907220>:0 
  at ManagerServer.HttpHandler.ProcessRequest () [0x000ff] in <86967e81cb114fbcb641363f20907220>:0 
  at HttpFramework.HttpServer.Worker () [0x000f4] in <f4a8accfb1134e3fbb7e718982d49c3d>:0 
  at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <d50a1f2f14b642d2b936cb144b307343>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <d50a1f2f14b642d2b936cb144b307343>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <d50a1f2f14b642d2b936cb144b307343>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <d50a1f2f14b642d2b936cb144b307343>:0 
  at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <d50a1f2f14b642d2b936cb144b307343>:0 
[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
  at ManagerServer.Extensions.HttpHandlerExtensions.GetCurrentUser (ManagerServer.HttpHandler httpHandler) [0x001d7] in <86967e81cb114fbcb641363f20907220>:0 
  at ManagerServer.HttpHandlers.Template.Get () [0x002c2] in <86967e81cb114fbcb641363f20907220>:0 
  at ManagerServer.HttpHandler.ProcessRequest () [0x000ff] in <86967e81cb114fbcb641363f20907220>:0 
  at HttpFramework.HttpServer.Worker () [0x000f4] in <f4a8accfb1134e3fbb7e718982d49c3d>:0 
  at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <d50a1f2f14b642d2b936cb144b307343>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <d50a1f2f14b642d2b936cb144b307343>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <d50a1f2f14b642d2b936cb144b307343>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <d50a1f2f14b642d2b936cb144b307343>:0 
  at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <d50a1f2f14b642d2b936cb144b307343>:0

20.2.49 also crashes after teh process runs for a few moments to a few minutes…

Could you try version 20.2.50? It shouldn’t crash the app anymore. However it will show the error. Can you navigate to site using private mode on your web-browser whether it makes difference?

20.2.50 loaded up…

Unhandled Exception:
System.InvalidOperationException: Cannot be changed after headers are sent.
at System.Net.HttpListenerResponse.set_ContentLength64 (System.Int64 value) [0x00021] in :0
at System.Net.HttpListenerResponse.Close (System.Byte responseEntity, System.Boolean willBlock) [0x00017] in :0
at HttpFramework.HttpResponse.Close () [0x00024] in <08f9df538de143278b9f76d6dd50b5c3>:0
at HttpFramework.HttpServer.Worker () [0x0011e] in <08f9df538de143278b9f76d6dd50b5c3>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in :0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in :0
at System.Threading.ThreadHelper.ThreadStart () [0x00008] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidOperationException: Cannot be changed after headers are sent.
at System.Net.HttpListenerResponse.set_ContentLength64 (System.Int64 value) [0x00021] in :0
at System.Net.HttpListenerResponse.Close (System.Byte responseEntity, System.Boolean willBlock) [0x00017] in :0
at HttpFramework.HttpResponse.Close () [0x00024] in <08f9df538de143278b9f76d6dd50b5c3>:0
at HttpFramework.HttpServer.Worker () [0x0011e] in <08f9df538de143278b9f76d6dd50b5c3>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in :0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in :0
at System.Threading.ThreadHelper.ThreadStart () [0x00008] in :0

btw… private mode results in same error.

20.2.55 seems to be workin great! Thanks @lubos

The strange thing the version 20.2.55 shouldn’t be fixing this issue yet. I’ve noticed someone else is having exactly the same problem so still looking into this.