Operation Cancelled By User?

[A's_Tech]

Hi all,

I'm probably missing something but I need help. I'm brand new to Veeam and trying to backup one VM in VMware and the job keeps failing with: Operation was canceled by user (Veeam.Backup.Common.CStopSessionException)

This is straight from the job log. I'm sure I'm missing something simple; can anyone help?

Thanks,

Bergy

[Gostev]

Hi, is it possible that somebody else is stopping the job from a different RDP console? Believe or not, we have had quite a few support cases when this was the reason.

[A's_Tech]

Gostev,

It appears that it was a production-time problem; I honestly couldn't tell you if a user was physically cancelling the job or if there was too much activity on the SQL database, but I setup the job to run automatically overnight and it was successful.

Thanks for your help!

Bergy

[dellock6]

I don't remember the actual error statement, but maybe there is a configured backup window and it timed out, forcing the job to be cancelled? Just guessing since you say that overnight the job completed successfully.

Luca.

[A's_Tech]

Luca, you are a genius! I was cancelling my own job!

Feeling like an idiot...

Bergy

[dellock6]

I'm not a genius and you are not an idiot, I've only been there before you in that error.
I remember somewhere in these forums a feature request about changing the error message if the job is canceled due to limited time window to a different message than "cancelled by user" to something like "Job was terminate because it exceeded allowed backup window"...

Glad you nailed the cause!
Luca.

[Gostev]

Are you using v7? I am surprised this is still not fixed, as I did discuss this issue with the team before... I am not tracking minor issues like that though. I will follow up, sorry for the inconvenience.

[veremin]

I’ve just checked this scenario with version 7 and the obsolete message “Canceled by user” seems still to be there. So, thank you for pointing it out; highly appreciated.

[mlivingston]

+1 this was also plaguing my new installation, setup with an overnight schedule then tested it during work hours and it fails with 'canceled by user'. Disabling schedule let the test proceed normally.

[foggy]

The message is scheduled to be fixed in one of the future versions.

[stevenrodenburg1]

I've seen this on Backup Copy jobs.
Example: a backup is scheduled for 08:00, it's copy job was also scheduled for 08:00. So every morning, i got an email saying that the copy job was "cancelled by user".
This happened every day with three copy jobs only.
During their retries, the copy jobs were successful.

I thought a burglar was sneaking in every morning (or i was sleep-walking), canceling my copy jobs. Never caught the sneaky b*stard

[veremin]

Yep, we're aware of this rather confusing stop event and planing to fix it in one of the next product releases. Thanks.

[tinto1970]

i've just falled in the same pitfall (running ver. 7.0.0.833)

thanks to Luca for existing

[jamesharper-bsol]

Hi Guys,

Just for info it still exists in Veeam 7 patch 4 (7.0.0.871). Again it was a backup window cancelling the job I was trying to test run

[veremin]

We're still planing to fix in the upcoming release. Thank you for raising the question again.

[WolfgangA]

What a silly error message. Just fallen into the same pitfall!

Could somebody raise a feature request to make a more meaningful error message like "Job cancled because out of service window" or something like that... this costed me quite some time to find it out

Veeam 7.0.0.690

[veremin]

Could somebody raise a feature request to make a more meaningful error message like "Job cancled because out of service window" or something like that

There is no need for that, as we're already aware of this rather confusing message and this should already be fixed in v8 code. Thanks!

[vadm1018]

How hard is it to patch for version 7? I just wasted 10 minutes of my life looking at someone else's setup that had such an issue. It shouldn't take your devs that long to update the code base with a more meaningful error message.

[foggy]

We don't typically produce hotfixes for such minor issues. Not sure why it slipped our attention prior releasing the latest v7 patch, but this should be addressed in v8 code, as Vladimir has stated above.

[gwntc]

I'm guessing that if the backup copy job runs into a VM that is being backed up it would also generate this error. Am I correct?