Azure file server error causing VM to become unresponsive.

Question

I have a windows 2016 azure vm file server that has been running without issue since it was spun up in 2018. Recently, the vm has become unresponsive after several days. In the Operations Manager event logs I found two entries could be contributing.

Log Name: Operations Manager
Source: Service Connector
Date: 3/27/2022 6:18:35 PM
Event ID: 4004
Task Category: Communication
Level: Error
HTTP operation failed with error "Not enough storage is available to process this command." (8L) ...

Followed shortly by:

Log Name: Operations Manager
Source: HealthService
Date: 3/27/2022 6:19:06 PM
Event ID: 4502
Task Category: None
Level: Error
A module of type "Microsoft.EnterpriseManagement.HealthService.HealthAssessmentData.HealthAssessmentDataSource" reported an exception System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 169.254.169.254:80

I've read several articles about communication errors to the mentioned IP, but most discuss this as part of initial setup of the server (NSG blocking) and nothing about already working NSG setups.
Could it be sessions not being pruned after a client system disconnects? Thoughts about the cause and possible resolutions?

Answer 1

Hello @Prrudram-MSFT ,
I have applied the IRPStackSize registry update to the server and set the value to 20. So far, no additional events have been recorded.