DocConverter Release Notes 2014.0.4.15255

Build 2014.0.4.15255

This ActivePDF DocConverter release (Build 2014.0.4.15255). This release includes new features 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 Features

This release of ActivePDF DocConverter includes the following features and capabilities:

  • New converters — Now includes support for Microsoft Visio® and Publisher®; Fuji Xerox DocuWorks®; Office 2013.
  • An override converter option for Watch Folders — Allows you to override the converters at a folder level.
  • Additional PDF/A standards support — Converts to and verifies all levels of compliance with:
  • PDF/A-1 a, b formats: Specialized for the digital preservation of electronic documents.
  • PDF/A-2 a, b, u formats: Support JPEG2000, transparency, embedding OpenType fonts, digital signatures.
  • PDF/A-3 a, b, u formats: Allow embedding of file formats such as XML, CSV, Word, and Excel into PDF/A as complete archived objects.
  • Improved ZIP file handling — ZIP files can now continue processing even if individual files error out; ZIP output creates subdirectories for easier retrieval of converted files.
  • Enhanced Email conversion — Convert HTML or text emails and their attachments into PDF.
  • Attach the original source files — Embed the original input file into the output PDF with AttachOriginal.
  • AES encryption — Add AES encryption to your PDFs.
  • New administrator interface — The new Configuration Manager User Interface (UI) improves usability, improves loading time and provides easy management of product settings.
  • Enhanced error handling — The new Results object provides more details about errors than earlier versions do.
  • Convert PDFs to multi-page .tiff files — A PDF can now be converted to a .tiff file that contains a subfile for each PDF page.

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



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

Use the LibreOffice converter.


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 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 Watch Folders are configured to a mapped drive (for example, P:\ ) DocConverter does not recognize the address and files are not converted.

Use UNC paths (such as \\my-server\mydirectory\mywatchfolder.)


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.


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

Verify Microsoft Publisher manually by opening it and clearing any pop-ups or activation prompts.


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.


When PDFs are secured with passwords, PDF to PDF/A conversions fail.

No workaround at this time.


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

Use OutputIntent = Print.

Bug Fixes

The following bugs were resolved after the Beta 2 release.





File specific: The PDF did not convert to a PDFA compliant document.

The document now converts as expected.


Installation: When logged in as an added user with administration rights, the Converter Verification application failed to run.

The Converter Verification application now runs as expected.


.NET: Revisions and comments were not included in the output PDF.

Revisions and comments are now included.


File specific: when converting a Microsoft Word document containing linked images to PDF or PDF/A, the output PDF sometimes did not display all the images.

A default wait time when converting Microsoft Word files containing linked images has been introduced, and now Word files with linked images convert as expected.

For more information, see the KB article: Microsoft Word Files with Linked Images


OpenRemoteConnection requires that port parameter is a string.

Parameter was changed to accept a long.


Passing 0 for Port does not work

Passing 0 now reverts to default Port value, as expected.


A sub folder in Content.Word temp directory continued to build up temp files (related to bug 3469).

All temporary files are now cleared as expected.

Bug Fixes Beta 2

The following bugs were resolved in the Beta 2 release.





During a PDF conversion, the Microsoft converter created Microsoft Office files (such as .wmf and .emf files) that were placed in the Temporary Internet Files folder and not deleted.

Temporary files older than four hours are now cleared when the conversion application initializes.


File specific: When using the LibreOffice or Microsoft Word converter to convert the email, the conversion failed.

The email now converts as expected.


When attempting to use Export to convert a Microsoft Excel file larger than 1 MB to PDF, the conversion failed.

The Excel file now converts using either Print To PDF or Export to PDF.
Note: If Print to PDF is used, and the file is larger than 1 megabyte, the timeout period on the Watch Folder should be increased.


File specific: The PowerPoint file failed to convert to PDFA.

The PowerPoint file now successfully converts to PDFA.


File specific: DocConverter was unable to convert the .tiff files to PDF.

The files now convert as expected.


.NET: If the default PDF profile was set to PDFA in the UI, and PDFA was set to false in the API, a PDF still converted to a PDFA file.

The API setting overrides the UI setting and the file now converts to PDF as expected.


File specific: The PowerPoint file did not convert to a PDF.

The internal code for the PowerPoint Open method was changed to match the default behavior of PowerPoint, and now the file converts as expected.


File specific: The Excel file failed to convert to PDF.

The failure was caused by Excel attempting to export structure tags during conversion. To prevent this issue, the default Output Intent option was changed from Print to Screen.


When converting a file with the same file name of an earlier conversion, the conversion failed with a "file in use" error.

DocConverter now uses unique temporary directories to prevent name collisions.

Bug Fixes Beta 1

The following bugs were resolved in the Beta 1 release.

File specific: When converting the .RTF file to PDF/A, the output PDF was blank.

The file now converts as expected.


File specific: When attempting to convert the PDF file to PDF/A, a -258 error (PDF generation exception during conversion) was returned.

The file now converts as expected.


File Specific: When DocConverter attempted to convert the .TIFF file, the output PDF was blank and no error message was returned.

The file now converts as expected.


When converting MSG or EML files, the timestamp in the mail header was reformatted from dd/mm/yyyy to mm/dd/yyyy in the output PDF.

This issue is resolved, and the dates now display as expected.


Under stress, eventually DocConverter's Microsoft Word converter would freeze, resulting in failed conversions.

This issue is resolved, and files convert as expected.


File Specific: When the source document included a private character (created in the Microsoft Private Character Editor) the character did not display in the output PDF.

The output PDF now displays the private character as expected.


File specific: When the Microsoft Word converter is set to Print to PDF in the settings tab of the Converter Profiles page, and the Watch Folder uses a PDF Profile set to PDF/Aconversion, the Microsoft Word document converts to PDF, but the source document is moved to errors folder instead of the originals folder.

The document converts to PDFA as expected, and the source document is moved to the originals folder.

Additional Solutions

These occurrences may happen when DocConverter is working as expected.



What to do


File specific: When attempting to convert a .RAR file that was renamed to .DOC, the conversion failed.

DocConverter does not support .RAR files.

When DocConverter encounters a .RAR file, it first converts it to a PostScript file. This PostScript file may be very large (possibly many gigabytes, depending on the source file). The PostScript file may time out before it is converted. If it does, the .RAR file is moved to the errors folder. If the PostScript file does not time out, and converts to a PDF file, the resulting PDF file is composed of binary text symbols, and is not usable.

Note: If a .RAR file's extension is renamed to .doc or .docx, the same issues remain. The file is still intrinsically a .RAR file.

To exclude .RAR files (and .RAR files whose extensions have been changed) from a Watch Folder, create a binary signature that identifies .RAR files, and set up a filter using the signature. See the Signature Profiles topic in the Quick Start Guide for more information.


Excel file: When a PDF with a watermark is converted to an Excel file, the output Excel file does not include the watermark.

Remove watermarks from Excel files before conversion. DocConverter does not convert Excel files that include watermarks.


When Watch Folders are installed on a remote UNC path, the emails set up to be sent after a successful PDF conversion were not sent

In order to run conversions with remote Watch Folders, the login information for the remote machine's local Admin user needs to be added to the Watch Folder's profile.

1.    In the DocConverter UI, go to the Watch Folder Profile screen.

2.    Select the Watch Folder to edit.

3.    In the Credentials dropdown menu for each folder, select Custom.

4.    In the fields that appear, fill in the Domain, Name, and Password for the remote local Admin account.

Once the Watch Folder is set up and working correctly, set up the email profile to use in the Email Profiles page.

Select the email profile in the Post Process Options tab in the Watch Folder Profiles page.

This should now generate an email when a conversion is successful.


DocConverter UI: In the Conversion Options tab of the PDF Profiles page, when Attach File is selected, the text entered for Subject is not added to the output PDF.

The subject information is included; to view it: right click on the attachment icon.


When UseLegacyReturnCode is set to True, some return codes do not exactly match the DocConverter 2010 return codes.

For a map of the DocConverter error codes that map to the current DocConverter error codes, please see the 2010 Return Codes Map in the DocConverter API Reference Guide.


When using Print to PDF, document metadata from the source file is not included in the output PDF.

To include metadata from the source document in the output PDF, use Export to PDF or add metadata using API scripting.


DocConverter UI: If a new signature is added in Signature Profiles, it does not appear in the list of signatures in the Filter Profiles in the Default filter.

New signatures cannot be added to the default filter. To use a new signature, create an new filter profile, then select the new signature.

Installation and API Reference 

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