Jobs stalling with VBM365 Failed Nothing to Process - Build 8.1.1.159

[claudiohipolito]

We have backup jobs on the VBM server showing a nothing to process error. The job gets stuck in detecting mode and then fails immediately.

I believe the error is due to connectivity with the NATS Server. This has happened before and we resolved it by updating the version, but we are now on the latest release 8.1.1.159, replacing 8.1.0.3503, which caused the same error.

We have backup jobs on the VBM server showing a nothing to process error. The job gets stuck in detecting mode and then fails immediately.

I believe the problem is due to connectivity with the NATS Server. This has happened before and we resolved it by updating the version, but we are now on the latest release 8.1.1.159, replacing 8.1.0.3503, which caused the same error.

In our environment, the NATs Server was previously installed on port 4225, since port 4222 was already in use by a vulnerability management solution.

An old workaround was to delete the cache from the nats-server stream folder available in the C:\ProgramData\Veeam\Backup365\nats\jetstream\$G\streams directory, but this folder only exists when NATS-Server is installed directly through the VBM setup.

Registered case 07694872 in support but no workaround recommendations for now.

Thanks.

Cláudio Hipólito

[t7MevELx0]

I've been deleting the NATS streaming directory and restarting services for weeks now. They need to pull this version/build, as it is clearly defective.

Case #07674412 — Issue "Case #07670283"

The last "fully" working version was 8.05.

[raftbone]

I'm having the same issue. Some jobs seem to be stuck, but when I check the logs on the proxy, they seem to be still running.
As soon as I restart the main Veeam M365 server, the job status is updated on the console. Seems to be a communication issue between the proxies and the main server.

However, some other jobs (especially copy job) are completely stuck even after rebooting the main server. Those issues really needs to be addressed. Having tons of issues since upgrading to version 8.

[jokester6633]

Good luck. Tech support has not moved much on my case that has been open since beginning of February.

[donkeymagic]

We had a similar issue recently which was caused by installing a recent .net framework updated but not an optional rollup update for Windows. We had very similar issues in that backups would start and just do nothing (only affecting a single organisation) with the others running ok. Veeam support went round and round in circles and couldn't diagnose the issue (firewall, ports, permissions etc) but I ended up installing the optional windows update and it resolved the issue.

The .net update was KB5057056 with the windows rollup being KB5055612. The solution has been perfect since but it gave very similar results before hand in that the NATS server wasn't responding and/or passing on the information to the proxy server and we had to delete the cache to keep some stability in the solution.

[t7MevELx0]

Those updates (KB5057056 and KB5055612) are not showing up in our systems when I search for them. This issue is also occurring across multiple environments and operating systems. That includes environments where NATS is installed on Windows, as well as one where NATS is running on Ubuntu.

I'm still waiting on RnD to get back to me.

[donkeymagic]

While that did fix the issue for us for a short period of time the issue is back again. I raised a case with Veeam on this last week and have yet to get any feedback, I've so far had the usual rubbish response of "this is an initial contact but an engineer will be in touch", I'm starting to get completely fed up with this as this is far too common with Veeam now specifically for M365. I've complained to our account manager, raised it with a manager via the case support system but nothing changes. Veeam used to be our benchmark for support with issues resolved quickly but I dread having to raise anything now for M365 as I have to fight for updates, its seriously making us consider a different solution for all our customers moving forwards as it doesn't appear that Veeam can support their product (again specifically M365, VBR we still get great support).

[donkeymagic]

So we have been provided with a hot fix today specifically for an error in the back end that has been affecting our client and so far it has resolved the issue. The issue has been caused by the following warning in our backups.

[15.05.2025 08:31:34.236] 19 (1) e289e2818273f3d46c18e5563e083274:bfab1a3dcd76afe4 [Info] Cancellation link added for object: b7d1575d-d4cd-1f2b-f82b-982eb503b584

While this is an informational warning it's actually been the cause of the issue so I would suggest checking your backup logs to see if you have the same error, if you do quiz tech support about the hot fix.

[raftbone]

Thanks for your update. Nice to hear that there is a progress on this issues. Hopefully this fix will be officially released soon, since we always have to create support ticket via our Veeam Partner company to get support.