Xerox 6180N FreeFlow® Print Server System Guide - Page 111

Job integrity problems, Tray to media mapping problems, Gateway problems, PDL problems - printer driver

Page 111 highlights

System Guide Troubleshooting Job integrity problems If the job does not print as expected (missing pages, missing data, incorrect page orientation, incorrectly ordered sets, job attribute inconsistencies), perform the following: 1. Check the job properties to ensure proper programming. 2. Check for any queue override attributes that may be conflicting with the job programming. 3. If the job is PCL or PostScript, check for job ticket information that may have created a problem with the job. Make changes and resubmit the job. Tray to media mapping problems The JPM logs contain the job attributes that the XPIF library is setting. In cases where the tray to media mapping is not happening as expected, then this log can give clues on how the mapping is being translated into job attributes. /opt/XRXnps/log/JPM.Debug.Log Gateway problems Gateway logs reveal how the data is being received by the system. /opt/XRXnps/log/CGAPI.Debug.Log (for IPP gateway) /opt/XRXnps/log/XLP.Debug.Log /opt/XRXnps/log/Socket.Debug.Log PDL problems If a problem exists with a PDL job, the System Administrator can ask the job submitter specific questions to identify the problem. Possible questions that may help are the following: • What printer driver was used to create the file? • What application was used to create the file? • Do all applications create this file format? • Have you tried to use a different printer driver? If not, do so to conclude if it also creates problems. • Has the file printed previously on a different printer? • Was the file recreated and resubmitted? • Have you checked to see if the destination queue is accepting files? Were the resources adequate? • Did this file or a similar file print on a previously installed version of the system software? 8- 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136

System Guide
8-9
Troubleshooting
Job integrity problems
If the job does not print as expected (missing pages, missing data,
incorrect page orientation, incorrectly ordered sets, job attribute
inconsistencies), perform the following:
1.
Check the job properties to ensure proper programming.
2.
Check for any queue override attributes that may be conflicting
with the job programming.
3.
If the job is PCL or PostScript, check for job ticket information
that may have created a problem with the job. Make changes
and resubmit the job.
Tray to media mapping problems
The JPM logs contain the job attributes that the XPIF library is
setting. In cases where the tray to media mapping is not
happening as expected, then this log can give clues on how the
mapping is being translated into job attributes.
/opt/XRXnps/log/JPM.Debug.Log
Gateway problems
Gateway logs reveal how the data is being received by the
system.
/opt/XRXnps/log/CGAPI.Debug.Log (for IPP gateway)
/opt/XRXnps/log/XLP.Debug.Log
/opt/XRXnps/log/Socket.Debug.Log
PDL problems
If a problem exists with a PDL job, the System Administrator can
ask the job submitter specific questions to identify the problem.
Possible questions that may help are the following:
What printer driver was used to create the file?
What application was used to create the file?
Do all applications create this file format?
Have you tried to use a different printer driver? If not, do so to
conclude if it also creates problems.
Has the file printed previously on a different printer?
Was the file recreated and resubmitted?
Have you checked to see if the destination queue is accepting
files? Were the resources adequate?
Did this file or a similar file print on a previously installed
version of the system software?