DocConverter Release Notes

2010 R4.3 Build

This article contains the software release notes for ActivePDF DocConverter Enterprise 2010 R4.3 (build This release includes bug fixes.

Software Requirements

The following software is required to successfully use DocConverter.

  • Windows Server® 2003 (32- or 64-bit edition) OR
  • Windows Server® 2008 (32- or 64-bit edition) OR
  • Windows Server® 2012

Additional Software Requirements

  • Microsoft® .NET Framework 3.5 (If it is not detected, it will be installed automatically)
  • LibreOffice® 3.6.2 (if not installed, DocConverter can install it automatically)
  • (Optional) Microsoft Word®, Excel®, PowerPoint®, (2003, 2007, or 2010)
    (These applications are needed if the file types are in use and you want to use the application's own converter instead of the LibreOffice converter)
  • (Optional) Corel® WordPerfect X5 (WordPerfect 15) (if these file types are in use)

Hardware Requirements

The minimum hardware requirements for DocConverter are: 

  • 512 MB of RAM
  • 90 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.

Bug Fixes 


Known Issue



When adding a watermark to a PDF/A conversion, an error message was returned and the conversion failed. The error log recorded the conversion error "Object reference not set to an instance of an object".

Conversions that include watermarks now produce valid PDF/A files as expected.


When a PDF to PDF/A conversion failed, an output PDF was still generated in the output location. With an API conversion, an appropriate error code was returned indicating a failure, but a PDF was still written to the output location.

When a conversion to PDF/A fails, the source file is now moved into the errors folder, and a PDF is not generated in the output location.


Illegal characters in a file path caused Office Verifier to crash.

Illegal characters in a file path now result in an error message.

Installation and API Reference 

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