patches failed for virtual machine

Question

patches failed for virtual machine

Varma 1,495

I have set up Maintenance configuration with dynamic scope for the particular resource group, here are the maintenance configuration details: User's image

and when i navigated to HISTORY to see virtul machine patch status , I see 1 out 19 , only 1 succeded and 18 failed. 1. Please help us in fixing this issue why it is failed? 2. I have set up 3 hours 55 min. is this time not enough? since what we gave is maximum time MS gave, how we can fix if it is time issue? here are the log details: User's image

and User's image

and

AnuragSingh-MSFT 21,546 Reputation points Moderator

2024-01-18T06:50:35.5533333+00:00

Varma, Following-up to check if you had a chance to review the answer provided.

If the answer did not help, please add more context/follow-up question for it, and we will help you out. Else, if the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.

2 answers

Your answer

AnuragSingh-MSFT 21,546 Reputation points Moderator

2024-01-18T06:50:35.5533333+00:00

Varma, Following-up to check if you had a chance to review the answer provided.

If the answer did not help, please add more context/follow-up question for it, and we will help you out. Else, if the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.

Answer 1

JimmySalian-2011 42,491

== Hi, Can you check if the patches were downloaded on the servers? Also check the patches size and probably you will have to increase the time window in this instance if the servers are not updated in a while this will contain multiple updates and patches, so try to increase the window and do the maintenance over the weekend so starting from Friday evening as an example and let it run, however do not reboot the servers as this will impact the applications. Hope this helps. JS Please Accept the answer if the information helped you. This will help us and others in the community as well.

Varma 1,495 Reputation points

2024-01-14T17:58:12.02+00:00
HI Jimmy,

1.

But while configuration maintenance configuration , I believe maximimum allotted time is 3 hrs 55 minutes in the schedule section?

can we give more than that? if yes how we can give?

Where exactly to check whether it is downloaded or not in the server?
Varma 1,495 Reputation points

2024-01-16T06:46:27.5066667+00:00

HI Anurag, Did you get a chance to look my previous comment?

Answer 2

AnuragSingh-MSFT 21,546 Moderator

Varma, thank you for the reply. To answer your questions:

The maximum maintenance configuration window allowed is 235 minutes (3 hours, 55 minutes) for on demand update as well as the scheduled update. For more details, see Install updates on a single VM, the same restriction is also available when configuring maintenance window which restricts to 3 hours 55 minutes. This cannot be changed.
Regarding logs, you can review the logs in the location below for Windows VMs. C:\WindowsAzure\Logs\Plugins\Microsoft.CPlat.Core.WindowsPatchExtension<version> For other types of machines, the log path differs, and you can review the following link for more details - General troubleshooting Regarding your specific issue of the large number of updates (approx. 19) pending to be installed, I would suggest installing them in chunks of 3-4 updates at a time using the specific KB/category filters. Another option would be to install these updates in chunk manually using "One-time update" option. Hope this helps.

Varma 1,495 Reputation points

2024-01-15T13:48:59.4233333+00:00

HI ANurag, Could you please clarify my follow up questions: 1. is 1 out 19 is it machines or pending updates? what exactly it indicates? 2. is there any reference document saying patches time maximum is 235 minutes? 3 is there any reference document saying apply one time schedule when time crossed 230 minutes? 4 what could be the cause for the above patched failed? 5. what could be the cause in my case, which catagiry in the document you have shared

6. Below is the message I am seeing what does it indicate and what is the fix?
AnuragSingh-MSFT 21,546 Reputation points Moderator

2024-01-16T07:06:58.9866667+00:00
Varma, thank you for the reply. Please find the response below:

Apologies for the miss here. I did not see that last small screenshot posted and assumed based on your question that you were talking about 19 updates. Based on the screenshot, it says only 1 machine's update was successful and 18 other machines could not be updated.

Review the point 5 available in the following doc - Install updates on VM

There is no such doc stating to apply 1 time schedule. The reason I suggested this approach was because the scheduled maintenance configuration would have configured for a broad set of categories. With the assumption that the update might have failed because of the large number of updates available (which was an incorrect assumption from my part), I suggested "One-time update" to selectively install updates.

For more details about the reason for patch failure, I would suggest reviewing the logs created by Azure Update Manager. The log locations, depending on machines, are available here - https://learn.microsoft.com/en-us/azure/update-manager/troubleshoot#general-troubleshooting I also looked at the KB which failed installation and based on the KB doc, there are additional reasons why it could fail. For more details, see KB5034439: Windows Recovery Environment update

For more details, I would suggest reviewing the log directory as available in this doc (note there are 2 different log directories) - Azure Windows VM

The screenshot just mentions that the agent in charge of execution did run and there was no error while running it - exit status code "0" means successful execution. However, this only tells you that agent ran - there might be errors during its execution with respect to patch installation and that log will be available in either of the following file:

WindowsUpdateExtension.log: Contains information related to the patch actions. This information includes patches assessed and installed on the machine and any problems encountered in the process.

CommandExecution.log: There's a wrapper above the patch action, which is used to manage the extension and invoke specific patch operation. This log contains information about the wrapper.

These logs and files should help you understand what was happening during the scheduled maintenance and what might have failed. The log files might be huge, therefore, to begin with, I would suggest looking at lines only during the schedule and filter for [Warn] and [Error]. This should get you the initial assessment of the failures/timeouts if any.

Hope this helps.

In case you need further assistance, I would suggest opening a support ticket so that these logs and environment can be assessed 1:1 and troubleshooting can be performed as required. In case you face issues opening a support ticket, please let me know.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Varma 1,495 Reputation points

2024-01-19T12:06:11.81+00:00

Hi Anurag, I have tried even one time update for single machine, there also i see time insufficient error. PFA logs and respective screenshot below, and Please suggest fix for this

logs:
Varma 1,495 Reputation points

2024-01-21T06:19:29.27+00:00

Hi Anurang DId you get a chance to look my above thread? I have tried with one time schedule and also with maintenance configuration. in both cases patch installation is failing, I found below info from logs Just adding some more info from logs as below Failed to OpenPackage using worker session [HRESULT = 0x800f0805] InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~x86~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] Parent: microsoft-windows-serverazurestackhcicoredition~31bf3856ad364e35~amd64~~10.0.20348.1, Standalone integration and parent is missing, ignore this parent.
AnuragSingh-MSFT 21,546 Reputation points Moderator

2024-01-30T05:46:35.62+00:00

Varma, apologies for the delayed response.

The first log screenshot shared states that the extension was triggered, and update operation was being executed (no errors here).

In the second screenshot shared above (WindowUpdateExtension.log), there are errors in line 4 and 5 which state that the installation failed. Please review these lines in detail. Also, do review the Application logs from EventViewer around the same time which also contains errors related to installation. These would give you an idea of the reason for failure.
AnuragSingh-MSFT 21,546 Reputation points Moderator

2024-02-02T09:06:20.84+00:00

Varma, Following-up to check if you had a chance to review the answer provided.

If the answer did not help, please add more context/follow-up question for it, and we will help you out. Else, if the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.

Share via

patches failed for virtual machine

2 answers

Your answer