The PDF conversion program, which is launched by MarkLogic Server to perform the conversion, crashed. Often this is caused by something unexpected in the PDF itself or by an error in the PDF configuration file.
Try either converting specific page ranges of the document or disabling image extraction to see if the problem is associated with a particular page or feature. Try using a different configuration file. Otherwise, if you have a current maintenance contract with MarkLogic, you can contact support with the detailed test case and error message.
PDF conversion is executed in a program launched by MarkLogic Server and is protected by a limited-duration license key generated when the conversion program launched. If the key is checked after it expires, this error will be raised. Usually this is a sign that the host is overloaded, causing an excessive delay between launch and execution.
PDF conversion is executed in a program launched by MarkLogic Server and is protected by a limited-duration host-bound license key generated when the conversion program is launched. This error will be raised if the conversion program sees a different host than the server. This may be caused by unusual DNS configurations.
PDF conversion failed due to an internal error passed up from the responsible libraries. This error indicates that the conversion process ran out of memory.
Try conversion with the PDFtoText.cfg
configuration file (config
option). If that works, try normal conversion with illustrations
and image-output
set to false
. If the PDF is large, try converting a few pages at a time; if you are using CPF consider one of the batched conversion pipeline alternatives. If you have a current maintenance contract with MarkLogic, you can contact support with the detailed test case and error message.
Parameter too long. You probably have a very long path or filename, try shortening it. variable2
PDF conversion failed due to an internal error passed up from the responsible libraries. This error indicates the PDF configuration file references a macro that has not been defined.
Try running conversion with a different configuration file ("config" option). If you are using a custom configuration file, make sure you spelled the macro name properly; or escape macro syntax if you don't intend to refer to a macro. Otherwise, if you have a current maintenance contract with MarkLogic, you can contact support with the detailed test case and error message.