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

PDF problems, Editor problems

Get Xerox 6180N - Phaser Color Laser Printer PDF manuals and user guides
UPC - 095205425307
View all Xerox 6180N manuals
Add to My Manuals
Save this manual to your list of manuals

Page 113 highlights

Troubleshooting PDF problems The following questions may be helpful to ask when trying to isolate a PDF problem: • Was the PDF created from the original PostScript using the latest version of Adobe's PDF Distiller? • Does the original PostScript file print correctly? • Will all of the pages of the job open with Adobe Acrobat? • What application and/or PDF software created the PDF file? • With the printer's error pages turned on, does the printer produce a PostScript error page? • Has the file been redistilled again using a newer PostScript? • Are all of the document fonts downloaded and included within the job? • What was used to create the PDF? PDF Writer or Adobe's PDF Distiller? Editor problems For problems with the Editor, diagnostic and troubleshooting should start with the Editor. The following is the command that validates that the Editor is "alive": ps -ef|grep XRXuiEdit The administrator may be able to isolate the problem by monitoring the XRXuiEdit process operations and following these steps: 1. Login as root. 2. Kill XRXuiEdit and GUI process. 3. Copy the updated executable class file over to the system: 4. opt/XRXnps/XRXuiEdit/bin/pdfView Edit/*.class files and 5. opt/XRXnps/XRXuiEdit/bin/pdfParser/*.class files. 6. Restart the Xerox FreeFlow Print Server GUI using./ startGUI command. 7. Verify the /opt/XRXnps/logs/ui_logs from a terminal window to monitor its output message. System Guide 8- 11

  • 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-11
Troubleshooting
PDF problems
The following questions may be helpful to ask when trying to
isolate a PDF problem:
•
Was the PDF created from the original PostScript using the
latest version of Adobe’s PDF Distiller?
•
Does the original PostScript file print correctly?
•
Will all of the pages of the job open with Adobe Acrobat?
•
What application and/or PDF software created the PDF file?
•
With the printer’s error pages turned on, does the printer
produce a PostScript error page?
•
Has the file been redistilled again using a newer PostScript?
•
Are all of the document fonts downloaded and included within
the job?
•
What was used to create the PDF? PDF Writer or Adobe’s
PDF Distiller?
Editor problems
For problems with the Editor, diagnostic and troubleshooting
should start with the Editor. The following is the command that
validates that the Editor is “alive”:
ps -ef|grep XRXuiEdit
The administrator may be able to isolate the problem by
monitoring the XRXuiEdit process operations and following these
steps:
1.
Login as root.
2.
Kill
XRXuiEdit
and GUI process.
3.
Copy the updated executable class file over to the system:
4.
opt/XRXnps/XRXuiEdit/bin/pdfView Edit/*.class
files and
5.
opt/XRXnps/XRXuiEdit/bin/pdfParser/*.class
files.
6.
Restart the Xerox FreeFlow Print Server GUI using
./
startGUI
command.
7.
Verify the
/opt/XRXnps/logs/ui_logs
from a terminal
window to monitor its output message.