Azure Update management "failed to start" jobs

Arnaud DEJOIE 6

hi,
I have a problem with update manager :
I have 3 different machines on-premise (CentOS7, Ubuntu 20.04 and windows serveur 2019).
For all, I have Status "Failed to start" after the jobs were scheduled.
I saw this Workspace ID "00000000-0000-0000-0000-000000000000" like in the screenshot below.

tbgangav-MSFT 10,381 Reputation points

2022-07-02T04:06:29.297+00:00

Hi @Arnaud DEJOIE

Did you get chance to review my earlier comment? Let me know if you have any further queries regarding it.

1 answer

tbgangav-MSFT 10,381 Reputation points

2022-06-24T04:45:59.183+00:00

Hi @Arnaud DEJOIE ,

Does the issue still persist? If yes, as per this troubleshooting guide, the "failed to start" error can occur due to various reasons. For more details on cause and resolution, refer this troubleshooting guide.
Please sign in to rate this answer.

1 person found this answer helpful.
Arnaud DEJOIE 6 Reputation points

2022-07-18T12:45:14.99+00:00

Hi,
Sadly this don't resolve my problème :

The machine doesn't exist anymore.
The machine exist

The machine is turned off and unreachable.
The machine is running

The machine has a network connectivity issue, and therefore the hybrid worker on the machine is unreachable.
The machine is connected to Internet and there is no proxy

There was an update to the Log Analytics agent that changed the source computer ID.
No major update was made on the VMs and Log Analytics agent make inventory of updates and programs that are installed.

Your update run was throttled if you hit the limit of 200 concurrent jobs in an Automation account. Each deployment is considered a job, and each machine in an update deployment counts as a job. Any other automation job or update deployment currently running in your Automation account counts toward the concurrent job limit.
There are Three VMs for testing the solution (Azure update management), so the limits are far far away

The 3 VMs are a CentOS7, debian and a Windows serveur 2019
all have the same problem.

tbgangav-MSFT 10,381 Reputation points

2022-07-21T15:44:36.47+00:00

Hi @Arnaud DEJOIE ,

If you have a support plan then to find the root cause of the issue here, I recommend you reach the Azure technical support team by raising a support ticket as mentioned here.
Sign in to comment