Image file path is invalid

Possible Cause:  When using the img makep or img restorep command, you might have specified the location of the image file (UNC path) using backslashes. Backslashes are not recognized as such by Linux*.

Action:  Use forward slashes or enclose the entire UNC path in quotes. For example:

img makep 137.65.95.127 //xyz_server/sys/imgs/dellnt4.zmg

or

img makep 137.65.95.127 "\\xyz_server\sys\imgs\dellnt4.zmg"

Possible Cause:  When using the img make or img restore command, you might have omitted the .ZMG extension from the image filename, or you might have used a different extension.

Action:  You must use a .ZMG extension for the image filename. For example:

img makel dellnt4.zmg

or

img makep 137.65.95.127 //xyz_server/sys/imgs/dellnt4.zmg

If you omit the extension or use a different one, the imaging engine uses .ZMG anyway.

Possible Cause:  When using the img makep or img restorep command, you might have specified a filename with spaces in it. If long filenames are allowed by the operating system, this will work; if not, see the action below.

Action:  Enclose the filepath parameter in quotes. For example:

img makel "Dell NT 4 Image.zmg"

Possible Cause:  When using the img makep or img restorep command, you might have specified a different server in the address parameter than in the filepath parameter. In this case, the one specified in the address parameter is used, and if the specified path doesn't exist on that server, you get the error message.

Action:  See Image Is Created on or Restored from the Wrong Server in Troubleshooting Workstation Imaging in Troubleshooting.

  Previous Page: Imaging Error Messages  Next Page: Failed to write to proxy