For some, the only way to get a physical server up and running again is to force the server off and reboot. Upon reboot, there are some steps you need to take to prevent this from happening again until Microsoft releases another .Net update and a new Azure Connect agent.
What is actually happening
When a server runs out of memory to allocate, a local swap file is used. This causes services to respond sluggishly as programs normally run in memory are being written to disk and must be swapped back into memory as requests are received. Eventually the server is forced to start disabling basic services in an effort to prevent itself from crashing. Once this happens, things like logging into the server to shut it down properly are often not possible.
To work around the issue until replacement updates are released, Microsoft suggests removing the offending KB update and rebooting the server. The exact update to remove depends on the local server operating system. Before removing any updates, first check to find out which update you need to remove based on your unique situation. Once you have located the KB update to remove, remove it and then reboot the server. NOTE: Always be sure you have a reliable and up-to-date backup before performing such tasks as part of your business continuity plan.
Updates are inevitable. Sometimes they address security issues, sometimes they add features, and sometimes they have unintended results. The wide variety of differences among server operating systems, proprietary software and updates applied make it challenging for every update to work seamlessly with every system. This means it is important to know what to do to work around issues as they arise. While this fix is only temporary, it should solve the memory leak issue until new updates are released.
As always, there will be unexpected obstacles when it comes to tech. Knowing how to work around them is key!