Job cannot be started; Timeout

[wiiaam]

Hi there

Installed Veeam Backup for Windows 2.1.0.423 on 2 PC's which are mostly identical.
Wind 10 Pro 64-bit, all updates. Backingup to a shared NAS-folder.
Scheduled backups monday to friday, every saturday a full-backup.

On one PC it works without hassle....
On the other it works 2-3 times, then "Job cannot be started, Timeout"
After a restart, it works for 2-3 days, then timeout again.

Did a rebuild SQL-database with regedit 3-4 times... problem persists
Uninstalled and reinstalled, no luck

I know, that I had problems before on the same machine with Win 7 internal backup-solution.
Maybe the same problem, that a daemon or service not started

Any help...??

Thx a lot

[Dima P.]

Hello wiiaam.

This might be a connectivity issue. Can you please double check that your NAS device is reachable from the agent side (all ports are opened and your firewall is not blocking the connection)? Thanks in advance.

[wiiaam]

Hi Dima

Thx for answering.

I have 2 PC's, that are backing-up to the same NAS, with a difference between an hour in the night.
NAS is not going to sleep, never.
1 work all the time, other not. After a restart it works 2-3 days/nights, than timeout.

When I check the tray-monitor, it says "job cannot be started, timeout"
If I say then: "backup now"... nothing happens... only "backup is in progress" above and "not started"

There are 5 VeeamFirewall-Rules in-and out on the PC, all Ports free.....
For testing, I opened all Ports in NAS for the PC's-IP..... no backup....

It has nothing to do with firewall, because 1 PC's is backing up without problems since beginning.
And on the other it works like described sometimes

It has to do with a daemon or service that don't start....

[LThibx]

Has this ever been resolved?
I am having the same problem.
Backing up multiple workstation to NAS.
One workstation runs fine for a few days, then stops processing.
Event Log shows:
Veeam Agent 'Backup Job CBT-HV16DZ1' finished with Failed.
Job details: Job [Backup Job CBT-HV16DZ1] cannot be started. SessionId: [c1cad361-acd1-4a3a-92c5-dcee757e1a16], Timeout: [360.4525594 sec]
Job has failed unexpectedly

Reboot the machine and it runs for few days, then the issue occurs again.
Not seeing anything in the logs folder as no newer log exists after the date of the last time it ran successfully. Only evidence is what is in the event log which is shown above.
At this moment upgrading from v2.0.0.700 to 2.1.0.423.
I am not thinking that this will resolve the issue as original poster stated he was already running this version.

Hope that Veeam can determine why this is happening.

Thanks
Lonnie

[mweissen13]

We are having the exact same issue on one Workstation. But we are backing up to a Cloud Connect repository. Still waiting for Veeam support to solve it. Case # 04194219
This problem has persisted through all updates of Veeam Agent and Windows 10 we went through in the last year. The only workaround that helps is rebooting the PC. But we cannot do this daily on a regular basis.

[AVIConsult]

Is there solution?

[Natalia Lupacheva]

Hi @AVIConsult,

To be absolutely sure you see what's going on, I would recommend to open a Support case. Support team would be able to check your logs and find the exact reason of this problem.

Some issues are solved after increasing the Desktop heap size but I would not say it's a panacea.

Thanks!

[mweissen13]

In our case, in the end, the only thing that helped was indeed increasing the Desktop heap size. We had to increase it to 8192 - 2048 as suggested in kb1909 was not enough. As always, YMMV