How to fix the issue of " Agent status is not ready "

Question

My virtual machine was running successfully and the very next day it didn't connect neither with RDP nor with public ip through remote desktop. I tried to connect it on different devices but no success. I troubleshoot the issue according to provided instructions, even redeploy & reapply it but still couldn't connect it. Its completely unable to understand for me that a running machine got stuck. You can see more clear picture of the issue in attached screenshots.

Some more details of the virtual machine are below.

Operating system: Windows

VM generation: V1 Size: Standard DS1 v2

VM architecture: x64 vCPUs: 1

Agent status: Not Ready RAM: 3.5 GiB

Agent version: Unknown Source image publisher: MicrosoftWindowsServer

Hibernation: Disabled Source image offer: WindowsServer

                                                                            Source image plan:    2016-Datacenter

Looking forward to hearing from you soon to resolve this issue on priority basis. Thank You very much.

Answer 1

Hi Hamza Malik

Following is an additional test to continue the troubleshooting. If the server has lost wireserver connectivity, RDP might fail.

Test WireServer connectivity

To run successfully, Guest Agent requires connectivity to the WireServer IP (host IP) address 168.63.129.16 on ports 80 and 32526. For instructions about how to test connectivity to this IP address, see the Troubleshoot connectivity section of What is IP address 168.63.129.16?

If any of the tests in that section don't connect, check for issues that might cause any of the following components to block access to IP address 168.63.129.16:

• A firewall
• A proxy
• An application

If you are not able to access the above details somehow, I suggest you to create a test VM in the same network and try accessing the problematic VM from there. Ideally, http://168.63.129.16/?comp=versions should be accessible from web browser of any VM. If suppose, the above address is not accessible, RDP might fail. You can see, if DHCP is enabled in the server's network interface?

Check it?

netsh interface ip show config

Enable DHCP

netsh interface ip set address name="<name-of-the-interface>" source=dhcp

Have you also seen the following NSG settings applied correctly?

Hope this helps.

---

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Before raising a case, I am suggesting following the steps below and if that doesn't help, raise a case with Microsoft support to expediate the fix

1. Create a new VM in the same virtual network and with a local IP in the similar range of the problematic VM
2. Try to access the VM from the new VM through RDP using the local IP address
3. Check the files under the following folders and see the exact issue for this error and troubleshoot accordingly C:\WindowsAzure\Logs\WaAppAgent.log C:\WindowsAzure\Logs\TransparentInstaller.log
4. If that doesn't help, I suggest flowing the steps explained in 'Solution 9: Copy a working machine.config file to the VM, and then restart the Guest Agent services' in the article: windows-azure-guest-agent
5. If the rdp connectivity is not working, you can try accessing the folders within the VM by accessing the files like <computer-name or IP>\C$ and check the above logs indicated in the step 3

If you are facing issues in following the above steps, Azure Support ticket can be raised here: https://azure.microsoft.com/en-us/support/create-ticket