Server Release Notes 2013.2.0.15351

Build 2013.2.0.15351

This article contains the software release notes for ActivePDF Server 2013 R2 (2013.2.0.15351). This release includes bug fixes and new features.

Software Requirements

The following software is required to successfully use ActivePDF Server.

  • Windows Server® 2008, 2008R2
  • Windows Server® 2012 R2
  • Microsoft® .NET 4.0 (Installed by Server if not detected on your system.)

Hardware Requirements

The minimum hardware requirements for ActivePDF Server are:

  • 246 MB of RAM
  • 170 MB of hard disk space (for application)

New Features

When using ConvertPSToPDF, you can now set the page dimensions for the output file without scaling.

Using the UI or API, you can use the new FontPath property to specify the alternate font path, if any, to use during the PostScript™ conversion.

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: When the PCL file is converted, the output PDF does not display as expected.

No resolution at this time.


VBScript: Japanese OS: When using ConvertImageToPDF and ConvertPSToPDF with a file path that has Japanese characters, the conversion fails.

Use ASCII characters in folder names.


File specific: When the PostScript file with layers is converted, the layers are not preserved in the output PDF.

No resolution at this time.


File specific: When this PCL file is converted, the output PDF is missing some content.

No resolution at this time.


When SetInfo is used to include Author and Keyword metadata and a comma is included in the information, double quotes are added to the Author and Keyword metadata in the output PDF.

No resolution at this time.


File specific: This .DOCX file (which contains tables that use dotted lines for line styles) takes three minutes to convert.

Change the lines styles for the tables from dotted to solid lines.

Bug Fixes

The following bugs were resolved.





After using SetOutputSecurity, opening the secured PDF in the user interface removed the security.

This is resolved in the new user interface. When a secured PDF is opened, you are prompted for a password, and the security remains after closing the PDF.


File specific: When Server converted this PostScript™ file to PDF, some background elements displayed an ivory color instead of white.

This is resolved and the output PDF displays as expected.


.NET only: If a bookmark name included parenthesis (), the bookmark did not display in the output PDF. Any subsequent bookmarks added were also missing.

This is resolved and now bookmark names may include parenthesis.


After every conversion, a file named test.xml was created in the root of the C: drive.

The code was updated and the test.xml file is no longer created.


Files specific: Although the fonts were installed, when this PostScript file was converted, the output PDF was missing the service mark and copyright characters.

FontPath handling was enhanced in the code and now the output PDF displays the characters as expected..

Additional solutions

These occurrences may happen when Server is working as expected.






File and font specific: When this PostScript™ file using CID- (character ID) keyed CJK fonts was converted, the output had garbled characters.

CID map files provide the encoding for CID-keyed CJK fonts.

Placing a CID map file for the CJK font you are using into this folder may solve the issue of garbled characters:

[Common Application Data]\ActivePDF\Include.

Server will pick up the CID map file at runtime and determine the proper font substitution.


Installation and Getting Started

For installation instructions and general startup information, see the Legacy Documents section for  ActivePDF Server Getting Started Guide at:

API Reference

See the Legacy Documents section for ActivePDF Server API Reference Guide for information about .NET and COM methods and properties at: