Troubleshooting
Introduction
This chapter describes what you can do if you do not get the results you expect when you run APGetInfo:
- 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.
Reviewing the Troubleshooting Checklist
This troubleshooting checklist describes common problems. It is the first place to look for a possible solution to your problem.
All platforms
Are you trying to retrieve information from one or more encrypted files?
You must specify the -d option, followed by a User password, as in the following example. (An Owner password will not work.)
You can only specify one User password. Therefore, all of the encrypted files you include on the command line must have the same User password. If you want to retrieve information from encrypted files that have different User passwords, run a separate command for each User password.
Are you using any options that require a file name (-o, -l)?
The file name must immediately follow the option, as in the following examples:
-o C:\Appligent\APGetInfo\samples\myoutput.txt
-l /Appligent/APGetInfo/mylogfile.txt
If a text string other than a file name follows the option, APGetInfo will recognize that text string as the file name.
Did you receive an error “this file cannot be found”?
You may not have provided the correct path for all files or you may have misspelled a file or directory name.
Is each input file a PDF document?
APGetInfo can only open 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 APGetInfo 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 APGetInfo 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.
UNIX only
Did you get a “command not found” error?
If you get a command not found error when running APGetInfo in its own directory, enter the command with the dot-slash in front of it, as in the following example:
./apgetinfo /Appligent/APGetInfo/samples/APUtilsSample.pdf
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.