Toolkit 2017 1.1 Release Notes

This Toolkit 2017 R1.1 release (Build 2017.1.1.18186) includes bug fixes.

Software Requirements

The following software is required to successfully use Toolkit.

Servers Supported

  • Windows Server® 2008 (32- or 64-bit edition)
  • Windows Server® 2008 R2
  • Windows Server® 2012 R2
  • Windows Server® 2016
  • Microsoft® .NET Framework is required to use Toolkit's .NET component
    (1.1, 2.0+, or 4.5.)

Note: If this is the first time you are installing Toolkit 2017 on a Windows 2012 server, you need to download and install two Microsoft updates for Windows 2012 servers. These updates resolve issues with the Microsoft Visual C++ Redistributable Runtime Components. For links and step-by-step instructions, see this ActivePDF Knowledge Base article: Installing Toolkit 2017 on Windows 2012 Servers.

Desktops Supported

(32- or 64-bit editions)

  • Microsoft Windows® 7, 8, 8.1, 10
  • Microsoft® .NET Framework is required to use Toolkit's .NET component
    (1.1, 2.0+, or 4.5.)

Hardware Requirements

The minimum hardware requirements for Toolkit are:

Server and desktop

  • 125 MB of RAM
  • 25 MB of hard disk space (for application)

Bugs Fixed

ID #




When a form field was edited to use MS Mincho font, other font was used instead.

Additional mapping for font name to font file was added to the code, and this resolved the issue.


When several files with subset fonts were merged, and DeleteUnusedFonts was called, the output contained garbled text, and redundant instances of subset fonts.

Changes to the code related to the usage of font properties resolved this issue.


Toolkit was unable to handle image streams from PowerBuilder.

Changes to the code relating to how memory streams from PowerBuilder are initialized resolved this issue.


File specific bugs.

These issues are now resolved.
Please contact customer support for further information.


Installation and API information is available in the Legacy documentation section for the Toolkit API Reference Guide at: