Troubleshooting Output Device Problems

If you are having trouble printing output from Applications Manager, use the following table as a troubleshooting guide.

Symptoms Causes Action

Printing to most output devices is successful. However, one or more devices do not print, and don't give any error messages.

The Inactive radio button is selected in the output device's Auto Output Options box.

Make sure the Active radio button is selected in the output device's Auto Output Options box.

The interface script assigned to the output device's output interface is not defined correctly.
  1. Verify that the interface script has execute permissions for Applications Manager.
  2. After the interface script to echo its command line to a log file rather than executing the command.

    3. For example change
    eval "lp $* $file" to
    echo "lp $* $file" >
    $AW_HOME/exec/LPP.log    .

  3. Look at the log file (for example, LPP.log) to check that the syntax of the command is correct.
  4. Execute the log file (sh LPP.log) to see if it prints the document.

    5. If it prints, then the problem may be with Applications Manager. Call Automic Support.

    If the file does not print, then the problem is with your system.

An Applications Manager error message states that printing was unsuccessful.

Any

Record the details of the message, then call Automic Support.

Output files are not being created.

Permissions on the output directory may not be set correctly.

Verify that Applications Manager has write permission in the output directory.

New files cannot be written to the output directory because:

  • There is no free disk space
  • There are too many files already in the directory.

Verify that Applications Manager can write a file to the output directory. Free some disk space or clean out unneeded files as necessary.

The task failed before it could generate any output.

Check the Backlog or History to see if the task aborted. Determine why the task aborted.

Output files can be viewed from the Explorer window, but they do not appear on the Output window.

The output was generated with an output function of PRINT or STORE.

To view the output, query the Output window for status codes of PRINT and/or STORE.

To make the output files viewable by default on the Output window, set the output function for the job to LOG.

The SYSOUT output device was assigned to the job or process flow.

Select a different output device.

Debugging Printer Problems

When troubleshooting printing issues, it's probably best to start by debugging the task's system output file (the o file) in addition to screen shots of the printer and the spooler from the Applications Manager client. Make sure the output interface's (spooler's) print command works from the command line. Check the configuration settings before getting debug.

To turn on printing debug, create the following 0-byte files in the debug directory (notice that here AWMAIL and SYS_PRINT are listed to cover both AWMAIL printing problems and system printing problems):

Then run the task and look for a awprint*log file in the log directory.