Working with PDF Conversions 3-15
Since the URL path is identical to 000123, your relative URL link in the document for 000456 would only need to be:
000123.pdf
■
Example 2: Relative linking to a different document type
Using the same document names, if you checked document 000456 into the same security group but a different document type, its web viewable URL
would look like:
http:machineucmgroupspublicdocumentsadcorp000456.pdf This means that your relative URL link needs to go up one directory and then
into adacct to find 000123.pdf. So the relative URL link would be: ..\adacct\000123.pdf
■
Example 3: Relative linking to a different document security
Now if you also change the security group of document 000456, its web viewable URL would look like:
http:machineucmgroupssecuredocumentsadcorp000456.pdf This means that the relative URL link will need to go up three directories and
then back down to 000123.pdf. So the relative URL link would be: ..\..\..\public\adacct\000123.pdf
6.
Check the documents into the content server. When converting the documents to PDF, the refinery will create links relative to the location of the web viewable file
for each document you are checking in.
3.3 Troubleshooting PDF Conversion Problems
This section covers the following topics:
■
Troubleshooting Process for PDF Conversion Issues on page 3-15
■
Common Conversion Issues on page 3-16
■
Inbound Refinery Setup and Run Issues on page 3-17
■
PDF Display Issues on page 3-21
3.3.1 Troubleshooting Process for PDF Conversion Issues
The vast majority of PDF conversion issues fall into one of the following categories:
■
When a file is checked into the content server, a PDF is not generated.
■
A PDF is generated, but there are problems with the output. When troubleshooting PDF conversion issues, you should first try to identify if the
issue is related to just one specific file, all files of that type, or all files. For example, if you are having problems converting a Microsoft Excel document to PDF, try checking
in other Microsoft Excel documents; preferably files that are smaller and less complex. If the problem is specific to a single file, the problem is most likely related to
something within the file itself, such as file corruption, file setup and formatting, and so forth.
PDF not generated:
3-16 Administrators Guide for Conversion
If a PDF is not generated when a file is checked into the content server, complete the following basic troubleshooting steps:
1.
Look at the Inbound Refinery and agent logs and identify which step of the conversion process failed printing to PostScript, PostScript to PDF conversion,
etc.. For more information about viewing Inbound Refinery and agent logs and enabling verbose logging for agents, refer to the Inbound Refinery Administration
Guide.
2.
If the file is timing out during conversion, first try checking in another, smaller, less complex file of the same type. If multiple files are timing out, adjust your
timeout values and re-submit the files for conversion. For more information about configuring timeout values, refer to the Inbound Refinery Administration Guide.
3.
If the file is failing to print to PostScript, try printing the file to PostScript manually. Most failure to print to PostScript issues are related to the following
possible causes:
■
The IDC PDF Converter PostScript printer is not installed.
■
The IDC PDF Converter PostScrpt printer is not named or set up properly.
4.
If the file is printing to PostScript successfully but failing to convert to PDF, again first try checking in another, smaller, less complex file of the same type. If the
problem is not specific to a single file, or you cannot identify a problem within the files that is causing the conversion to fail, the problem is most likely related to the
distiller engine that you are using.
3.3.2 Common Conversion Issues
