Message | Solution |
|
|
Could not get the file. | Verify that a valid PC/printer |
| connection exists. If so, verify the |
| syntax of the command and retry it. |
Could not put the file. | Verify that a valid PC/printer |
| connection exists. If so, verify the |
| syntax of the command. Then, retry |
| the command. |
Could not remove directory: | Verify that the directory you specified |
| exists and retry the command. |
Could not save file locally. | There is not enough space on the PC |
| to save a file received from the |
| printer. Free some space and retry |
| the command. |
Did not receive a response from | Verify that a valid PC/printer |
the Ultra. | connection exists. If so, increase the |
| length of the timeout. Then retry the |
| command. |
| From the user perspective, a |
| command may finish running, but |
| there can still be processing going |
| on behind the scenes before the |
| command is truly finished. A timeout |
| can occur during this timeframe. |
| Therefore, when a timeout error |
| occurs, check to see if the command |
| actually finished or not before trying |
| to correct the problem. For example, |
| if the error occurred on a put, verify |
| that the file copy completed. |
Error Running command on | A |
Ultra. Returned Error = xxx | printer. Retry the command. If the |
| same error occurs, |
| printer and/or have it serviced. |
|
|