Ghost Solution Suite

 View Only
  • 1.  Error -99, Status code: 106

    Posted Feb 22, 2018 04:20 PM

    I'm trying to create an image of a full disk. It appears to be going fine but failed right at the end with the following:

    Task:        Created disk image

            Completed:    2/22/2018 4:09:23 PM

            Module:        User Defined

            Level:        Error

            Status:        Error -99 during imaging process

            Result:        Failed (Status code: 106)

     

    Windows 10 laptop being Image from a task a server running 3.2.

    Can't seen to find these error numbers anywhere in the docs.

    Any suggestions?

    Thanks!



  • 2.  RE: Error -99, Status code: 106

    Posted Feb 23, 2018 01:24 AM

    It might actually be in your interests to log a call with Symantec support over this as that error doesn't appear to be anywhere. Unless it's hardware-related on the source or target.

    Thanks!



  • 3.  RE: Error -99, Status code: 106

    Posted Feb 26, 2018 11:24 AM

    Ah yes, Error -99.  We've seen that error in a few different situations.  I would recommend opening a ticket with Symantec, because all environments are different and the resolution that worked for me, might not work for you.  One resolution was to change the IP address of the LMHOSTS in step 6 of 8 (Network Drive Mappings) in the pre-boot environment configuration to the IP address of the Ghost server.  

    Have you tried capturing the image to an external hard drive using a USB Ghost Boot Disk?

    Maybe try adding the -split=0 switch to the image capturing process?

    Have you tried adding any of the below switches to the image capture process?

    -notrim -ntexact -ntc- -ntil -ntic -ib

    Here is a link explaining swiches in Ghost: https://support.symantec.com/en_US/article.TECH130961.html



  • 4.  RE: Error -99, Status code: 106

    Trusted Advisor
    Posted Feb 27, 2018 11:44 AM

    The first thing to check here is that your drive mappings have been made successfully. This can be due to,

    1. Account lockout for the username used to map the drives
    2. Bad username/password used to map the drives
    3. Network drive mapping conflicting with local drives
    4. Security permission issues on the server mapped drive

    Kind Regards,

    Ian./

     



  • 5.  RE: Error -99, Status code: 106

    Posted Feb 27, 2018 04:15 PM


  • 6.  RE: Error -99, Status code: 106

    Trusted Advisor
    Posted Mar 06, 2018 05:11 AM

    @ITGirl -that Symantec Support article was relevant to early releases of GSS 3.0 only. As the poster is talking about GSS3.2, this isn't the issue.

    @mseery -Is this issue outstanding, or should I mark this as resolved now?