Share via

Windows Server 2019 Standard - Event ID 36 and 4005

Anonymous
2024-01-12T10:43:07+00:00

Hi Team,

We have a 2019 server with RDS role installed. Randomly users cannot connect to an RDP session. Instead, those users see a black screen, and they are eventually disconnected.

Same as mentioned here - https://support.microsoft.com/en-us/topic/july-2016-update-rollup-for-windows-8-1-and-windows-server-2012-r2-385eeb37-3b97-fdac-6a83-be88691f4c27

The roll-up mentioned above is not compatible with Windows 2019.

Also, Event ID: 20498 - Remote Desktop Services has taken too long to complete the client connection in Windows > Terminal Service > Remote connection manager

Could you advise, what to do in this case?

Regards,

Aneesh

Windows for business | Windows Server | User experience | Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-01-15T02:58:37+00:00

    Hello   Aneesh Kunnath，

    Thank you for posting in Microsoft Community forum.

    Event ID 36 and 4005 are related to Remote Desktop Services and indicate that the RDS server is having trouble communicating with the RDS licensing server. The error message suggests that the licensing server may be offline or unreachable.

    To troubleshoot this issue, you can try the following steps:

    1. Verify that the RDS licensing server is online and reachable from the RDS server. You can use the ping command to test connectivity.
    2. Check the Event Viewer on the RDS licensing server for any related errors or warnings.
    3. Verify that the RDS server is configured to use the correct licensing mode (per user or per device) and that it is pointing to the correct licensing server.

    Regarding the Event ID 20498, it indicates that the RDS server is taking too long to complete the client connection. This could be caused by a variety of factors, such as network issues, server performance problems, or misconfiguration.

    To troubleshoot this issue, you can try the following steps:

    1. Check the Event Viewer on the RDS server for any related errors or warnings.
    2. Monitor the server's performance using Task Manager or Performance Monitor to see if there are any spikes in CPU, memory, or disk usage.
    3. Verify that the RDS server is configured correctly and that it meets the recommended hardware and software requirements.

    I hope the information above is helpful.

    If you have any question or concern, please feel free to let us know.

    Best Regards,

    Haijian Shan

    0 comments