Error Id: 28040 | Azure error message: 'Multiple VMExtensions per handler not supported for OS type 'Windows'. VMExtension 'InplaceOSUpgradeCleanUp' with handler 'Microsoft.Compute.CustomScriptExtension' already added or specified in input.'.

Gorav Gandhi 20

I'm using Azure Migrate to migrate and upgrade Windows Server 2016 to 2022. All works fine except the OS Upgrade, which failed with following error:

Error ID 28040
Error Message An Azure Resource Manager operation failed.
Possible causes Azure error message: 'Multiple VMExtensions per handler not supported for OS type 'Windows'. VMExtension 'InplaceOSUpgradeCleanUp' with handler 'Microsoft.Compute.CustomScriptExtension' already added or specified in input.'.
Recommendation Please resolve the error and try the operation again.

Is this a known issue and resolution? Thanks

SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2024-03-14T10:21:16.4333333+00:00

@Gorav Gandhi Thank you for reaching out to us on Microsoft Q&A platform.

I understand that you are using Azure Migrate to migrate and upgrade Windows Server 2016 to 2022. While upgrading OS you are getting an error message "'Multiple VMExtensions per handler not supported for OS type 'Windows'. VMExtension 'InplaceOSUpgradeCleanUp' with handler 'Microsoft.Compute.CustomScriptExtension' already added or specified in input."Compute Team has confirmed that Only one version of an extension can be installed on a VM at a time. This is by design, and we cannot have two different versions of extension type : customscriptextension on same VM. If we try to install the same, we will get this error : Multiple VMExtensions per handler not supported for OS type 'Windows'. VMExtension 'CustomScriptExtension' with handler 'Microsoft.Compute.CustomScriptExtension' already added or specified in input.

However, the experience should be different while using Azure Migrate for server migration and in-place OS upgrade.

I'm checking with the concerned team on this. Shall get back to you once I have a concrete information to share here.

In the meanwhile, please try the workaround posted in the following links:

https://stackoverflow.com/questions/64909984/multiple-vmextensions-per-handler-not-supported-for-os-type-windows-terrafor

https://mitesh1612.github.io/blog/2021/05/14/vms-with-multiple-extensions

https://www.linkedin.com/pulse/azure-install-multiple-custom-agentsscripts-using-arm-upreti

Hope this helps!
Gorav Gandhi 20 Reputation points

2024-03-14T10:43:47.5033333+00:00

@SadiqhAhmed-MSFT Thanks for the response and sharing the links. Though all shared links explains how to run two version of same VM extension, but I'm not trying to do do that. It's all automatically executed by Azure Migrate during Test Migrate and was expecting the migration & OS upgrade process to be seamless. Screenshot below for reference:

Are there any configurations which can be enabled to avoid this?
Gorav Gandhi 20 Reputation points

2024-03-14T11:57:58.2833333+00:00

Hi @SadiqhAhmed-MSFT Thanks for the reply and sharing links. Though all the links explains how to run two versions of same VM Extension, but I'm not trying to do that as just executing Azure migrate and expecting it to seamlessly migrate the VM and upgrade the OS instead of failing with this error. Are there any configurations in Azure Migrate, which can be used to avoid this error?
SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2024-03-14T18:49:04.9233333+00:00

@Gorav Gandhi I got it. Allow me some time and I will get back to you with an update.
SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2024-03-15T07:09:46.1266667+00:00

@Gorav Gandhi Can click on "Completed with errors" and share the details of the error message?
Gorav Gandhi 20 Reputation points

2024-03-15T07:18:11.7+00:00
@SadiqhAhmed-MSFT It shows the same messages as put in my initial question. Pasting again for reference:

Error ID 28040

Error Message An Azure Resource Manager operation failed.

Possible causes Azure error message: 'Multiple VMExtensions per handler not supported for OS type 'Windows'. VMExtension 'InplaceOSUpgradeCleanUp' with handler 'Microsoft.Compute.CustomScriptExtension' already added or specified in input.'.

Recommendation Please resolve the error and try the operation again.
SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2024-03-15T10:59:19.78+00:00

@Gorav Gandhi Checked with internal sources about this issue and got to know that they are aware of this issue and working on a fix that will be deployed next month.

Note: It is actually not an issue. You may want to check from the VM blade in Azure portal to verify if the OS upgrade has happened or not.
Gorav Gandhi 20 Reputation points

2024-03-18T06:36:02.34+00:00

@SadiqhAhmed-MSFT Thanks for the reply. The OS for the VM still shows 2016. I have logged in to the VM and validated as well.

Is this a known issues? As you mentioned it will be fixed by next month. I'm assuming if known then everyone should be facing this.
SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2024-03-18T08:26:29.3166667+00:00

@Gorav Gandhi Thanks for the information. Some other error code will be there in error details.

Prior to this particular error, which will point out to the actual failure.
SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2024-03-20T10:11:14.9766667+00:00

@Gorav Gandhi Were you able to find the error details?
Gorav Gandhi 20 Reputation points

2024-03-21T11:06:35.2266667+00:00
@SadiqhAhmed-MSFT There were no other errors. I raised a ticket with MSFT support team and after validating the logs from backend following error was identified:

"Deletion of custom script extension with name InplaceOSUpgrade of virtual machine XXXX in the resource group XXXX of subscriptionId XXXX failed. | Exception: Azure status code: Forbidden. Arm error code: AuthorizationFailed. Arm error message: The client 'XXXX' with object id 'XXXX' does not have authorization to perform action 'Microsoft.Compute/virtualMachines/extensions/delete' over scope '/subscriptions/XXXX/resourceGroups/XXXX/providers/Microsoft.Compute/virtualMachines/XXXX/extensions/InplaceOSUpgrade' or the scope is invalid. If access was recently granted, please refresh your credentials..."

Solution Provided: Please go to subscription > Choose the subscription > Add Role assignment > Contributor/Owner role to the application Hyper-V Recovery Manager . Then re-try test failover.

Observation:

Upgrade was successful after giving permission to this Enterprise application.

It is an Enterprise application with type as Microsoft and is a default application in all tenancy.

MSFT support team agreed this step is no updated in current public documentation.
SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2024-03-21T18:02:51.63+00:00

@Gorav Gandhi Thanks for the update! Glad to hear that the issue is resolved :)

I'm re-posting your answer for the benefit of other community members on this platform.

Accepted answer

SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2024-03-21T18:05:27.1033333+00:00
"Sharing the solution with broader community"

There were no other errors. @Gorav Gandhi raised a ticket with MSFT support team and after validating the logs from backend following error was identified:

"Deletion of custom script extension with name InplaceOSUpgrade of virtual machine XXXX in the resource group XXXX of subscriptionId XXXX failed. | Exception: Azure status code: Forbidden. Arm error code: AuthorizationFailed. Arm error message: The client 'XXXX' with object id 'XXXX' does not have authorization to perform action 'Microsoft.Compute/virtualMachines/extensions/delete' over scope '/subscriptions/XXXX/resourceGroups/XXXX/providers/Microsoft.Compute/virtualMachines/XXXX/extensions/InplaceOSUpgrade' or the scope is invalid. If access was recently granted, please refresh your credentials..."

Solution Provided: Please go to subscription > Choose the subscription > Add Role assignment > Contributor/Owner role to the application Hyper-V Recovery Manager . Then re-try test failover.

Observation:

Upgrade was successful after giving permission to this Enterprise application.

It is an Enterprise application with type as Microsoft and is a default application in all tenancy.

MSFT support team agreed this step is no updated in current public documentation.

Hope this helps others on this community who may be looking for a solution to this problem.

If the response helped, do "Accept Answer" and up-vote it
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Error Id: 28040 | Azure error message: 'Multiple VMExtensions per handler not supported for OS type 'Windows'. VMExtension 'InplaceOSUpgradeCleanUp' with handler 'Microsoft.Compute.CustomScriptExtension' already added or specified in input.'.

0 additional answers