Hello
We have a 2019 Remote Desktop Gateway server. This morning most users could not login with their connections hanging on the "Securing Remote Desktop" part of the connection. We rebooted the Gateway server and removed\re-added the RDSH servers and that allowed users to connect.
Whilst we were having the problem we were getting lots of "Event ID 3005" errors in the Application Log. After the reboot we're still getting these but less frequently. The text of the error is:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 03/09/2024 11:05:46
Event time (UTC): 03/09/2024 10:05:46
Event ID: 84a59781ba4e408a91070fbca76e0882
Event sequence: 1729
Event occurrence: 246
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT/RDWeb/Pages-2-133698269112408744
Trust level: Full
Application Virtual Path: /RDWeb/Pages
Application Path: C:\Windows\Web\RDWeb\Pages\
Machine name: PTBM-GW02
Process information:
Process ID: 5240
Process name: w3wp.exe
Account name: IIS APPPOOL\RDWebAccess
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext objHttpContext)
at ASP.en_us_default_aspx.<GetAppsAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()
Does anyone know how to fix this please? Everyone is logging in OK now although I'm concerned that we'll get back to the same problem.
Thanks
Andy.