- 1 Introduction
- 2 Reviewing the Troubleshooting Checklist
- 2.1 All platforms
- 2.2 UNIX only
This chapter describes what you can do if you do not get the results you expect when you run APSplit:
- Review the troubleshooting checklist
- Clean suspect PDF files. If you cannot solve the problem, refer to Support to find out how to contact customer support.
This troubleshooting checklist describes common problems. It is the first place to look for a possible solution to your problem.
Are you trying to retrieve information from one or more secured files?
You must specify the -d option, followed by the Owner password, as in the following example. (The Owner password is also called the Master password or the Permissions password.)
You can only specify one Owner password. Therefore, all of the secured files you include on the command line must have the same Owner password. If you want to split secured files that have different Owner passwords, run a separate command for each Owner password.
Are you using any options that require a file or directory name (-o, -l)?
The file or directory name must immediately follow the option, as in the following examples. If a text string other than a file or directory name follows the option, APSplit will recognize that text string as the file name. APSplit will also recognize a directory name as a file name if it does not end with a slash.
Are all file and path names correct?
The best practice is to use full path names for all files. That includes input files, output files, and log files. Also make sure that all directory names end with a slash (back slash in Windows, forward slash in UNIX/Macintosh).
Is each input file a PDF document?
APSplit can only split PDF files. If you are using wildcards, include the pdf suffix (for example, *.pdf) to help prevent you from accidentally attempting to open a non-PDF file.
Are you using APSplit in a script?
Use full path names for all files and applications accessed from within the script. If you cannot get your script to work, make sure that you can run APSplit from a command line.
Are you getting unexpected results from one or more PDF files?
There might be something wrong with the file. See Cleaning up PDF Documents below.
Did you get a “command not found” error?
If you get a command not found error when running APSplit in its own directory, enter the command with the dot-slash in front of it, as in the following example:
./apsplit -o /Appligent/APSplit/outPDFDirectory/Appligent/APSplit/samples/inPDFFile
This tells your system that the application is in the current directory.
Do the application files have the execute permissions set?
If they don’t, you must set them.
You have completed the distillation process. Try using the distilled PDF file with APSplit. If you experience problems, see Support.