Deployment Solution

 View Only

  • 1.  Ghost32 11.5 - Cannot open spanned file - Error 10006 when trying to capture image

    Posted Oct 19, 2012 01:25 PM

     

    I'm trying to capture my Windows 7 x64 image using Ghost since Rdeploy in the future won't be supported. At 99% the process erorrs out with Application Error 10006.
     
    I've searched that the error code is "Cannot open spanned file" - Your image file consists of a set of two or more separate files. Check the file name and path for the second and subsequent files.
     
    How do I resolve this?


  • 2.  RE: Ghost32 11.5 - Cannot open spanned file - Error 10006 when trying to capture image

    Posted Oct 19, 2012 01:28 PM

    Do I need to set an additional parameter? This is what I have currently.

    -clone,MODE=create,SRC=1,DST=%IMAGE_FILENAME% -sure



  • 3.  RE: Ghost32 11.5 - Cannot open spanned file - Error 10006 when trying to capture image

    Posted Oct 19, 2012 02:42 PM

    After more searching, I believe the reason why it is splitting up even though I am booting into WinPE is because I am mapping a network drive and Ghost is unable to determine the file system on mapped drives and splits them up at 2GB. With that said, I still don't know why I am getting this error.



  • 4.  RE: Ghost32 11.5 - Cannot open spanned file - Error 10006 when trying to capture image

    Posted Oct 22, 2012 01:33 PM

    anybody?



  • 5.  RE: Ghost32 11.5 - Cannot open spanned file - Error 10006 when trying to capture image

    Posted Oct 22, 2012 04:50 PM

    Is there a ghosterr file you can post?



  • 6.  RE: Ghost32 11.5 - Cannot open spanned file - Error 10006 when trying to capture image

    Posted Oct 22, 2012 05:18 PM

    I do have a ghosterr file, but it is unrelated to the error that I get. It's an error when I tried to use -split=0 as a parameter.



  • 7.  RE: Ghost32 11.5 - Cannot open spanned file - Error 10006 when trying to capture image
    Best Answer

    Posted Oct 22, 2012 06:40 PM

    Nevermind I figured out why. The naming of my image file was causing the issue. I had a dash (-) in the naming and it gave this error for some reason.