DocConverter Release Notes 2014.1.2.16159


This ActivePDF DocConverter release (Build 2014.1.2.16159) includes a new feature and bug fixes.

Software Requirements

The following software is required to successfully use DocConverter.

  • Windows Server® 2008 (32- or 64-bit edition) OR
  • Windows Server® 2012 R2
  • Microsoft® .NET Framework 4.0 (If it is not detected, it will be installed automatically)

Optional Software Applications

  • (Recommended) Default converter: LibreOffice 4.2 (if not installed, DocConverter can install it automatically)
  • Install these applications if you want to use their native converters instead of the default converter:
  • Microsoft Word®, Excel®, PowerPoint®, Visio®, Publisher® (2007, 2010, or 2013)
  • Fuji Xerox DocuWorks® Viewer Light 7.2.1 minimum
  • Corel® WordPerfect X5, X6, and X7 (WordPerfect 15, 16, 17)

Note: Install the applications before installing DocConverter.

Hardware Requirements

The minimum hardware requirements for DocConverter are:

  • 512 MB of RAM
  • 150 MB of hard disk space (for application)


  • Additional hard disk space is needed to meet the requirements of the installed applications and the volume of files being processed.
  • ActivePDF does not officially support running DocConverter in a Remote Desktop Services (RDS), Terminal Services or Citrix environment.

New Features

In DocConverter you can now convert password-protected Microsoft® PowerPoint® files.
If a password is needed to open a PowerPoint file:

  1. Open the DocConverter Configuration Manager.
  2. Go to:
    Watch Folder Profiles > Conversion Settings >Input Password.
  3. Enter the password.

Or: Use the DocumentPassword property in the API to pass the password.

Bug Fixes

The following bugs were resolved since the last release.

ID #




DocConverter UI: After creating a new signature for .xml files using a signature type of text, the new signature did not display in the UI and could not be used.

Fixed the issue that prevented the UI from saving the text signature.


Some graphic file types that included Japanese characters in filename failed to convert.

This issue is resolved, and graphic files with Japanese characters will now convert.


When Alter the output PDF filename (3) was used for the OverwriteMethod and used with ConvertFromPDF, the setting was ignored, and any PDF with the same filename was overwritten.

A separate document is now created with a unique filename.


When DocConverter was configured to run a script after conversions, the script was not run.

This issue is resolved, and scripts now run as expected.


If a filepath was not configured for the Originals folder in the Watch Folder, the source file was deleted after conversion.

The code has been updated to allow the Originals file path in Watch Folder to be blank. If blank, the input file is removed after conversion.


When DocConverter was configured for a silent installation, DocConverter created Desktop shortcuts for the DocConverter UI and the Watch Folder.

Now silent installations do not install Desktop shortcuts.

Known Bugs

When a bug is fixed, it is moved to the Bug Fixes table.

Note: Even if a workaround exists, the bug may be fixed in a later release.

ID #

Known Issue



File specific: After converting a PDF to PowerPoint, the text in the output PowerPoint is not horizontally aligned.

No workaround at this time.


File set specific: After converting the PDFs to PowerPoint or Microsoft Word, bullets and tables in the output files do not display correctly.

No workaround at this time.


File specific: When the timeout is set to 10 minutes, this file has a timeout failure before 10 minutes has elapsed.

No workaround at this time.


File Specific: When the Microsoft Word converter is used in the export or print mode, the Microsoft Word document fails to convert to PDF/A and the output PDF does not display correctly.

Use the built-in converter.


File specific: When converting the email .MSG file, the output PDF displays the wrong characters.

No workaround at this time.


After a PDF to PDF conversion, the output file is two to three times larger than the input file.

No workaround at this time.



File specific: When FromPDF_ToHtml is used, the output HTML is distorted.

No workaround at this time.


LibreOffice converter: When using LibreOffice to convert an email .MSG file that includes Japanese characters, the conversion fails.

Use the Microsoft Word converter.


File specific: When the PDF with a table is converted to text , the tabular content in the output text file is shifted unexpectedly.

No workaround at this time.


File specific: After converting a scanned PDF to PDF/A, the output PDF is blank.

No workaround at this time.


File specific: A user-defined font in the input file appears pixelated in the output PDF.

No workaround at this time.


File specific: After converting the .TIFF file, when the output PDF is opened an error is returned: "insufficient data for an image".

No workaround at this time.


File specific: After converting PS to PDF, when text from the output PDF is copied and pasted into a Microsoft Word file, the hyphens are missing (although they display in the PDF).

No workaround at this time.


File specific: When attempting to convert a PDF form to PDF/A1-b, the resulting PDF/A file is non-compliant, but no warning message is issued.

PDF/A1-b does not support forms so an alternate option should be used. However, DocConverter should return an error indicating the PDF/A could not be created.

There is no workaround at this time. In the interim, when converting files to PDF/A, we recommend running a PDF/A verification on the output files as a post-processing step.


File specific: Converting the file to PDF/A returns the error code 10270 (Error encountered converting PostScript to PDF).

No workaround at this time.


When DocConverter is configured to send emails after successful file conversions and UNC file paths are used in the settings, emails are not always sent.

No workaround at this time.


File specific: When the PostScript file is converted, the output file has garbled text.

No workaround at this time.


When a PDF containing PDF stamps is converted to a Microsoft Word document, the output file does not include the stamp graphic.

Conversion of PDF stamp graphics to Word is not currently supported. No workaround at this time.


When DocConverter is configured for PDF/A conversion and also for PDF compatibility level, the compatibility level in the output PDF is always PDF version 1.6, no matter what compatibility level is chosen.

No workaround at this time.


DocConverter UI using Microsoft Internet Explorer browser: There is a time lag moving to new screens, the Microsoft Internet Explorer browser is slow to load a new page in the DocConverter UI.

Use a Chrome or Firefox browser.


When LibreOffice is installed, it configures itself as the default program for opening Microsoft Office files (such as .docx, .xlsx)

After installing LibreOffice, reset the file associations for each Microsoft Office file type that is used.

Or install Microsoft Office after installing DocConverter/LibreOffice and rerun the Office Verifier.

Note: This does not affect how DocConverter performs file conversions. It DOES impact the behavior of document files when they are opened interactively or manually on the DocConverter server.


File specific: When convert to PDF/A is attempted, the conversion fails.

No workaround at this time.


File specific: When using Print to PDF, only two pages of the three-page Excel file are converted to PDF.

Use Export to PDF.


File specific: When using the LibreOffice engine to convert an .eml (email) file, a blank page is added to the output PDF.

Use the Microsoft Word engine if available.


File specific: When the linearized PDF is secured with passwords, the PDF to PDF/A conversion fails.

No workaround at this time.


File specific: When the .xlsx file is converted using OutputIntent = Screen, the output is cutoff.

Use OutputIntent = Print.


File specific: When the email .msg file is converted, the output PDF text includes the HTML tags.

No workaround at this time.


When Microsoft Word files have images added using both the IncludePicture field code and by copy and pasting in the images, after conversion, the output PDF does not always include all the images.

To insert an image in Microsoft Word, use either the IncludePicture field, or copy and paste, but do not use both methods in the same file.


After using DirectToPDF (Export) to convert Microsoft Word files, if the output PDF is opened in Adobe®Acrobat® , the first page cannot be deleted. An error message reports that the PDF has an invalid structure.

Use PrintToPDF for conversion.


DocConverter UI: When a custom file extension is added to the extensions list in the Basic signature, and DocConverter attempts to convert a file that has that extension, the converter selected does not handle the conversion properly.

No workaround at this time.


File specific: When using FromPDF_ToWord with ConvertFromPDF, the content on some pages is converted to header material, instead of being part of the normal document content flow.

No workaround at this time.


File specific: When using FromPDF_ToExcel with ConvertFromPDF, only the content that is in tables is included in the output Excel file.

If you are converting a file with images or content that is not in a table, use FromPDF_ToWord or a similar type conversion.


When using FromPDF_ToExcel with ConvertFromPDF, the commas used in the numbering are not included in the output Excel file.

No workaround at this time.


File specific: When using Direct (Export) with PDFConversionType for converting this Excel file, the output PDF is longer than expected.

In the Windows Devices and Printers window, select a different default printer.


File specific: Barcode fonts are installed and used in this .rtf file, but after conversion to PDF, text displays instead of the barcode.

Windows is not allowing access to the fonts during conversion.


Note: Always be very careful when making edits in the Registry Editor.

1.    Open the Registry Editor (regedit).

2.    Go to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion/Fonts

3.    Right click on Fonts, select Permissions, and set Full Control for the Users.

4.    Reboot the machine to take effect.

Note: After rebooting, there will be a long delay before Desktop loads.


File specific: After conversion, the output PDF is missing the logo image.

No workaround at this time.

Installation and API Reference 

Installation and API information is available in the documentation at: