Could not stop job

[HN1396]

Hello

I have an Exchange job running an i could not stop ist. Whether reboot or restart services nothing helps. I cannot delete my entire org, it says job is running.
Where can i hard delet this one?

I never see this before. How can a job survive an entire server reboot???
No other jobs can run then.

Best ragards,

Hendrik

[Mildur]

Hello Henrik

Welcome to the forum. Could you please confirm the build level you are currently running?
The issue you're describing should be resolved with 8.0.3.1044 or later.

Additionally, please share your case number, as it is requested for every technical issue. We cannot troubleshoot technical issues over a forum topic.

Thank you,
Fabian

[HN1396]

Hello Fabian,

ok, i will do so.

Come Back,

Thanks

[Mildur]

Hi Hendrik

Thank you.
According to the case notes, our customer support team was able to assist you.

Best,
Fabian

[aeph]

We have this issue once a week. We have the newest update installed.

"Solution" is to empty jetstream folder.

Is this currently being worked on? It is a bit time-consuming to constantly delete this folder and restart all proxies. We have 5 proxies, which takes time. Also, due to very large jobs, we only have a very small window without having to interrupt working jobs.

A solution that allows stopping via the graphical user interface would be desirable.

[Polina]

With the next release, we plan to deliver some improvements that should resolve such issues in most cases.

[utleyab]

I'm also having issues with this, but my version of the VBM console is 8.1.305 - and while I know there is a version higher than this, I'm apprehensive about upgrading when the job isn't stopping regardless of services or reboot. My case number is #07612441 - was wondering if anyone had any ideas while I wait for a response from the engineer helping me.

[sandsturm]

same issue here and my VBM365 environment is running on version 8.1.1.159 P20250328

[Polina]

@sandsturm
Could you please share your support case ID?

[sandsturm]

Case #07728597

[sandsturm]

I could solve the issue with the help of veeam support by doing the following:

1. Stop the NATS and VB365 services.
2. Delete the contents of the folder C:\ProgramData\Veeam\Backup365\nats\jetstream\$G\streams.
3. Restart NATS and Veeam services.