Forum Discussion
JozefIzsoGoit
Aug 07, 2019Copper Contributor
RDWeb exception in Windows Server 2019
When user access the RDWeb exposed on port 443 directly from the application server with Remote Desktop Service roles and hits these addresses:
https://gw.contoso.com:443/RDWeb/
https://gw.contoso.com:443/RDWeb/Pages/en-US/Default.aspx
The server will log NullReferenceException in Event viewer.
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7. 8. 2019 11:40:40
Event time (UTC): 7. 8. 2019 9:40:40
Event ID: 00c125e50abe4c26a3502bc2fc2289bd
Event sequence: 63
Event occurrence: 5
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT/RDWeb/Pages-3-132096433038469260
Trust level: Full
Application Virtual Path: /RDWeb/Pages
Application Path: C:\Windows\Web\RDWeb\Pages\
Machine name: APP1
Process information:
Process ID: 7756
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()
Request information:
Request URL: https://gw.contoso.com:443/RDWeb/Pages/en-US/Default.aspx
Request path: /RDWeb/Pages/en-US/Default.aspx
User host address: 85.243.21.13
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOL\RDWebAccess
Thread information:
Thread ID: 155
Thread account name: IIS APPPOOL\RDWebAccess
Is impersonating: False
Stack trace: 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()
Custom event details:
- hansvosCopper Contributor
JozefIzsoGoit Did you find any fix for this issue ?
- rcs_8192Copper Contributor
I know this is an old post, but since I killed about three days looking for a resolution I figured I would post what solved the issue for me...
I was having the exact same error and spent several days searching for a solution. For me what it turned out being was a published app that had been uninstalled from the server. Once I went in and unpublished the app the website exception fixed itself.
Hope this helps someone else.
- Finger1970Copper ContributorAbsolute GOLD RCS 8192, I never expected my errors were from a published app but after removing some, everything worked again, thanks for the post.