VSS Error: 0x80042316 IDispatch error #8470


Author
Message
glanc
glanc
New Member
New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)
Group: Forum Members
Posts: 4, Visits: 11
Hello,

in Site Manager 7.2.39.71 that was working with no problems imaging several vm server and phisical workstations, now they all fails with these errors:
----
A VSS error was encountered creating the snapshot - Error: 0x80042316
The backup failed to complete successfully - Reason: Backup aborted! - Failed To Create Volume Snapshot. Failed - 0x80042316 - IDispatch error #8470
----

Tried several sultions: VSSFIX.exe from Macrium, manual script to re-register vss components, vssadmin list writers are all OK and so on. vss services are up and running on all clients. Also added the registry fix to increase the vss timeout byt still fails. Don't know what to do now! Thanks.
Chris
Chris
Macrium Representative
Macrium Representative (231 reputation)Macrium Representative (231 reputation)Macrium Representative (231 reputation)Macrium Representative (231 reputation)Macrium Representative (231 reputation)Macrium Representative (231 reputation)Macrium Representative (231 reputation)Macrium Representative (231 reputation)Macrium Representative (231 reputation)Macrium Representative (231 reputation)
Group: Moderators
Posts: 155, Visits: 3.2K
glanc - 21 January 2019 5:22 PM
Hello,

in Site Manager 7.2.39.71 that was working with no problems imaging several vm server and phisical workstations, now they all fails with these errors:
----
A VSS error was encountered creating the snapshot - Error: 0x80042316
The backup failed to complete successfully - Reason: Backup aborted! - Failed To Create Volume Snapshot. Failed - 0x80042316 - IDispatch error #8470
----

Tried several sultions: VSSFIX.exe from Macrium, manual script to re-register vss components, vssadmin list writers are all OK and so on. vss services are up and running on all clients. Also added the registry fix to increase the vss timeout byt still fails. Don't know what to do now! Thanks.

HI @glanc

Thanks for posting and sorry you are having issues with the backup process in Site Manager. We are aware of the issue and are currently working on a fix for release. This should be available shortly but cannot confirm ETA at this time.

Kind regards​​​​​

--
Chris Bamford
Macrium Reflect Development & Support
KnowledgeBase: http://knowledgebase.macrium.com/
YouTube Videos: https://www.youtube.com/user/Macrium

Next Webinar


glanc
glanc
New Member
New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)
Group: Forum Members
Posts: 4, Visits: 11
Hello,

deleting the registry entry "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{533c5b84-ec70-11d2-9505-00c04f79deaf}\UpperFilters" from all the affected PC fixed the issue. Thanks.

It is recommended the registry entry above is *not* deleted. This may cause VSS to be non functioning on most systems.


Edited 13 November 2019 1:05 PM by Nick
glanc
glanc
New Member
New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)
Group: Forum Members
Posts: 4, Visits: 11
Now I've another issue with a Windows Server 2003 Standard tha is failing with this error:

itializing
Validating location:    \\192.168.0.251\macrium\GESTSRV\{FCCABD73-8267-4BAD-ACF6-ACE8535BDEE5}\ - Invalid (Accesso negato.)
    Backup aborted! - None of the specified backup locations could be written to

I've attached the LastBackupXML.log

Alex
Alex
Macrium Representative
Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)
Group: Moderators
Posts: 139, Visits: 602
glanc - 22 January 2019 5:02 PM
Now I've another issue with a Windows Server 2003 Standard tha is failing with this error:

itializing
Validating location:    \\192.168.0.251\macrium\GESTSRV\{FCCABD73-8267-4BAD-ACF6-ACE8535BDEE5}\ - Invalid (Accesso negato.)
    Backup aborted! - None of the specified backup locations could be written to

I've attached the LastBackupXML.log

Hi,
Unfortunately it looks like you've encountered a second issue that was being hidden by the VSS issue. The latest version of the Site Manager agent creates a log called AgentNetwork.log which contains detailed information on the error accessing the share.

Unfortunately I can't read the attached LastBackupXml.log, so I can't see what sort of credentials you have set on your share, but in some situations this error can be caused by either missing the domain from the repository credentials or using the older style DOMAIN naming rather than the newer style DNS domain.local naming.

If you continue to have issues, our support team should be able to help if you open a support case!

Regards,
Alex Stevenson
Macrium Software


Kind regards,
Alex,
Macrium Development.

glanc
glanc
New Member
New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)
Group: Forum Members
Posts: 4, Visits: 11
Alex - 28 January 2019 9:48 AM
glanc - 22 January 2019 5:02 PM
Now I've another issue with a Windows Server 2003 Standard tha is failing with this error:

itializing
Validating location:    \\192.168.0.251\macrium\GESTSRV\{FCCABD73-8267-4BAD-ACF6-ACE8535BDEE5}\ - Invalid (Accesso negato.)
    Backup aborted! - None of the specified backup locations could be written to

I've attached the LastBackupXML.log

Hi,
Unfortunately it looks like you've encountered a second issue that was being hidden by the VSS issue. The latest version of the Site Manager agent creates a log called AgentNetwork.log which contains detailed information on the error accessing the share.

Unfortunately I can't read the attached LastBackupXml.log, so I can't see what sort of credentials you have set on your share, but in some situations this error can be caused by either missing the domain from the repository credentials or using the older style DOMAIN naming rather than the newer style DNS domain.local naming.

If you continue to have issues, our support team should be able to help if you open a support case!

Regards,
Alex Stevenson
Macrium Software

Hello,
filling the DOMAIN field with the hostname of the QNAP solved the problem.
Alex
Alex
Macrium Representative
Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)Macrium Representative (269 reputation)
Group: Moderators
Posts: 139, Visits: 602
glanc - 28 January 2019 9:55 AM
Alex - 28 January 2019 9:48 AM
glanc - 22 January 2019 5:02 PM
Now I've another issue with a Windows Server 2003 Standard tha is failing with this error:

itializing
Validating location:    \\192.168.0.251\macrium\GESTSRV\{FCCABD73-8267-4BAD-ACF6-ACE8535BDEE5}\ - Invalid (Accesso negato.)
    Backup aborted! - None of the specified backup locations could be written to

I've attached the LastBackupXML.log

Hi,
Unfortunately it looks like you've encountered a second issue that was being hidden by the VSS issue. The latest version of the Site Manager agent creates a log called AgentNetwork.log which contains detailed information on the error accessing the share.

Unfortunately I can't read the attached LastBackupXml.log, so I can't see what sort of credentials you have set on your share, but in some situations this error can be caused by either missing the domain from the repository credentials or using the older style DOMAIN naming rather than the newer style DNS domain.local naming.

If you continue to have issues, our support team should be able to help if you open a support case!

Regards,
Alex Stevenson
Macrium Software

Hello,
filling the DOMAIN field with the hostname of the QNAP solved the problem.

Hi,

That's good news. We're currently investigating what the root cause of these issues is and hope to have a fix soon, but it's good that you have a workaround and are up and running again.

Regards,
Alex Stevenson
Macrium Software


Kind regards,
Alex,
Macrium Development.

lodestar53
lodestar53
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 3, Visits: 4
I just encountered this error today. Rerunning the script worked.



I'm running the most recent version of Reflect but thought I'd post this in case it might help.

Nick
Nick
Macrium Representative
Macrium Representative (3.2K reputation)Macrium Representative (3.2K reputation)Macrium Representative (3.2K reputation)Macrium Representative (3.2K reputation)Macrium Representative (3.2K reputation)Macrium Representative (3.2K reputation)Macrium Representative (3.2K reputation)Macrium Representative (3.2K reputation)Macrium Representative (3.2K reputation)Macrium Representative (3.2K reputation)
Group: Administrators
Posts: 1.9K, Visits: 11K
lodestar53 - 11 November 2019 5:24 PM
I just encountered this error today. Rerunning the script worked.



I'm running the most recent version of Reflect but thought I'd post this in case it might help.

Thanks for posting.

This error is generally resolved with a reboot or by changing the time that the backup is run. Please see this KB article.

https://knowledgebase.macrium.com/display/KNOW72/VSS+error:+VSS_E_SNAPSHOT_SET_IN_PROGRESS

Kind Regards

Nick - Macrium Support

Next Webinar


lodestar53
lodestar53
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 3, Visits: 4
Nick - 12 November 2019 4:47 PM
lodestar53 - 11 November 2019 5:24 PM
I just encountered this error today. Rerunning the script worked.



I'm running the most recent version of Reflect but thought I'd post this in case it might help.

Thanks for posting.

This error is generally resolved with a reboot or by changing the time that the backup is run. Please see this KB article.

https://knowledgebase.macrium.com/display/KNOW72/VSS+error:+VSS_E_SNAPSHOT_SET_IN_PROGRESS

These scripts have been in use for months without any problems until yesterday. Today, or better, last night - the same error occurred and, again, when I ran the script manually it worked as expected. I've made no changes to this machine with regards to backup software - this was a sudden change in behavior. I ran "Fix VSS Problems" earlier today with the hope that my image script will run tonight without any problems.

I've rebooted several times to make sure nothing is sitting in memory - still puzzled by this sudden change.

If this continues tonight I'll modify the script to begin at a later time and post what I find.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search