Create and/or Deploy image tasks fail with an error in the console "Error -99"
The path to the image file the is specified in a job is not valid. This can be caused by a credentials problem in the automation configuration, or a pathing error in the image job. This can also be caused by invalid characters in the folder or file name.
When an imaging task is created the path that is specified to the image file must be valid according to the client that is in Automation.
Solution #1: The images are in the default images share, you need to repair the mapping to the default images share.
The most common cause of this problem is a credentials issue in the automation configuration. If the password changes for the user that is specified in automation configuration the map will not be created properly and this error will result.
If you are seeing this error when you are working with image files in the default images share and you are still seeing this error that probably means the default images share has not mapped properly. If the default images share has not mapped properly, this error will appear whenever the path within an imaging job points to an image in the default express share.
To test if the default images share has mapped properly follow these steps:
Another test is to try running the net use command to map the drive to the express share at the command prompt.
Here is the documentation for the net use command:
Here is an example of usage of the net use command to map to the express share if the Ghost server is called "GhostServer"
net use m: \\GhostServer\express
If you are unable to map this share at the command prompt you either do not have credentials, or some security has been applied that is stopping the drive mapping from working. Contact Microsoft for assistance if you are unable to map network drives in your environment.
Solution #2: The images are on a network share.
If your image file is on a network share you should create a mapped drive to the network share within automation. It is easiest if the map to this network share is exactly the same in Automation as it is on the Ghost Server. The steps to configure an additional network drive are specified in this document: https://support.symantec.com/en_US/article.HOWTO125350.html
Solution #3: The images are on a different physical drive that is connected to the Ghost server
If your images are located on a second physical hard drive that is connected to your Ghost server you can either map the second location as a network drive or you can use "mklink" to create a shortcut from your default images share to the new images share.
The steps for using an mklink are in this document:
Solution #4: Use GhostCast
Unlike a regular imaging task, if you are using GhostCast to distribute an image, the path that is specified in the image job needs to be valid according to the GhostCast Server, not the client in automation. There is no option in the Ghost Solution suite console to define a Create Disk Image job using GhostCast, to use GhostCast to create an image you would need to launch the GhostCast server manually and define the parameters of the job within GhostCast, rather than as a job. For Distribute Disk Image jobs you can launch GhostCast manually and configure your job, or you can use GhostCast on an imaging job by checking the Data transfer mode (Ghost Only) checkbox and enter a GhostCast server session name. When you click Finish it will offer to launch the GhostCast server for you with the parameters you specified.
Solution #5: Unusual characters in the image path
Do not use anything other than alphanumeric English characters in your folder or image file name.
Underscores in the folder names can cause this problem.
Non-English characters in the file name can cause this problem.