DocConverter Release Notes 2014.1.1.15328

Build 2014.1.1.15328

This ActivePDF DocConverter release (Build 2014.1.1.15328) 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

Additional Software Requirements

  • Microsoft® .NET Framework 4.0 (If it is not detected, it will be installed automatically)
  • LibreOffice® 4.2 (if not installed, DocConverter can install it automatically)
  • (Optional) Microsoft Word®, Excel®, PowerPoint®, Visio®, Publisher® (2007, 2010, or 2013)
    (These applications are needed if the file types are in use and you want to use the application's native converter instead of the LibreOffice converter)
  • (Optional) Fuji Xerox DocuWorks® Viewer Light 7.2.1 minimum (if these file types are in use)
  • (Optional) Corel® WordPerfect X5, X6, and X7 (WordPerfect 15, 16, 17) (if the file type is in use and you want to use the application's native converter instead of the LibreOffice converter)

Note: If you will be using WordPerfect, install it before you install DocConverter.
If DocConverter is already installed:

  1. Stop the activePDF P3 service before installing WordPerfect.
  2. Install WordPerfect.
  3. Execute the WordPerfectCheck.exe application located in:
    C:\Program Files\activePDF\DocConverter\WordPerfect
  4. Restart the activePDF P3 service.

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 Feature

In the DocConverter user interface, you can now select the file extension name for the output PDF:

DocConverter > Watch Folder Profiles > Conversion Settings > PDF section > PDF Extension

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.


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.

The built-in converter decompresses compressed object streams and does not re-compress them in the output PDF.

If no other operations are performed (for example, adding security or metadata), the files will pass through without a change to the image compression.


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 attempting to convert the Excel file, DocConverter returns a -10263 error (an error was encountered generating the output file). After considerable time, an output file is created.

No workaround at this time.


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.


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

No workaround at this time.


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

No workaround at this time.

Bug Fixes

The following bugs were resolved since the last release.





Remote: When calling ZipToPDF, DocConverter attempted to convert the actual zip file.

The problem was related to difficulties deleting read-only files from the temporary directory. This has been resolved, and DocConverter now extracts and converts zipped files as expected.


During installation, the converter verifier did not perform the verification process for the Microsoft Publisher 64 bit application.

This has been resolved and now Microsoft Publisher is verified as expected.


When calling the API Debug property to enable or disable verbose logging, the API call did not overwrite the debug setting in DocConverter:
DocConverter > General tab > Write Debug Messages.

API calls should always take precedence, and overwrite any settings in the DocConverter UI.

Setting the Debug property using the API now overrides the DocConverter UI settings as expected.


When an FTP profile was set up in the DocConverter UI and used by a Watch Folder, after successful conversions the files were not uploaded to the FTP site.

DocConverter did not read the remote location path for uploading. This has been corrected and files are now uploaded to FTP sites as expected.


COM: When a stamp collection did not exist, and StampText or StampImage was called, the output PDF did not include the stamp unless AddStampCollection was called first. Expected behavior: DocConverter should create a stamp collection automatically if one does not exist.

This issue is resolved; if needed, DocConverter now automatically creates a stamp collection when StampText or StampImage is called.


If a file had a filename longer than 90 characters, the conversion failed.

The temporary file path used in the code was changed to a generated GUID; and the issue is now resolved.

Additional Solutions

These occurrences may happen when DocConverter is working as expected.



What to do


When DocConverter attempts to convert a Microsoft Works .wps document using the Word converter, a memory error is returned and the conversion fails.

Microsoft Office 2010 and 2013 do not support Microsoft Works .wps files.

Use the Microsoft Office 2007 or LibreOffice converter.


When Watch Folders were configured to a mapped drive (for example, P:\ ) DocConverter does not recognize the address and files are not converted.

DocConverter does not recognize mapped drives when used in a file path. Use UNC paths.



Cannot change the user name for DocConverter.

See the KB article:

Changing User Credentials for DocConverter


The Microsoft Word engine does not support OpenType CFF fonts. When you use Export for conversions, the Microsoft engine rasterizes any OpenType CFF fonts found in the text.

You have three options for handling this issue:

A. Use OpenType fonts with non-CFF outlines, or another non-CFF font.

B. Use the print mode instead of export mode to produce the output PDF.

C. Edit the DocConverter XML settings file to convert the OpenType CFF fonts to bitmap images.

Steps for Option C:

To edit the XML settings file

1. In a text editor, open the DocConverter settings file found in:
C:\ProgramData\activePDF\Settings\DocConverter\ DC_Converters.xml

2. Under the <Converters:Alias>Microsoft Word</Converters:Alias> tag,
find: <Applications:BitmapMissingFonts>1</Applications:BitmapMissingFonts>

3. Change the value from 0 to 1.

4. Restart the DocConverter service.

Further steps for Option C:

If you have edited the XML and the issue remains, you may also need to make this adjustment to the DCOM settings as well.

To edit the DCOM settings

1.    Open DCOM Configuration (from run "dcomcnfg").

2.    Go to the properties of the Microsoft Word object:

3.    Click the Identity Tab and set it to The interactive user.

4.    Restart the DocConverter service.

Installation and API Reference 

Installation and API information is available in the DocConverter Legacy documentation section at: