Skip to content

Known Issues

Zhidong Peng edited this page May 19, 2021 · 3 revisions

List of known issues:

2.7.41491.1009 - [DllNotFound] Error: System.DllNotFoundException: Unable to load DLL

In our recently releases, we start to add monitoring thread to check the heartbeat timestamp for our main VMAgent service (WindowsAzureGuestAgent); while we decided to take the action to restart the VMAgent service if its heartbeat timestamp is too old in 2.7.41491.1009. When the customer captured the OS image with VMAgent version 2.7.41491.1009 and re-use it to create new next VM, our VMAgent self-update logic detects if there is a new version available, it will stop the main VMAgent service and delete the folder too. While when the new VM starts, our heartbeat monitor thread also detects the main VMAgent service needs restart. There will be some chance, the heartbeat monitor thread restarted the VMAgent service while the self-update is deleting the folder, which cause our main VMAgent service failed to process the goalstate with error "Unable to load Dll".

We aware this issue and new version 2.7.41491.1010 to not restart the main VMAgent service. While your VM may stuck after self-update from 2.7.41491.1009 to 2.7.41491.1010. The quick mitigation could be restart our main VMAgent service (WindowsAzureGuestAgent).