1. ZPL II, ZBI 2, Set-Get-Do, Mirror, WML Programming Guide
  2. Mirror
  3. Mirror Overview
  4. Requirements
  5. Creating ZPL Files for Use in the <update-root>/files Directory
  6. Configuration
  7. How to Set Up and Use Mirror
  8. Troubleshooting
  • ZPL II, ZBI 2, Set-Get-Do, Mirror, WML Programming Guide
Troubleshooting

Troubleshooting

If a Mirror process completes unsuccessfully, troubleshooting information can be retrieved by sending this command to the printer: 
! U1 GETVAR "ip.mirror.last_error"
Table 1 lists possible printer responses, an explanation of each, and resolutions. Table 2 provides problem scenarios and solutions.
A mirror path can have up to 50 characters.
Printer Response Troubleshooting
Printer Response
Explanation
Resolution
"connection failed"
The network connection to the Mirror FTP server failed while attempting to perform a printer update.
  • Check the user name, password, and server address for the Mirror FTP server and ensure that these values are set correctly in the printer.
  • Ensure that the user name assigned to the printer has the proper permission to log into the Mirror FTP server.
  • Check that the printer has a successful network connection and is able to send and receive network data.
"Failed to get File: [filename]"
During an update operation, the printer's attempt to retrieve the file [filename] failed.
  • Ensure that the printer's network connection has not been interrupted. If it has, re-establish network connectivity and retry the update.
  • Check the server's access permissions for the user name assigned to the printer. Make sure the user name is granted access to read [filename] from the server.
"feedback connection failed"
The network connection to the Mirror FTP server failed while attempting to send printer feedback.
  • Check the user name, password, and server address for the Mirror FTP server and ensure that these values are set correctly in the printer.
  • Ensure that the user name assigned to the printer have the proper permission to log into the Mirror FTP server.
  • Check that the printer has a successful network connection and is able to send and receive network data.
"Failed getting file to parser : [filename]"
During an update operation, the printer’s attempt to retrieve a file [filename] in the
<mirror_path>/appl
directory failed.
  • Ensure that the printer’s network connection has not been interrupted. If it has, re-establish network connectivity and retry the update.
  • Check the server’s access permissions for the user name assigned to the printer. Make sure the user name is granted access to read
    [filename]
     from the server.
"Failed to send feedback file: <feedback_path>/<feedback_filename>"
During a feedback operation, the printer’s attempt to store the feedback file in the
<feedback_path>
 directory failed.
  • Ensure that the printer’s network connection has not been interrupted. If it has, re-establish network connectivity and retry the update.
  • Check the server’s access permissions for the user name assigned to the printer. Make sure the user name is granted access to write to the
    <feedback_path>
     directory.
  • Ensure that the
    <feedback_path>
     directory exists on the remote server.
"Too many files in the firmware download directory"
The Mirror FTP server has more than one file in the
<mirror_path>/appl
 directory.
Ensure that there is only one (1) firmware file in the
<mirror_path>/appl
directory.
Problem Scenario Troubleshooting
Problem Scenario
Solution
I performed a Mirror Update and now my printer is continuously reprogramming.
Ensure that the name of the firmware file in
<mirror_path>/appl
 matches the version of firmware contained in that file.
For firmware version V53.17.2Z, the name of the file in the
<mirror_path>/appl
 directory must be
V53.17.2Z.ZPL
 to prevent the continuous reprogramming cycle.
Every time a Mirror Update is run, a file is fetched even though no changes have been made to the files on the server.
  • Check the names of the files in the
    <mirror_path>/files
     and
    <mirror_path>/commands
     directories. If the names are longer than 16 characters (minus extensions), then the printer will truncate them to 16 characters when downloading. If two filenames truncate to the same 16 characters, the printer will not be able to tell the difference between them and will re-download one of the two files during every update operation.
  • Check the names of the files in the
    <mirror_path>/files
     and
    <mirror_path>/commands
     directories. If any of the names are the same, then the printer will not be able to tell the difference. Therefore it will get the one in the files directory, update the timestamp file, and then it will get the one in the commands directory and update the timestamp file. Then, the next time through the one in the files directory will have a different timestamp, so it will get that file again and then check the commands directory, and so on.
  • Check the server's access permissions for the user name assigned to the printer. Make sure the user name is granted access to read all files in the
    <mirror_path>/files
     and
    <mirror_path>/commands
     directories.
The printer is continually rebooting.
  • Check the
    /commands
     directory. If a
    file.delete
     command resides, then you need to remove
    file.delete
     or modify your script.