none
VSS issue, event ID 22, 12289, 12293, error 0x8004230f Failed to retrieve volumes that are eligible for shadow copies

    Question

  • I have a new Dell R710 that I have 2008 Server R2 64-bit installed. It's role is file server. I first noticed there were VSS initialization issues in BackupExec and that the system state wasn't getting backed up.
     
    Then I would run "vssadmin list writers" from CMD and system writer would be timing out....
     
    Writer name: 'System Writer'
        Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
        Writer Instance Id: {18370018-3454-46cf-a352-db13b2536aa6}
        State: [7] Failed
        Last error: Timed out
     
    I would also get Event ID 12289 Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} - 0000000000000140,0x0053c020,00000000003BDFD0,0,00000000003BBFA0,4096,[0]).  hr = 0x80070057, The parameter is incorrect.
     
    I would also get Event ID 12293 Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::IsVolumeSupported() failed with 0x8000ffff [hr = 0x8000ffff, Catastrophic failure
     
    Also event ID 22 for volsnap The shadow copy storage volume specified for shadow copies on volume \\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} could not be added.
     
    Also I can't configure shadow copies due to error 0x8004230f "Failed to retrieve volumes that are eligible for shadow copies.

    PLEASE HELP!

    Friday, May 11, 2012 3:21 PM

All replies

  • 1. As the first action, please restart your server and see if the mentioned error messages and conditions occur again.

    2. Run chkdsk /f C: on the server, reboot the server and see if the mentioned error messages and conditions occur again.

    3. Do you have installed Service Pack 1 on the problematic server?

    4. Pleas run the vssadmin list writers command and post the output completely.

    5. Run diskpart, then run list volume and then report back the result.

    6. Run vssadmin list providers and report back the result.

    7. I also suggest you to modify the registry as follows:

    • Click Start, click Run, type regedit, and then click OK.
    • Locate and then click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VolSnap
    • On the Edit menu, point to New, and then click DWORD value.
    • Type MinDiffAreaFileSize, and then press ENTER.
    • On the Edit menu, click Modify.
      Type the size (for example 1200) that you want for the shadow copy storage area, and then click OK.

    8. Read the following technet article to troubleshoot your problem:

    http://blogs.technet.com/b/askcore/archive/2010/06/18/reasons-why-the-error-enumeration-of-the-files-failed-may-occur-during-system-state-backup.aspx

    Another resources for troubleshooting:

    http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/0be3d3b4-2561-4c4c-90ec-0f6ec939fd54

    http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/73bb349f-0acb-4360-8b74-c2b51d556de5

    http://networkadminkb.com/KB/a467/how-to-fix-windows-2008-r2-system-state-backup-fails.aspx

    Please feel free to let us know if you have any question or concern.


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Edited by R.Alikhani Saturday, May 12, 2012 2:53 PM
    Saturday, May 12, 2012 2:48 PM
  • Hi,

    Based on the research, the error message may be related to the Backup application that is running on the problematic server.

    Do you use any third party software application to make backup on the problematic server except Symantec BackupExec?

    The VSS event ID 12289 may occurs if the third party backup application is used. If possible, we would like to suggest that you use Windows Server Backup which is a built-in feature on Windows Server to take backups, this error may be caused by BackupExec.

    Reference:

    Windows Server Backup Step-by-Step Guide for Windows Server 2008

    http://technet.microsoft.com/en-us/library/cc770266.aspx

    About event ID 12289,I find an article for reference:

    http://technet.microsoft.com/en-us/library/ee264206(WS.10).aspx


    Jeff Ren TechNet Community Support beneficial to other community members reading the thread.


    Monday, May 14, 2012 5:28 AM
  • 0
    Vote As Helpful

    1. As the first action, please restart your server and see if the mentioned error messages and conditions occur again.

    I restarted and the system writer status will go back to "State: 1 no error". When I tried to use the Windows Server Backup program to backup the system state, I would get the same error. My Dell creates a 2 GB partition using FAT32 that contains bootsect.bak, bootmgr.ini, and a folder named "Boot". I converted that to NTFS. Rebooted, retried the system state and was successful. I use BackupExec 2010 R3. I reran the backup job and was success backing up the system state. Usually after rebooting the system writer would be fine. I would run the backup and the system writer would go back to to an errored state. Now after both system state backups the system writer shows it is still fine. Although when I right click on C: > Configure Shadow Copies, I still get the error 0x8004230f "Failed to retrieve volumes that are eligible for shadow copies".

    2. Run chkdsk /f C: on the server, reboot the server and see if the mentioned error messages and conditions occur again.

    I haven't ran that yet. But a read-only chkdsk reports a clean volume. I will try that on reboot tonight during the maintenance window.

    3. Do you have installed Service Pack 1 on the problematic server?

    Yes, Windows Server 2008 R2 Standard SP1 64-bit. There are no additional patches available for install via M$ Update.

    4. Please run the vssadmin list writers command and post the output completely.

    C:\Windows\system32>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {9bfa176b-5465-4d84-9421-f4669ad4e6bd}
       State: [1] Stable
       Last error: No error

    Writer name: 'FSRM Writer'
       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
       Writer Instance Id: {b89d5b9d-b582-4d9b-9d09-2deb0a30d6b2}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {7aa989f6-d167-4ebe-aed8-8c7e7128cb1d}
       State: [1] Stable
       Last error: No error

    Writer name: 'MSSearch Service Writer'
       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
       Writer Instance Id: {30a0ac1f-9c49-49fa-a1b1-605e1a99c5c6}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {3d3e917e-617b-440b-964f-33cb67a70e80}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {5b3e696d-0153-445f-8755-e45947a5ec40}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {17992098-218e-48af-8761-93661457ac4a}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {c55c9077-14c4-4cae-bff0-e7bbcee8d256}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {1f913ea3-a68f-4d7f-8fee-3f4743c08752}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {431b08a1-4fe1-4810-8e82-8b03c032c28d}
       State: [1] Stable
       Last error: No error

    5. Run diskpart, then run list volume and then report back the result.

    C:\Windows\system32>diskpart

    Microsoft DiskPart version 6.1.7601
    Copyright (C) 1999-2008 Microsoft Corporation.
    On computer: FBPA1FS1

    DISKPART> list volume

      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0     D   TrueCrypt R  CDFS   DVD-ROM     3372 KB  Healthy
      Volume 1     E                                 CD-ROM          0 B  No Media
      Volume 2     S   OS               NTFS   Partition   2048 MB  Healthy    System
      Volume 3     C   Local Disk     NTFS   Partition    276 GB  Healthy    Boot
      Volume 4     F                       RAW    Partition    195 GB  Healthy
      Volume 5     G   ClearText      NTFS   Partition    530 GB  Healthy
      Volume 6     H                       RAW    Partition    390 GB  Healthy

    6. Run vssadmin list providers and report back the result.

    C:\Windows\system32>vssadmin list providers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
       Provider type: System
       Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7

    7. I also suggest you to modify the registry as follows:

    • Click Start, click Run, type regedit, and then clickOK.
    • Locate and then click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VolSnap
    • On the Edit menu, point to New, and then click DWORD value.
    • Type MinDiffAreaFileSize, and then press ENTER.
    • On the Edit menu, click Modify.
      Type the size (for example 1200) that you want for the shadow copy storage area, and then clickOK.

    Ken Johnston

    Monday, May 14, 2012 3:45 PM
  • Is your problematic server a virtual server? If you have installed the agent of the Symantec Backup Exec on this server, uninstall it, reboot the server and then see the result.


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, May 14, 2012 4:06 PM
  • It is not a virtual server.

    I have uninstalled the remote agent, rebooted, ccleaner, reinstalled, no difference.


    Ken Johnston

    Monday, May 14, 2012 5:11 PM
  • Please check the situation without installing the Backup Exec agent...

    Also please note that CCleaner is a tool that you mainly run it on Windows Clients-class of operating systems and so is not recommended to use it on your server...


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Edited by R.Alikhani Monday, May 14, 2012 5:23 PM
    Monday, May 14, 2012 5:21 PM
  • No go.

    I found this article, but it scares me a little. http://www.clickbay.de/win/volume-shadow-copy-error.htm


    Ken Johnston

    • Proposed as answer by Tiatan Tuesday, April 09, 2013 1:23 PM
    Tuesday, May 15, 2012 1:50 PM
  • I cannot confirm that the provided article can resolve your issue but remember that to backup registry (or at least export the registry key that you want to delete) first...


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, May 15, 2012 5:17 PM
  • Based on previous experience, this error may occur on the server that installed symantec backup software, the error may be caused by BackupExec, we would like to suggest that you use Windows Server Backup which is a built-in feature on Windows Server to take backups,  it is not compatible with windows server backup, I'm sorry to let you know this error may persist if you stick to use Symantec software on your server.

    Jeff Ren TechNet Community Support beneficial to other community members reading the thread.


    Wednesday, May 16, 2012 1:58 AM
  • Any updates for your issue?

    Jeff Ren TechNet Community Support beneficial to other community members reading the thread.

    Thursday, May 17, 2012 5:11 AM
  • No. Still unresolved.

    I have uninstalled BackupExec Remote Agent 2010, and I still can't configure Shadow Copies.


    Ken Johnston

    Thursday, May 17, 2012 2:28 PM
  • After confirming that the related agent for Symantec Backup Exec has not been installed on the problematic server, re-registering VSS related dlls may resolve your problem. To do so, copy the following code into a text file, save the text file with .bat extention and then run it. Then reboot the server and report back the result:

    @echo off
    REM
    REM Batch file that attempts to reset the
    REM Volume Shadow Copy (VSS) installation.
    REM
    echo This batch file must be run as an Administrator. If you are using Windows
    echo Vista then run it by right-clicking on the batch file and selecting
    echo "Run as administrator"
    
    %SYSTEMDRIVE%
    cd %SystemRoot%\System32
    echo.
    echo Ignore any messages saying a service is not started.
    echo.
    Net stop vss
    Net stop swprv
    regsvr32 ole32.dll
    regsvr32 oleaut32.dll
    regsvr32 vss_ps.dll
    Vssvc /Register
    regsvr32 /i swprv.dll
    
    echo eventcls.dll will fail to register on Windows Vista.
    regsvr32 /i eventcls.dll
    
    echo es.dll will fail to register on Windows Vista.
    regsvr32 es.dll
    
    regsvr32 stdprov.dll
    echo.
    echo vssui.dll only exists on Windows 2003. Ignore the error if not using Windows 2003.
    regsvr32 vssui.dll
    
    regsvr32 msxml.dll
    regsvr32 msxml3.dll
    echo.
    
    echo msxml4.dll may not be installed and is optional. Ignore the error.
    regsvr32 msxml4.dll
    echo.
    echo DONE!
    echo.
    echo IMPORTANT: Reboot your computer. After the reboot, open a command prompt
    echo and run the following:
    echo.
    echo vssadmin list writers
    echo.
    echo Ensure that all your writers are displayed without errors.
    echo.
    echo vssadmin list providers
    echo.
    echo Ensure that all your providers are displayed without errors.
    pause
     Please feel free to let us know if you have any question or concern.



    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, May 17, 2012 2:54 PM
  • This is the output of the bat file....
    ------------------
    This batch file must be run as an Administrator. If you are using Windows
    Vista then run it by right-clicking on the batch file and selecting
    "Run as administrator"

    Ignore any messages saying a service is not started.

    The Volume Shadow Copy service is not started.

    More help is available by typing NET HELPMSG 3521.

    The Microsoft Software Shadow Copy Provider service is not started.

    More help is available by typing NET HELPMSG 3521.

    eventcls.dll will fail to register on Windows Vista.
    es.dll will fail to register on Windows Vista.

    vssui.dll only exists on Windows 2003. Ignore the error if not using Windows 200
    3.

    msxml4.dll may not be installed and is optional. Ignore the error.

    DONE!

    IMPORTANT: Reboot your computer. After the reboot, open a command prompt
    and run the following:

    vssadmin list writers

    Ensure that all your writers are displayed without errors.

    vssadmin list providers

    Ensure that all your providers are displayed without errors.
    Press any key to continue . . .

    I rebooted. Still getting the error. in Application Events I get an error ID 12293, Source is VSS

    Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::QueryVolumesSupportedForSnapshots(ProviderId,29,...) [hr = 0x8000ffff, Catastrophic failure


    Ken Johnston

    Friday, May 18, 2012 2:58 AM
  • The mentioned error event may be logged because Volume Shadow Copy Service (VSS) is not started on the target machine. To test this situation do the following steps:

    1. Verify Volume Shadow Copy service is started on the target machine.

    • Go to, Windows Services console (Start > Run > type Services.msc)
    • Check for Volume Shadow Copy status.

    The status of this service should be in Manual. If so, please start it manually and check the Event Viewer for related Warning or Error messages.

    Please also copy the entire error event (open the error event in Event Viewer and click on the Copy button) and paste it here.


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    • Edited by R.Alikhani Friday, May 18, 2012 6:15 AM
    Friday, May 18, 2012 4:15 AM
  • Another piece of information that may prove helpful is to know which volume corresponds to the original DeviceIoControl error 0x80070057 being reported for '\\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963}'.

    Also, can you please detail how and what are you configuring shadow copies when you experience the other orginal error 0x8004230f.

    When able, please run and report the output for the below commands.  Apologies for asking you to gather and provide more information.

    C:\>MOUNTVOL
    C:\>VSSADMIN LIST VOLUMES
    C:\>VSSADMIN LIST SHADOWSTORAGE
    C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\VSS" /s
    C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore" /s
    C:\>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP" /s
    C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\MountMgr" /s

    Friday, May 18, 2012 6:22 PM
  • C:\>MOUNTVOL

     \\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963}\
         S:\

     \\?\Volume{a558e95d-6ede-11e1-9afc-001018bdcabe}\
         F:\

     \\?\Volume{caaccaeb-2a96-11e1-b14b-806e6f6e6963}\
         C:\

     \\?\Volume{642ddc1e-2c75-11e1-bef4-001018bdcabe}\
         G:\

     \\?\Volume{cd6539db-6f99-11e1-bdfc-001018bdcabe}\
         H:\

     \\?\Volume{854163ce-6dd8-11e1-be24-001018bdcabe}\
         K:\

     \\?\Volume{cd6539ee-6f99-11e1-bdfc-001018bdcabe}\
         T:\

     \\?\Volume{caaccaee-2a96-11e1-b14b-806e6f6e6963}\
         D:\

     \\?\Volume{caaccaf0-2a96-11e1-b14b-806e6f6e6963}\
         E:\


    C:\>VSSADMIN LIST VOLUMES

    C:\Windows\system32>VSSADMIN LIST VOLUMES
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Error: The shadow copy provider had an unexpected error while trying to process
    the specified command.


    C:\>VSSADMIN LIST SHADOWSTORAGE

    C:\Windows\system32>VSSADMIN LIST shadowstorage
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Error: The shadow copy provider had an unexpected error while trying to process
    the specified command.


    C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\VSS" /s

    This is too big to post on this site.

    ================================================================
    C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore" /s

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\DllPaths

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBack
    up
        WER    REG_MULTI_SZ    %ProgramData%\Microsoft\Windows\WER\* /s
        Kernel Dumps    REG_MULTI_SZ    %systemroot%\Minidump\* /s\0%systemroot%\mem
    ory.dmp
        Power Management    REG_MULTI_SZ    \hiberfil.sys
        MS Distributed Transaction Coordinator    REG_MULTI_SZ    C:\Windows\system3
    2\MSDtc\MSDTC.LOG\0C:\Windows\system32\MSDtc\trace\dtctrace.log
        WUA    REG_MULTI_SZ    %windir%\softwaredistribution\*.* /s
        Netlogon    REG_MULTI_SZ    %SystemRoot%\netlogon.chg
        Mount Manager    REG_MULTI_SZ    \System Volume Information\MountPointManage
    rRemoteDatabase
        Memory Page File    REG_MULTI_SZ    \Pagefile.sys
        Temporary Files    REG_MULTI_SZ    %TEMP%\* /s
        ETW    REG_MULTI_SZ    %SystemRoot%\system32\LogFiles\WMI\RtBackup\*.*
        RAC    REG_MULTI_SZ    %ProgramData%\Microsoft\RAC\*\0%ProgramData%\Microsof
    t\RAC\StateData\*\0%ProgramData%\Microsoft\RAC\Outbound\*\0%ProgramData%\Microso
    ft\RAC\PublishedData\*\0%ProgramData%\Microsoft\RAC\Temp\*
        VSS Default Provider    REG_MULTI_SZ    \System Volume Information\*{3808876
    B-C176-4e48-B7AE-04046E6CC752} /s
        VSS Service DB    REG_MULTI_SZ    \System Volume Information\*.{7cc467ef-686
    5-4831-853f-2a4817fd1bca}DB
        VSS Service Alternate DB    REG_MULTI_SZ    \System Volume Information\*.{7c
    c467ef-6865-4831-853f-2a4817fd1bca}ALT
        Internet Explorer    REG_MULTI_SZ    %UserProfile%\index.dat /s
        BITS_metadata    REG_MULTI_SZ    C:\ProgramData\Microsoft\Network\Downloader
    \*
        BITS_LOG    REG_MULTI_SZ    C:\Windows\System32\Bits.log
        BITS_BAK    REG_MULTI_SZ    C:\Windows\System32\Bits.bak
        DFSR Database    REG_MULTI_SZ    \System Volume Information\DFSR\* /s

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnap
    shot
        WUA    REG_MULTI_SZ    %windir%\softwaredistribution\*.* /s
        RAC    REG_MULTI_SZ    %ProgramData%\Microsoft\RAC\*\0%ProgramData%\Microsof
    t\RAC\StateData\*\0%ProgramData%\Microsoft\RAC\Outbound\*\0%ProgramData%\Microso
    ft\RAC\PublishedData\*\0%ProgramData%\Microsoft\RAC\Temp\*
        OutlookOST    REG_MULTI_SZ    $UserProfile$\AppData\Local\Microsoft\Outlook\
    *.ost

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToResto
    re
        MS Distributed Transaction Coordinator    REG_MULTI_SZ    CurrentControlSet\
    Control\MSDTC\ASR\
        Mount Manager    REG_MULTI_SZ    MountedDevices\
        Pending Rename Operations    REG_MULTI_SZ    CurrentControlSet\Control\Sessi
    on Manager\PendingFileRenameOperations
        Pending Rename Operations2    REG_MULTI_SZ    CurrentControlSet\Control\Sess
    ion Manager\PendingFileRenameOperations2
        Session Manager    REG_MULTI_SZ    CurrentControlSet\Control\Session Manager
    \AllowProtectedRenames


    ================================================

    C:\>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP" /s

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP
        LastIndex    REG_DWORD    0x3
        CreateTimeout    REG_DWORD    0x1200000

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP\Clients
        {1D6B8E63-E68B-4DA2-900F-6017B4B6E1A0}    REG_MULTI_SZ    \\?\Volume{caaccae
    a-2a96-11e1-b14b-806e6f6e6963}\:OS (S%3A)\0\\?\Volume{caaccaeb-2a96-11e1-b14b-80
    6e6f6e6963}\:Local Disk (C%3A)

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP\Leases

    =================================================
    C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\MountMgr" /s

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MountMgr
    DisplayName REG_SZ @%SystemRoot%\system32\drivers\mountmgr.sys,-100
    Group REG_SZ System Bus Extender
    ImagePath REG_EXPAND_SZ System32\drivers\mountmgr.sys
    Description REG_SZ @%SystemRoot%\system32\drivers\mountmgr.sys,-101
    ErrorControl REG_DWORD 0x3
    Start REG_DWORD 0x0
    Type REG_DWORD 0x1

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MountMgr\Enum
    0 REG_SZ Root\LEGACY_MOUNTMGR\0000
    Count REG_DWORD 0x1
    NextInstance REG_DWORD 0x1


    Ken Johnston

    Monday, May 21, 2012 2:48 PM
  •  Error: The shadow copy provider had an unexpected error while trying to process the specified command.

    Please check the status of the Microsoft Software Shadow Copy Provider service. The status of this service should be in Manual. If so, please start it manually and check the Event Viewer for related Warning or Error messages.


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    • Edited by R.Alikhani Monday, May 21, 2012 3:34 PM
    Monday, May 21, 2012 3:32 PM
  • Thank you for providing the information.  Ok, your S: volume maps to '\\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963}'.   As an observation, your D: volume has the label "TrueCrypt".  If TrueCrypt is enabled, there are known interoperability issues with VSS and TrueCrypt.  So it would be prudent for you to manually diagnose the current VSS issue by dismounting possible TrueCrypt volumes (k:,t:) and\or using the "Mount Options" "Mount volume as removeable medium\media" and determine if VSS becomes operational.  If not, let me know and I will continue to review the provided information.


    • Edited by marcusolinii Monday, May 21, 2012 10:00 PM less intrusive diagnostic
    Monday, May 21, 2012 8:31 PM
  • Do you have any URLs I can review for the known operational issues with TrueCrypt and VSS?

    The service has been set to Manual this whole time and I can manually start it if I choose. Any related events have already been posted.


    Ken Johnston

    Wednesday, May 23, 2012 4:19 PM
  • Sure.  Please review the limitations section of the TrueCrypt documentation (search for “shadow”): http://www.truecrypt.org/docs/issues-and-limitations.

    By the way, I performed some diagnostics with TrueCrypt and I was able to reproduce the issues that you are experiencing.

    From further review of your provided information, it appears that the cause of the Backup Exec System State backup failures is because your System volume is encrypted with TrueCrypt.  The System State ASR VSS Component resides on the System volume and since VSS snapshots cannot be performed for TrueCrypt encrypted volumes a backup failure will result.  Please review the ASR VSS Metadata in the Backup Exec logs directory to confirm: “c:\program files\symantec\backup exec\logs\{BE000CBE-11FE-4426-9C58-531AA6355FC4} - ASR Writer.xml”.

    To resolve the Backup Exec System State backup failures, the System volume must be un-encrypted with TrueCrypt.  I know this is a difficult action but it is essential.

    Also, in order to resolve the other VSS operational issues, all of the TrueCrypt encrypted volumes and encrypted volume file containers must be mounted as removable media.  However and unfortunately, a VSS snapshot will still not be successful for any TrueCrypt encrypted volumes and encrypted volume file containers.

    Hope this proves accurate and helpful.

    Wednesday, May 23, 2012 10:21 PM
  • Have anyone found a solution? Got the same issue :(
    • Edited by Tiatan Tuesday, April 09, 2013 1:21 PM
    Tuesday, April 09, 2013 1:21 PM
  • same issue.. i have tried everything mentioned (twice) but no luck...

    Thursday, July 11, 2013 11:24 PM
  • I'm having the same or a very similar issue. But one Thing I know is, that I changed to System drive just bevor this happend for the first time. On this Server I just had the System drive running on a Raid 1. I changed to a raid 5 on a new Controller. But haven't done a new Installation, just a Partition copy. I guess that the proble is related to the "now missing old hard drive". But if I'm right I have no idea how to get rid of it. Must be somewhere whithin the registry but where?
    Thursday, August 15, 2013 12:16 PM
  • Solved 12289 VSS deviceIO errors..  There was a unknown volume  in device manager along with the generic volume, inside "storage volumes"  with show hidden items selected.   Found that volume.inf and volume.pnf missing from windows\inf ...   How they were deleted or how the C: still worked  idk..   Identified problem by experiencing weirdness  with disk manager console, creating new disk..     copy the files from another 2008 server x86.  Back in business!

    Log Name:      Application
    Source:        VSS
    Date:          8/14/2013 3:54:03 PM
    Event ID:      12289
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      VSSBROKEN.com
    Description:
    Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{819d9c01-746e-11df-8283-806e6f6e6963} - 00000198,0x0053c008,0002C820,0,0002D828,4096,[0]).  hr = 0x80070079. 

    Operation:
       Processing EndPrepareSnapshots

    Context:
       Execution Context: System Provider
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="VSS" />
        <EventID Qualifiers="0">12289</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-08-14T20:54:03.000Z" />
        <EventRecordID>91544</EventRecordID>
        <Channel>Application</Channel>
        <Computer>VSSBROKEN.COM</Computer>
        <Security />
      </System>
      <EventData>
        <Data>DeviceIoControl(\\?\Volume{819d9c01-746e-11df-8283-806e6f6e6963} - 00000198,0x0053c008,0002C820,0,0002D828,4096,[0])</Data>
        <Data>0x80070079</Data>
        <Data>

    Operation:
       Processing EndPrepareSnapshots

    Context:
       Execution Context: System Provider</Data>
         



    • Edited by Chris th Saturday, August 17, 2013 1:30 PM
    Saturday, August 17, 2013 1:28 PM