Direkt zum Inhalt

Cyber Protect Cloud Agent automatic update fails

Thread needs solution

We have 3 VMs running Windows Server 2022 and always seem to have a problem with at least one of them when Acronis Cyber Protect Cloud tries to update the agent.

"Task timeout expired. The agent that is responsible for processing the task is not accessible"

Also, when this happens, Remote Desktop service stops responding so I can't access the server and try to manually install. Each time this happens we have to schedule downtime to restart the VM.

Has anyone experienced this? Does anyone have a solution? Thanks in advance

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 2
Kommentare: 1727

Hello Dustin!

Please note that this issue used to happen with old builds of the agent. If you use an old version please try to update the agents manually one by one.

As alternative, Please try the following workaround 

  1. Stop Acronis Agent Core service (this will also automatically stop Acronis Managed Machine Service);
  2. Stop Acronis Update Controller service
  3. Wait for a few minutes.
  4. Start aakore service (Acronis Agent Core Service)
  5. Start mms service (Acronis Managed Machine Service)
  6. Start Acronis Update Controller service

If the issue persists, please raise a ticket with our support at https://kb.acronis.com/content/8153 .

Best regards.

Thanks Jose. We restarted the whole server and it made no difference. On further investigation it looks like maybe Acronis has reset the firewall rules to default. The Remote Desktop rules were disabled, and a custom database rule that was there before, was completely missing. We'll log a support ticket.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 2
Kommentare: 1727

Dustin Bunyan wrote:

Thanks Jose. We restarted the whole server and it made no difference. On further investigation it looks like maybe Acronis has reset the firewall rules to default. The Remote Desktop rules were disabled, and a custom database rule that was there before, was completely missing. We'll log a support ticket.

Thanks for the information.

Please update the thread with the solution provided by our support. This may help the other users.

Best regards.