Internal Server Error when creating a NetworkWatcher Reachability Report

Heiko Alexander Munz 21 Reputation points
2022-04-14T05:48:11.807+00:00

When I execute the following commands in the Azure PowerShell (in the Azure Portal) I get an error.

>New-AzResourceGroup -Name rg-latencydemo -Location westeurope

>New-AzNetworkWatcher -Name nw-latencydemo –ResourceGroupName rg-latencydemo -Location westeurope

>$nw = Get-AzNetworkWatcher -Name nw-latencydemo -ResourceGroupName rg-latencydemo

>New-AzNetworkWatcher -Name nw-latencydemo –ResourceGroupName rg-latencydemo -Location westeurope

The last command results in...

Get-AzNetworkWatcherReachabilityReport: Long running operation failed with status 'InternalServerError'.
StatusCode: 500
ReasonPhrase: Internal Server Error
ErrorCode: InternalServerError
ErrorMessage: An error occurred.
Azure Network Watcher
Azure Network Watcher
An Azure service that is used to monitor, diagnose, and gain insights into network performance and health.
169 questions
Accepted answer
  1. ChaitanyaNaykodi-MSFT 26,101 Reputation points Microsoft Employee
    2022-04-15T22:34:20.803+00:00

    Hello @Heiko Alexander Munz , Welcome to the Microsoft Q&A forum

    I tried the Get-AzNetworkWatcherReachabilityReport on my end and got the internal server error as well. As per this documentation looks like this feature has been deprecated, hence the internal server error.

    193563-image.png

    A work-around in this scenario will be to use tools like PsPing to test the latency or to use some open source projects on internet which offer similar functionality like https://www.azurespeed.com/Azure/Latency.

    Hope this helps! Please let me know if you have any additional questions. Thank you!

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.