Share via

Can't start vm (Resource is in Failed state)

  • Article

Question

Friday, June 7, 2019 2:15 PM

I was using my VM with Windows 10 for about an hour today in the morning. Almost all was ok, except one reboot because a connection was lost or something like that. However, I couldn't start or restart this virtual pc again after 2 hours. I even can't resize my VM to use more VCPUS and RAM. I always get an error like that:

Failed to resize virtual machine '****' to size 'Standard B4ms'. Error: Cannot proceed with operation because resource **** used by resource /subscriptions/********/resourceGroups/Test/providers/Microsoft.Network/networkInterfaces/******* is not in Succeeded state. Resource is in Failed state and the last operation that updated/is updating the resource is PutPublicIpAddressOperation.

How to solve this problem?

All replies (12)

Friday, June 7, 2019 2:28 PM âś…Answered

Hi, 

  1. Go to https://resources.azure.com/
  2. Select your subscription
  3. Navigate to your NIC by Subscription --> Resource Group --> Providers --> Microsoft.Network --> Your NIC
  4. Then flip the Read/Write switch on the top and click on edit and do a PUT operation
  5. Once that is done, try turning ON your VM.

If you see any error, paste it here. 

Regards, 

Msrini

Sunday, June 9, 2019 12:57 PM

Hi, 

Do you have any update for me on this thread?

Please 'Mark as answer' if any of the replies helped, so that others in the community who are looking for similar question, can benefit from it.

Regards, 

Msrini

Monday, June 10, 2019 6:06 AM

Hi Msrini

I have the same error. I followed your instructions but no success.

Unfortunately, error still exists.

Yaniv

Monday, June 10, 2019 6:22 AM

Can you send me your subscription ID to [email protected]?

I can take a closer look. If this requires a deeper investigation, I can raise a support ticket for you. 

Regards, 

Msrini

Tuesday, June 11, 2019 8:22 AM

Sorry for a delay with my reply.

I see the following picture after following your instructions:

Not sure what to do further.

If I expand the networkInterfaces node, I see two NIC IDs (if this is what I really need). However, they differ from what I see in the Settings for my VM (the Network Interface field in the Networking blade).

Just in case, I did that PUT operation for the two child nodes of networkInterfaces as you usggested, but it didn't help. Still get the same Resource is in Failed state error.

Tuesday, June 11, 2019 8:30 AM

Hi, 

Now expand Network Interface and then selcet the NIC which is attached to your VM in question.

  1. Then flip the Read/Write switch on the top and click on edit and do a PUT operation
  2. Once that is done, try turning ON your VM.

Regards, 

Msrini

Tuesday, June 11, 2019 10:37 AM

Have you read my reply carefully? I wrote that I expanded networkInterfaces and did what you had asked for the two child nodes, but it didn't help.

Tell me how to find my NIC for the problem vm. Perhaps, I am moving not in the right direction.

Tuesday, June 11, 2019 10:53 AM

Hi, 

I haven't seen your edited post when I answered back. If the PUT operation didn't help, then I need to find what made this NIC to Failed state. 

This required deeper analysis, so can you raise a support ticket?

If you don't have a support plan, drop an email to [email protected] with your subscription ID and the Link of this thread. I will enable one time free support to you. 

Regards, 

Msrini

Tuesday, June 11, 2019 11:45 AM

Sent you a letter as suggested. TIA

You also didn't tell me how to find the NIC for the problem vm. I wrote that I saw two different NICs under networkInterfaces. Is it ok?

Tuesday, June 11, 2019 12:08 PM

In the Portal, select your VM which is problematic. Then click on the Networking tab, and then select the NIC which is attached to it.  Yes, it is fine. If you mention the VM name, we can find the NIC. 

Regards, 

Msrini

 

Friday, June 14, 2019 10:40 PM

Any update on this? 

Monday, June 24, 2019 10:11 AM

The guy from the support team helped me to solve the problem in chat. We used the 'EDIT and PUT' way suggested by msrini for all related network resources until the vm started to function properly.