This error message only started popping up after I upgraded from the free version to paid.
I'm currently on v8.0.6392
I've browsed the forums and have probably found every person with this issue on different versions of Reflect.
I've tried all the suggested solutions but nothing has worked.
Trying to create backups on a NAS (which worked fine on free version), credentials are entered correctly.
Backup works fine if ran manually from the Scheduled Backups tab.

I'm out of ideas on how to fix this issue. And also very curious why this would happen when the only change was upgrading from free to paid?

The backup works correctly when you use the Scheduled Backups tab?  So the failure condition is when you invoke it from the Backup Definition Files tab?  That's the opposite of the "typical" problem scenario, because invoking the job from Backup Definition Files would cause the job to run in your own user context, in which case Reflect would have access to network connections open in your user session.  Do you have an open network connection to this network share in your user session?  If so, are you possibly connected to that share using an account that's limited to read-only access as a security precaution?  If so, Windows doesn't support connecting to the same share within the same user context using multiple separate credentials, which means that if there's already an open connection, Reflect wouldn't be able to use the credentials you're storing in the application when running backups within your user context.  It would have to rely on the connection that was already open.  The credentials only come into play when there is NOT an existing network connection open in the user context that's running the backup.

All that said, if that were the problem, I would admittedly have expected an error message more clearly identifying that as the cause, but if the job fails ONLY when run interactively and not when executed as a background scheduled task, that's the only item that comes to mind.

As far as I am aware, there is no open connection to the network share. I did go into the NAS and see that there was a connected user (me) using my 'Windows Backups' folder under 'Resources' (I forgot to screenshot it before I killed it). But the timestamp lined up with when the backup tried running the first time today.


I agree it's odd that it works when run from the Scheduled Backups tab as I've seen in other posts people saying the opposite.
Any of my accounts to the network share have full read/write permissions.
Should Macrium need the credentials regardless? Is there any scenario where it could write to the NAS without credentials?

If you run an interactive backup with an existing read/write connection open, Reflect should be able to write to the NAS. In fact that may be worth testing just as a data point. Try mapping a drive to the share path you use in your Reflect job and then run the backup interactively. No need to modify the backup job specifically at the mapped drive letter. As long as the Reflect job and the mapped drive point to the same network path, you should be good to go.

I'll have to wait until tomorrow to see if the scheduled backup works. If I run it manually, I know it will work as usual. There must be something going on when I restart the computer.
The free version I had was v7 and now I'm on v8. Probably nothing to do with anything, I just can't understand why this is all of a sudden a problem when it was working as expected prior to upgrading.

Will report back tomorrow.

No, I meant map a network drive and then try running from the Backup Definition Files tab so it runs in your user context. If a manual invocation from Scheduled Backups works, then a typical scheduled backup would work too (unless maybe there was something about the specific time the job was running), so that wouldn’t be a useful data point.

That's the thing - manual invocation from Schedule Backups does work. Seems to only happen on the first (the only) backup of the day.
I mapped the share as a network drive and ran both Backup Definition File and Scheduled Backups manually. They worked.
I guess I'll just have to wait and see what happens tomorrow. I honestly can't think of anything that would prevent the user/pass from working.

Ok, time to back up. Your original post mentioned that manually running a backup from Scheduled Backups works. I figured, apparently incorrectly, that what WASN’T working in that case was interactive backups invoked from the Backup Definition Files tab. You didn’t correct me on that, but now you just said that the failure occurs with a regular execution of a scheduled backup. (Next time it would be worth being as clear about the failure circumstances as about the success circumstances.)

So does this first backup of the day always occur at a specific time, or does it run as soon as you start your system, or what?

I think I mistook what you said originally about it failing from the Backups Definition Tab. But yes, the ONLY time it fails is on a new scheduled backup (daily)
It will usually run when I turn on the system. It's scheduled for 9:00am but usually start it up later than that.
There have been absolutely NO changes to anything since upgrading. To the system, to the network, or to Macrium (other than upgrading)

Can you try moving the scheduled backup to a time when your PC will reliably be on?  It would be useful to isolate the variable of "first/only backup of the day" vs. "backup attempted as soon as the system powers on", in case something may be going on that causes network connectivity not to be ready somehow when Reflect attempts to run a backup as soon as the system starts.