ASP.NET 4.0.30319.0 Event ID 1209 on WSUS 2019 VM server

STES 0 Reputation points
2024-01-30T17:00:29.54+00:00

Hello all, I have a Windows Server 2019 VM server running WSUS. I am having two issues with either WSUS or the server itself. I cannot open the WSUS mmc snap-in locally or remotely, and I am also receiving numerous Warnings in Event Viewer regarding ASP.NET 4.0.30319.0 Event ID: 1309 Event Code 3001. VM Server info: Windows Server 2019 x64 12GB Memory Hyper-V Gen 2 VM .NET 4.8.03761 installed. Warning Message from Event Viewer is below: Event code: 3001 Event message: The request has been aborted. Event time: 1/30/2024 10:46:36 AM Event time (UTC): 1/30/2024 4:46:36 PM Event ID: 13b78305f3b24caa91076fc998fc4623 Event sequence: 162 Event occurrence: 49 Event detail code: 0

Application information: Application domain: /LM/W3SVC/1550003414/ROOT/SimpleAuthWebService-1-133511061600800114 Trust level: Full Application Virtual Path: /SimpleAuthWebService Application Path: C:\Program Files\Update Services\WebServices\SimpleAuthWebService\ Machine name: WSUS01

Process information: Process ID: 4952 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE

Exception information: Exception type: HttpException Exception message: Request timed out.

Request information: Request URL: http://wsus01:8530/SimpleAuthWebService/SimpleAuth.asmx Request path: /SimpleAuthWebService/SimpleAuth.asmx User host address: 10.57.252.184 User:
Is authenticated: False Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information: Thread ID: 49 Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False Stack trace:

Custom event details: Any help would be appreciated. Thanks.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,321 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Adam J. Marshall 7,921 Reputation points MVP
    2024-01-30T21:39:12.72+00:00

    If you restart the server, can you immediately log in and open the WSUS MMC or does it still not open? Same error or different?

    0 comments No comments