Internal Server Error when creating a NetworkWatcher Reachability Report

Question

question

MunzHeikoFIT2-7782 asked Apr 14, '22 LuisRodriguez-MSFT edited Apr 19, '22

Internal Server Error when creating a NetworkWatcher Reachability Report

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

· 3

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LuisRodriguez-MSFT · Apr 16 at 11:53 PM

Hi @MunzHeikoFIT2-7782 if you are interested in measuring the network latency between specific workloads you may want to try the new Azure Internet Analyzer tool (in public preview):
https://docs.microsoft.com/en-us/azure/internet-analyzer/internet-analyzer-overview

If you prefer to explore other options, apart from Psping or AzureSpeed tool you could use Sockperf (Linux) or Latte (Windows):
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-test-latency#tools-for-testing

I hope this helps

1 ·

ChaitanyaNaykodiMSFT-9638 LuisRodriguez-MSFT · Apr 19 at 06:46 PM

Thank you @LuisRodriguez-MSFT, for providing details on the new Azure Internet Analyzer tool (in public preview). I will work with the Doc author and see if we can add a note about this new tool in this Network watcher documentation for calculating latency.

@MunzHeikoFIT2-7782, hope this helps answer your query. Please let us know if you have any additional questions. Thank you!

1 ·

Theodore345-3942 ChaitanyaNaykodiMSFT-9638 · Apr 19 at 07:14 PM

Thanks for mentioning the source links. We were facing this issue from the last 2 week due to which I haven't updated my rabi crops list site. After checking the souce link I got quite enough information that I fixed the issue easily.

1 ·

Answer 1 · 2022-04-15T22:34:20.803Z

ChaitanyaNaykodiMSFT-9638 answered Apr 15, '22 ChaitanyaNaykodiMSFT-9638 edited Apr 19, '22

Hello @MunzHeikoFIT2-7782, 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.

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!

image.png (21.5 KiB)

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question