We have redeployed two Azure VDI Session hosts and reinstalled the Azure VDI agents as per https://learn.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-agent#your-issue-isnt-listed-here-or-wasnt-resolved due to Healthstate issues. The session hosts were registered with a registration key. We are seeing these errors in Event Viewer which are recurring frequently. Microsoft.RDInfra.RDAgent.Service.TURNRelayAccessHealthCheck CheckNATShapeAsync - Exception hit: System.AggregateException: One or more errors occurred. ---> System.TimeoutException: Timed out waiting for Receive to complete Microsoft.RDInfra.Diagnostics.Operations.LocalMonitoringOperation Op='DomainReachableHealthCheck' already set. Ignoring resultType=Success Microsoft.RDInfra.RDAgent.Service.DomainReachableCheck CheckSessionHostDomainIsReachableAsync - SessionHost unhealthy: the domain the SessionHost is joined to is not reachable! The hosts show as Green healthstate in the Portal and remote apps are running perfectly fine. Can anyone please assist on how to resolve these errors?

Hello @Addison McDermid The errors you are seeing in the Event Viewer indicate that the Azure Virtual Desktop Agent is having trouble communicating with the Azure Virtual Desktop service. This can be caused by a number of issues, including network connectivity problems, DNS resolution issues, or problems with the Azure Virtual Desktop service itself. Here are some steps you can take to troubleshoot and resolve these errors: Check the network connectivity between the session hosts and the Azure Virtual Desktop service. Make sure that the session hosts can reach the Azure Virtual Desktop service over the network and that there are no firewalls or other network devices blocking the traffic. Check the DNS resolution on the session hosts. Make sure that the session hosts can resolve the DNS names of the Azure Virtual Desktop service and that there are no DNS resolution issues. Check the Azure Virtual Desktop service status. Make sure that the Azure Virtual Desktop service is running and that there are no service outages or other issues. Restart the Azure Virtual Desktop Agent service on the session hosts. This can sometimes resolve communication issues between the session hosts and the Azure Virtual Desktop service. If the issue persists, try re-registering the session hosts with the Azure Virtual Desktop service. This can sometimes resolve issues with the Azure Virtual Desktop Agent. If none of these steps resolve the issue, you may need to contact Microsoft support for further assistance.

VDI Session Host health alerts in event viewer, how to resolve

Addison McDermid 0

We have redeployed two Azure VDI Session hosts and reinstalled the Azure VDI agents as per https://learn.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-agent#your-issue-isnt-listed-here-or-wasnt-resolved due to Healthstate issues.

The session hosts were registered with a registration key.

We are seeing these errors in Event Viewer which are recurring frequently.

Microsoft.RDInfra.RDAgent.Service.TURNRelayAccessHealthCheck CheckNATShapeAsync - Exception hit: System.AggregateException: One or more errors occurred. ---> System.TimeoutException: Timed out waiting for Receive to complete
Microsoft.RDInfra.Diagnostics.Operations.LocalMonitoringOperation
Op='DomainReachableHealthCheck' already set. Ignoring resultType=Success
Microsoft.RDInfra.RDAgent.Service.DomainReachableCheck
CheckSessionHostDomainIsReachableAsync - SessionHost unhealthy: the domain the SessionHost is joined to is not reachable!

The hosts show as Green healthstate in the Portal and remote apps are running perfectly fine.
Can anyone please assist on how to resolve these errors?

1 answer

Prrudram-MSFT 25,881 Reputation points

2024-08-01T09:59:08.6866667+00:00
Hello @Addison McDermid

The errors you are seeing in the Event Viewer indicate that the Azure Virtual Desktop Agent is having trouble communicating with the Azure Virtual Desktop service.

This can be caused by a number of issues, including network connectivity problems, DNS resolution issues, or problems with the Azure Virtual Desktop service itself. Here are some steps you can take to troubleshoot and resolve these errors:

Check the network connectivity between the session hosts and the Azure Virtual Desktop service. Make sure that the session hosts can reach the Azure Virtual Desktop service over the network and that there are no firewalls or other network devices blocking the traffic.

Check the DNS resolution on the session hosts. Make sure that the session hosts can resolve the DNS names of the Azure Virtual Desktop service and that there are no DNS resolution issues.

Check the Azure Virtual Desktop service status. Make sure that the Azure Virtual Desktop service is running and that there are no service outages or other issues.

Restart the Azure Virtual Desktop Agent service on the session hosts. This can sometimes resolve communication issues between the session hosts and the Azure Virtual Desktop service.

If the issue persists, try re-registering the session hosts with the Azure Virtual Desktop service. This can sometimes resolve issues with the Azure Virtual Desktop Agent. If none of these steps resolve the issue, you may need to contact Microsoft support for further assistance.
Please sign in to rate this answer.
Addison McDermid 0 Reputation points

2024-08-01T23:35:03.4833333+00:00

Hi Prrudram,

Have followed the MS article - https://learn.microsoft.com/en-us/azure/virtual-desktop/check-access-validate-required-fqdn-endpoint#use-the-azure-virtual-desktop-agent-url-tool to check the network connectivity and running step2 receive the following error:

PS C:\Users\BCA-Admin> cd $path

cd : Cannot find path 'C:\Users\BCA-Admin\RDAgent_' because it does not exist.

However searching for the file WVDAgentUrlTool.exe gives the following path:
C:\Program Files\Microsoft RDInfra\RDAgent_1.0.9103.3700

Running the tool from this path shows no URLs as inaccessible:
PS C:\Program Files\Microsoft RDInfra\RDAgent_1.0.9103.3700> .\WVDAgentUrlTool.exe

==============================================================

Azure Virtual Desktop Agent URL Tool

Copyright (c) 2022 Microsoft Corporation. All rights reserved.

Version 1.0.9103.3700

==============================================================

Connecting to Azure Virtual Desktop Agent (Attempt: #1)

UrlsAccessibleCheck : Outcome: HealthCheckSucceeded

Additional Contextual Information:<empty>

Accessible URLs:

======================================================

077bd4e9-1172-4082-9b79-35d16f53049c.rdbroker-g-au-r1.wvd.microsoft.com

077bd4e9-1172-4082-9b79-35d16f53049c.rdbroker.wvd.microsoft.com

077bd4e9-1172-4082-9b79-35d16f53049c.rddiagnostics-g-au-r1.wvd.microsoft.com

rdgateway-host-green-c101-aue-r1.wvd.microsoft.com

mrsglobalsteus2prod.blob.core.windows.net

gcs.prod.monitoring.core.windows.net

australiaeast-shared.prod.warm.ingest.monitor.core.windows.net

qos.prod.warm.ingest.monitor.core.windows.net

NOT Accessible URLs:

======================================================

<empty>

Acquired on:01-Aug-24 23:31:17 UTC

Could you please advise.

Prrudram-MSFT 25,881 Reputation points

2024-08-07T13:58:38.48+00:00

Hi @Addison McDermid

I have reviewed this internally with our AVD support team. This requires further diagnosis involving reviewing the logs collected from affected session hosts using this script Https://aka.ms/msrd-collect.

I would recommend creating a support case with AVD technical team, and share the logs requested above in the support case. If you don't have the ability to open a technical support ticket, please let me know and I can help you further with this.

Addison McDermid 0 Reputation points

2024-08-09T06:36:17.3566667+00:00

Hi @Prrudram-MSFT ,

Thank you for your update, we initially tried to raise a support case but was unable to raise a technical support ticket.

I have downloaded the msrd-collect tool and run the AVD target core scenario for both session hosts in question. Please advise if any additional items would be beneficial.

Could you please provide a secure transfer location for the zip of the logs extracted to be uploaded to for both 4-5 & 4-7 session hosts.

Thank you.

Prrudram-MSFT 25,881 Reputation points

2024-08-09T10:26:26.2833333+00:00

Hi @Addison McDermid

Please see my private message if you are unable to raise a support case.

Addison McDermid 0 Reputation points

2024-08-13T23:10:42.3033333+00:00

Hi Prrudram,

I cannot see your private message, perhaps it has expired.
Could you please send a new private message.
Apologies I wasn't at work on Monday.

Addison McDermid 0 Reputation points

2024-08-14T23:43:52.51+00:00

Hi @Prrudram-MSFT ,

The MSRD Collection has been run on both of the session hosts.

https://tecalaict-my.sharepoint.com/:u:/r/personal/addison_mcdermid_tecala_com_au/Documents/Documents/Public/MSRD-Results-A-VDI-POOL4-5-20240809_163308.zip?csf=1&web=1&e=TCU3U6

https://tecalaict-my.sharepoint.com/:u:/r/personal/addison_mcdermid_tecala_com_au/Documents/Documents/Public/MSRD-Results-A-VDI-POOL4-7-20240809_163739.zip?csf=1&web=1&e=omV5v9

Please review the results and look forward to hearing from you.

Prrudram-MSFT 25,881 Reputation points

2024-08-16T08:35:00.21+00:00

Hello Addison McDermid

I am unable to access the logs, we need to get these logs shared with support team for diagnosis. I would recommend you open an azure support case. If you don't have the ability to open a technical support ticket, please let me know and I can help you with one time free support.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

VDI Session Host health alerts in event viewer, how to resolve

1 answer

Your answer