I can't take much more of this.
My original issue was writing directly to my NAS (https://forum.macrium.com/57855/Invalid-The-user-name-or-password-is-incorrect)

Even after jumping into a remote session with Macrium Support, we were unable to resolve the issue - it seemed like we fixed it by creating a separate user on the NAS but then the issue came back the next day.

I gave up on trying to make that work and started writing backups to my one of my local drives.
Then I started receiving the error 'Backup aborted! - Failed To Create Volume Snapshot. Failed - 0x80042316 - IDispatch error #8470'

Everything I've read points to the backup conflicting with some other software or Windows updates using VSS.
Windows updates are not pending and I do not use any other disk imaging software, so I don't know what else could be using VSS.
I've ran the vssadmin list writers command and it all looks standard according to posts on the matter.

The failures seem random, sometimes I can go a few days without issue but eventually the error will return.
I've tried looking through logs for any additional information but I'm not seeing anything.

If I can't get this figured out I will have to insist on a refund. As stated in my previous post, everything was working fine while I was using the free version. The issues only started happening once I upgraded to the paid edition. That's it. No system changes anywhere. Why this is the case, I have no idea.

I forget if you tried this on your original issue.  Did you try the Fix VSS Problems under Other Tasks?  Since it seems to be somewhat random, this may fix the issue, but only temporarily.

+x

 

dbminter - 20 April 2022 5:02 PM

I forget if you tried this on your original issue.  Did you try the Fix VSS Problems under Other Tasks?  Since it seems to be somewhat random, this may fix the issue, but only temporarily.

I did. I've tried multiple times and it hasn't seemed to do much (It does run the fix but the error still comes back)

Well I'd be running 
SFC /scannnow
DISM /Online /Cleanup-Image /RestoreHealth
and
CHKDSK /scan /r (source dive)
Just to eliminate anything being hinkey with the backup source or Windows, but I do understand how it's frustrating.

You may well run into similar issues with any other backup software or going back to free if it's an unrelated cause, they all use VSS.

+x

 

Beardy - 20 April 2022 5:58 PM

Well I'd be running 
SFC /scannnow
DISM /Online /Cleanup-Image /RestoreHealth
and
CHKDSK /scan /r (source dive)
Just to eliminate anything being hinkey with the backup source or Windows, but I do understand how it's frustrating.

You may well run into similar issues with any other backup software or going back to free if it's an unrelated cause, they all use VSS.

Already ran through all of those commands. Also didn't resolve the error messages. No issues found through the scans either.

Have you tried taking images in the Rescue Media and see if they succeed?  If they do, I'd take a recent image of your Windows/partitions necessary to start the PC, and attempt to regress Reflect back to the free version.  See if the problem resolves itself.  If it does, reverse the steps again and install the paid version.  If the problem returns, you know there's something in your paid setup that is problematic.  You could try uninstalling and reinstalling the software, if you haven't already.

Well if you're sure you have nothing creating the shadow that's clearly in progress to give the error, you could try running your backup from a script & restart the volume shadow service before it runs.. total hackery.. but it might break whatever other software is using VSS & then you'll know the culprit.

It could also be some software (or windows) not cleaning up properly after an older snapshot.

Hopefully as simple as having reflect generate a batch or powershell script & doing "net stop vss", followed by "net start vss" at the beginning.
With luck that'll cause Windows to clean up whatever that snapshot is from.
Schedule the script instead of the xml & observe what if anything breaks..

+x

 

Beardy - 20 April 2022 9:27 PM

Well if you're sure you have nothing creating the shadow that's clearly in progress to give the error, you could try running your backup from a script & restart the volume shadow service before it runs.. total hackery.. but it might break whatever other software is using VSS & then you'll know the culprit.

It could also be some software (or windows) not cleaning up properly after an older snapshot.

Hopefully as simple as having reflect generate a batch or powershell script & doing "net stop vss", followed by "net start vss" at the beginning.
With luck that'll cause Windows to clean up whatever that snapshot is from.
Schedule the script instead of the xml & observe what if anything breaks..

That was one workaround I was thinking of trying. Could you help point me to where I would enter those commands for Macrium to run them?
Do I need to make a file and run it from here? Or can I just enter 'net stop vss' and 'net start vss' into the parameter fields?

I'm on v7 so the interface is slightly different, & that wizard (powershell?) appears to offer adding one command before where we need two.

If you use the batch file option you can click the edit button for the generated file then (batch files tab) then simply put:

net stop vss
net start vss

directly below where it says at the beginning (make space).

+x

 

Beardy - 20 April 2022 10:03 PM

I'm on v7 so the interface is slightly different, & that wizard (powershell?) appears to offer adding one command before where we need two.

If you use the batch file option you can click the edit button for the generated file then (batch files tab) then simply put:

net stop vss
net start vss

directly below where it says

@echo off

at the beginning (make space).

Can I leave everything else in the batch file as is?
Just enter the commands directly below