KNOWN ISSUE: When deploying an image, the status column reports 'Error -99 during imaging process'

TECH39771
Last Updated June 16, 2016
Copy Article Title/URL
Feedback
Subscribe

The Deployment Solution console reports error -99 when restoring an image.

There are several different instances of this error message.

  • First, when deploying an image, the 'Status' column reports 'Error -99 during imaging process'
  • Second, while trying to deploy a disk image from a secondary share point.

Steps to reproduce:

  1. Add "net use G: \\DS_server\share1" to startup.bat in WinPE 2.1.
  2. Create a share called "share1".
  3. Put an image file to "share1" called image.img.
  4. Create a distribute image job > Image file= G:\image.img > enable Disable image Path validation > enable Automatically perform configuration . . . > Preboot automation WinPE 2.1.
  • Third, there is a known issue where the Ghost file extension changes from .GHO to .IMG and must be set back.
  • NOTE: This problem has also been reported when running a Create Disk Image task in GSS 3.

A new issue has been found in the GSS 3.1, MP1, and MP2 release of the product.

This issue also provides you with an "Error -99 during imaging process" message at the end of imaging.  This error message can occur on both the capture and the deploy of an image.  What you'll notice with this error is that when you drill down onto the status details of the job you'll see a status code of either 104 or 106.

For the first case, the problem is that the path to the Ghost image file has a space in it. This causes the error 19010 ' "All arguments must be proceeded with a - or a /" 

 

The cause of the second instance is unknown at this time. 

Reviewing the RDeploy log rd.log shows the following:

Error description:
     Error opening the DS configuration file.
     (Note: DS configuration file: .\Temp\c5000042.cfg)

Possible causes:
     A file that was expected to exist does not exist.
     Data has been corrupted (e.g. in an image or on the network).

     Could be a hardware problem.

 

Possible resolutions:
     Make sure the file exists and is accessible.
     If the missing file is part of this program, reinstall the program.
     Repeat the operation to see if the problem occurs in the same manner again.
     Simplify the network by removing routers, etc. that might corrupt data.
     If a file is being read, recreate the file.


==================== Technical details ====================

Logfile = created Tue Apr 08 12:50:01 2008
  Build = RdeployT.exe 6.9 (8853)
Cmdline = F:\RDeploy\Windows\RdeployT.exe -noprompt -md -fg:\HPD220.img -mcint:192.168.1.254 -dsconfig:.\Temp\c5000042.cfg

Status = 191 (0xbf)
Source file = apps\rdeploy\appcfg.cpp
Line number = 799 (0x31f)
Stack trace = 0x409f32 0x409b3b 0x4024eb 0x401c40 0x40dc9d &Known=0x433490
Note = DS configuration file: .\Temp\c5000042.cfg
Imaging library revision = 8853 (win32-x86-release build, Fri Feb 22 19:30:12 2008)

It appears that rdeploy.exe is looking for a .cfg file that it can't find. However, the path specified for the location of the .cfg file appears valid.

  • There is a known issue with the Distribute Disk image Task. The file extension changes from .GHO to .IMG when modifying the job.

More specifically, this error is simply saying that rdeploy or ghost could not be called or write to the specified drive and is likely due to mapping or permissions issues.

The cause for the newly found -99 message with a status code of 104 or 106 is still unknown at this time.

For the first cause, either remove the space in the path to the Ghost image file, or add quotations to the tokenized destination in the 'Additional Parameters' field:

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

 

For the second cause:

1. Check permissions of the eXpress share.

2. Try changing the mapping letter of the pre-boot to 'I' or something higher than 'F'

 

For the third cause: 

For the other cause, test another machine of the same hardware.

For the known issue with file extensions:  When you create a job with the Distribute Disk Image task, then select the GHO file to be deployed and save the task, everything will work properly. But, if you need to edit the task, to change a parameter (like the Sysprep field as an example), you will need to go back into the field where you specify the GHO file name and re-select it. Even if you do not touch that field, incorrectly, the Imaging Tool is being reset to RDeploy, but retains the Ghost image information. The result is that when the job is deployed to a client computer, the command line will be for RDeploy.exe, but with the GHO filename. This of course will error out, many times with an "-99" error.

Additionally when every thing else looks good upgrade to Ghost Solution Suite 3.1 MP1 as there was an issue addressed in this release that would resolve an issue where the image would be created but the job would report a failure.   See the release note for Ghost Solution Suite 3.1 MP1 DOC9206

Development is currently working towards a resolution to the status code of 104 or 106.  Please subscribe to this tech article and you will be notified, through email, when a fix has been made available.

There is a work around that will allow you to continue imaging while we work on the issue.  For imaging imaging task you need to add the 104 or 106 as a success exit code.  Here's how.

  1. After choosing a capture or deploy task you need to hit NEXT to get to the Return Codes section of the task.
  2. Click on Add
  3. For the Code: value put either 104 or 106
  4. For the Response: put Continue
  5. For the Result: section put Succes

This will still get your a -99 for the status within the GSS console but it will show as a green check for success.  This will also allow you to continue with other tasks within the same imaging job.

 

Source: DEFECT
ID: LB 67333, 3935500 ,3887655
Description:

Logged in Littlebuggy (Altiris - Lindon, Plymouth) database

Imported Document ID: TECH39771
Legacy ID: 41238

Thanks for your feedback. Let us know if you have additional comments below. (requires login)

    © 1995-2019 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.