Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 6.0

...


Problem cases & solutions

  1. Disks with a non standard sector size
    If you see the following in the extended VSS information:
     

    Code Block
    languagetext
    ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed.

    
    - Returned HRESULT = 0x80042301

    
    - Error text: VSS_E_BAD_STATE


    You may have a disk with a non-standard sector size attached to your system, see here for a solution:

    http://kb.macrium.com/KnowledgebaseArticle50115.aspx

    VSS fails due to disks with a non-standard sector size

  2. Other VSS applications have modified VSS
    If you have used other backup (or any VSS aware) software in the past it may have altered VSS. To fix this issue see here:
    http://kb.macrium.com/KnowledgebaseArticle50031.aspxVSS fails due to modification by 3rd party software
  3. VSS failing on Windows Server 2008 R2 also producing Windows Event ID 12293
    This article describes a fix for a specific issue that can occur on Windows Server 2008 R2:
    http://kb.macrium.com/KnowledgebaseArticle50068.aspxVSS errors occur and Windows Event 12293 is also present on Windows Server 2008 R2 without BitLocker


Identifying VSS error information

You have 3 pieces of information to help diagnose the issue:

...

Retrieving this information varies between Version 4 & 5. The differences are displayed below.

Version 5/6

The extended VSS error information will be reported as below for version 5. Note the result code may be different.



...