Windows VISTA 64 bit with Service Pack 2 can't copy/update any snapshots using FDISR

Discussion in 'FirstDefense-ISR Forum' started by rardsky, May 29, 2009.

Thread Status:
Not open for further replies.
  1. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    Hi! anyone here who experienced using FDISR on vista 64bit with service pack 2 installed. Mine can't copy/update any snapshots after the install of SP2, the VSS always stops for some reason unknown to me. Im using the latest FDISR version. Hope somebody can help me in this problem. tnx!
     
  2. USAAlone

    USAAlone Registered Member

    Joined:
    Oct 11, 2006
    Posts:
    90

    Hi,

    Had that error when trying to create a snapshot running 64 bit Vista.


    Daniel
     
  3. Minimax2000

    Minimax2000 Registered Member

    Joined:
    Jun 11, 2006
    Posts:
    204
    Location:
    Switzerland
    Hi

    No problems using VSS on Vista x64 SP2. Problem must be related to your system configuration. Some third party product could interfere. Check your fd-isr logs for possible error messages.

    Regards
     
  4. Minimax2000

    Minimax2000 Registered Member

    Joined:
    Jun 11, 2006
    Posts:
    204
    Location:
    Switzerland
    Check also the event viewer. It might reveal something you can hang on.
     
  5. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    Hi!

    The logs doesn't really say anything except for the error that states that "The copy engine unexpectedly terminated". Im using NOD 32 ver. 3 for my antivirus.
    Im wondering what 3rd party conflict could be the reason.
     
  6. Minimax2000

    Minimax2000 Registered Member

    Joined:
    Jun 11, 2006
    Posts:
    204
    Location:
    Switzerland
  7. Minimax2000

    Minimax2000 Registered Member

    Joined:
    Jun 11, 2006
    Posts:
    204
    Location:
    Switzerland
    Here are the relevant processes involved during a copy on my system. Good luck.
     

    Attached Files:

  8. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    Tnx! il give this one a try and will give you update on the running processes while updating a snapshot.
     
  9. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    i tried process monitor and it seems that everything works normally. Maybe its my system config who is messing up with FDISR. I hope leapfrog can find a way to fix this. That error is really strange everything works fine under SP1 but when i upgraded to SP2 FDISR doesn't work properly. BTW im using VISTA 64 bit Ultimate edition.
     
  10. Minimax2000

    Minimax2000 Registered Member

    Joined:
    Jun 11, 2006
    Posts:
    204
    Location:
    Switzerland
    My OS is Vista x64 Home Premium for the sake of completeness.
     
  11. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    Tnx very much for the big help il try to configure my PC
     
  12. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    Hi! are you still using FDISR on VISTA?
     
  13. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    17,047
    Hi Radsky

    You might try uninstalling NOD32 and see if that matters. Don't just disable, but do a complete uninstall and reboot twice.

    Pete
     
  14. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    I already did that...but still it doesn't work maybe its a bug of FDISR under SP2.
     
  15. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    17,047
    I've read other folks are having problems with other programs under Vista SP2 x64. It may not be FDISR
     
  16. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    yes maybe its the SP2 itself... I dont know if it's in my PC config or some 3rd party app.
     
  17. Minimax2000

    Minimax2000 Registered Member

    Joined:
    Jun 11, 2006
    Posts:
    204
    Location:
    Switzerland
    Got some more thoughts:

    1. call chkdsk /f/r to check for harddisk errors.



    2. call vssdmin.exe with these parameters from the console.
    vssadmin list providers >> c:\result.txt
    vssadmin list writers >> c:\result.txt
    vssadmin list shadows >> c:\result.txt

    Watch for errors particularly after vssadmin list writers in the txt file. Show us your output.
     
    Last edited: Jun 1, 2009
  18. Minimax2000

    Minimax2000 Registered Member

    Joined:
    Jun 11, 2006
    Posts:
    204
    Location:
    Switzerland
    3. Make sure DCOM Server Process Launcher Service is running

    http://itsvista.com/2007/04/dcom-server-process-launcher/



    4. Run the System File Checker

    1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.

    2. Click Continue or supply Administrator credentials if prompted.

    3. In the Command Prompt window type the following, and press Enter:

    sfc /scannow

    This command tries to repair a corrupted OS.
     
  19. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    Hi how will I do this? Im sorry im not really an advance PC user
     
  20. benton4

    benton4 Registered Member

    Joined:
    Nov 29, 2004
    Posts:
    158
    Location:
    Oregon
    1. call chkdsk /f/r to check for harddisk errors.

    I believe this is how you do the above: do in this order(all left clicks unless mentioned)
    start menu> computer>right click on C drive>properties>tools tab>under error-checking click check now> make sure both boxes are checked> start>schedule disk check>exit out of everything and reboot your computer. It will do the dskchk on reboot and it does take while so don't do it when you want be on your computer.

    I have no idea how to do the second option you were given. I'm not an advanced user either but I have done the dskchk thing several times. :)
     
  21. Minimax2000

    Minimax2000 Registered Member

    Joined:
    Jun 11, 2006
    Posts:
    204
    Location:
    Switzerland
    Below is my output from a virtual machine. You should do the same. By using the ">>" shift signs you redirect the output from the screen to a file.
     

    Attached Files:

  22. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
     
  23. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    well the vssadmin writer states that it has no error and it is stable
    ummm.. what has gone wrong with my PC
     
  24. rardsky

    rardsky Registered Member

    Joined:
    May 27, 2009
    Posts:
    16
    I hope this is what you are looking for..I just figured it out

    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
    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

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {d4f9b405-1179-4aff-ad4e-764fd91ec5d1}
    State: [1] Stable
    Last error: No error

    Writer name: 'ASR Writer'
    Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Writer Instance Id: {3026f948-6f77-43ec-8793-009e2a5a1fdb}
    State: [1] Stable
    Last error: No error

    Writer name: 'MSSearch Service Writer'
    Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
    Writer Instance Id: {ea9bb067-5187-4905-aff4-52db78fc652f}
    State: [1] Stable
    Last error: No error

    Writer name: 'Registry Writer'
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {8fa57a52-6ae1-4565-82cd-ea2a27a74350}
    State: [1] Stable
    Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
    Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    Writer Instance Id: {c543b262-b155-4509-9b7a-0fbe839e669a}
    State: [1] Stable
    Last error: No error

    Writer name: 'COM+ REGDB Writer'
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {04f0a939-aa48-4230-b3d1-f37af303826e}
    State: [1] Stable
    Last error: No error

    Writer name: 'WMI Writer'
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {a63ead68-8915-4a72-89ab-bd6f69f3af3f}
    State: [1] Stable
    Last error: No error

    Writer name: 'BITS Writer'
    Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    Writer Instance Id: {4b807aab-209a-4540-9d9d-39c675cc0ca3}
    State: [1] Stable
    Last error: No error

    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

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {d4f9b405-1179-4aff-ad4e-764fd91ec5d1}
    State: [1] Stable
    Last error: No error

    Writer name: 'ASR Writer'
    Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Writer Instance Id: {3026f948-6f77-43ec-8793-009e2a5a1fdb}
    State: [1] Stable
    Last error: No error

    Writer name: 'MSSearch Service Writer'
    Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
    Writer Instance Id: {ea9bb067-5187-4905-aff4-52db78fc652f}
    State: [1] Stable
    Last error: No error

    Writer name: 'Registry Writer'
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {8fa57a52-6ae1-4565-82cd-ea2a27a74350}
    State: [1] Stable
    Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
    Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    Writer Instance Id: {c543b262-b155-4509-9b7a-0fbe839e669a}
    State: [1] Stable
    Last error: No error

    Writer name: 'COM+ REGDB Writer'
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {04f0a939-aa48-4230-b3d1-f37af303826e}
    State: [1] Stable
    Last error: No error

    Writer name: 'WMI Writer'
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {a63ead68-8915-4a72-89ab-bd6f69f3af3f}
    State: [1] Stable
    Last error: No error

    Writer name: 'BITS Writer'
    Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    Writer Instance Id: {4b807aab-209a-4540-9d9d-39c675cc0ca3}
    State: [1] Stable
    Last error: No error

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Contents of shadow copy set ID: {fcb56d36-c571-42ba-9996-4eda5e3933ea}
    Contained 1 shadow copies at creation time: 5/31/2009 8:15:20 AM
    Shadow Copy ID: {d915325b-f7bd-4e5c-a6da-9235b46103ac}
    Original Volume: (C:)\\?\Volume{8d770607-418d-11dd-b1e3-806e6f6e6963}\
    Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
    Originating Machine: Rards-PC
    Service Machine: Rards-PC
    Provider: 'Microsoft Software Shadow Copy provider 1.0'
    Type: ClientAccessibleWriters
    Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

    Contents of shadow copy set ID: {15ded994-e05a-4597-b548-1ec2f67110c6}
    Contained 1 shadow copies at creation time: 6/2/2009 7:59:30 AM
    Shadow Copy ID: {8fd6e3c6-c2f8-42b3-86cf-7f43342fe046}
    Original Volume: (C:)\\?\Volume{8d770607-418d-11dd-b1e3-806e6f6e6963}\
    Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
    Originating Machine: Rards-PC
    Service Machine: Rards-PC
    Provider: 'Microsoft Software Shadow Copy provider 1.0'
    Type: ClientAccessibleWriters
    Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

    Contents of shadow copy set ID: {2e80f54c-3784-489e-b352-6d3b6748fe62}
    Contained 1 shadow copies at creation time: 6/4/2009 11:07:03 PM
    Shadow Copy ID: {a1a5bf27-2e0b-480a-ad47-9b5bb603bad6}
    Original Volume: (C:)\\?\Volume{8d770607-418d-11dd-b1e3-806e6f6e6963}\
    Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
    Originating Machine: Rards-PC
    Service Machine: Rards-PC
    Provider: 'Microsoft Software Shadow Copy provider 1.0'
    Type: ClientAccessibleWriters
    Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

    Contents of shadow copy set ID: {fb72fab6-7537-4588-86ca-ae49fb501323}
    Contained 1 shadow copies at creation time: 6/5/2009 9:30:17 AM
    Shadow Copy ID: {5571185f-f532-4938-80c6-49edbba7e5ea}
    Original Volume: (C:)\\?\Volume{8d770607-418d-11dd-b1e3-806e6f6e6963}\
    Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
    Originating Machine: Rards-PC
    Service Machine: Rards-PC
    Provider: 'Microsoft Software Shadow Copy provider 1.0'
    Type: ClientAccessibleWriters
    Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

    Contents of shadow copy set ID: {a7b590ce-eac6-4f11-ac61-19b76fe54871}
    Contained 1 shadow copies at creation time: 5/26/2009 9:28:20 PM
    Shadow Copy ID: {5c7deb60-026c-4bcf-9127-e98c92fcb4ec}
    Original Volume: (F:)\\?\Volume{3460bddf-3888-11de-8377-001fc6012148}\
    Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7
    Originating Machine: Rards-PC
    Service Machine: Rards-PC
    Provider: 'Microsoft Software Shadow Copy provider 1.0'
    Type: ClientAccessible
    Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {91335613-854d-4c86-8fb0-abc5872fd72e}
    Contained 1 shadow copies at creation time: 5/4/2009 10:55:52 PM
    Shadow Copy ID: {cf20203b-a804-493f-9c57-82e7ffd86ea6}
    Original Volume: (G:)\\?\Volume{3460bdfb-3888-11de-8377-001fc6012148}\
    Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy12
    Originating Machine: Rards-PC
    Service Machine: Rards-PC
    Provider: 'Microsoft Software Shadow Copy provider 1.0'
    Type: DataVolumeRollback
    Attributes: Persistent, No auto release, No writers, Differential
     
  25. Minimax2000

    Minimax2000 Registered Member

    Joined:
    Jun 11, 2006
    Posts:
    204
    Location:
    Switzerland
    You seem to have a lot of system restore points according to the list of shadows. I suggest getting rid of them, by disabling System restore in Vista, and rebooting the system. Then do a "vssadmin list shadows" again to make sure all shadows are gone.

    I Have found a helpful article regarding VSS and restore point handling:

    http://www.computerperformance.co.u..._Investigate_Volume_Shadow_Copy_with_vssadmin

    On my OS, system restore is always turned off.

    Finally try a copy/update operation in FD-ISR.
     
Thread Status:
Not open for further replies.