| 1001 | The product found a syntax error with the command line options. | |
| 1002 | The JSON profile file was not found. | |
| 1003 | There was a syntax error in the JSON profile. | |
| 1004 | One of the values assigned to a parameter in the JSON profile was not valid. | |
| 1005 | The command line statement is missing a required argument for the input file. | |
| 1006 | The command line statement is missing a required argument for the output file. | |
| 1007 | The input file was not found. | |
| 1008 | The input file found has an unsupported file type. | |
| 1009 | The software could not connect to the Internet to verify the product license. | |
| 1010 | License activation unknown. | |
| 1011 | License inactive. Your license may have been disabled by the vendor. | |
| 1012 | License activation already in use by another user. | |
| 1013 | License expired. | |
| 1014 | License failed. Verify that the activation key was entered properly. | |
| 1015 | There was a problem in setting up Office. Try restarting your system. | |
| 1016 | There was a problem with converting an Office file. The file may be corrupt or mislabeled. | |
| 1017 | There was a problem in creating output for an Office file. The file may be corrupt or mislabeled. | |
| 1018 | There was a problem in reading the Office input file. The input path may be invalid. | |
| 1019 | An error occurred in creating output for an Office file. The output path may be invalid. | |
| 1020 | The Resources directory for Office files is missing. Please check your product installation or reinstall the software. | |
| 1021 | The PostScript ps.vm file is missing. Please check your product installation or reinstall the software. | |
| 1022 | The PostScript superatm.db file is missing. Please check your product installation or reinstall the software. | |
| 1023 | The PostScript startupNORM.ps file is missing. Please check your product installation or reinstall the software. | |
| 1024 | The PostScript ICCProfiles directory is missing. | |
| 1025 | The PostScript fonts directory is missing. | |
| 1026 | There was a problem in converting a PostScript file. The file may be corrupt. | |
| 1027 | There was a problem creating the output for a PostScript file. The file may be corrupt. | |
| 1028 | Encapsulated PostScript files with a binary preview are not supported. | |
| 1029 | FLIP2PDF could not create a PDF/X compliant document from the PostScript input file. Please change the PDF output type to PDF. | |
| 1030 | You tried to start the FLIP2PDF API, but the API was already initialized and running. | |
| 1031 | The FLIP2PDF API has not yet been initialized. FLIP2PDFInitialize() must be called first. | |
| 1032 | Log files created after an Office conversion failed are still present and need to be deleted.
When you start FLIP2PDF, the product looks for any error log files left behind by an Office conversion and deletes them if found. These files can keep FLIP2PDF from starting. If FLIP2PDF fails to delete these files properly, you will see this error message. The log files are found in this directory in Windows:
And in this directory in Linux:
Delete every file you find in this location and then try to start FLIP2PDF again. |
|
| 1033 | Problem converting PDF document to HTML. Try changing to a different web layout, like using “desktop” instead of “tablet.” |