WebGrabber Release Notes 2013.1.1.14197

WebGrabber 2013 R1.1 Build 2013.1.1.14197

This article contains the release notes for ActivePDF WebGrabber 2013 R1.1 (Build 2013.1.1.14197).

NOTE: This build (2013.1.1.14197) of ActivePDF WebGrabber 2013 supercedes previous R1.1 builds. Specifically, users performing conversions with the IE Engine should download and install the latest build (2013.1.1.14197).

Important Changes

A change was made to the API to add the WaitBeforePrinting property for use with the IE Engine (in addition to use with the Native Engine in the initial release of WebGrabber 2013). Use WaitBeforePrinting to specify the time (in seconds) that WebGrabber waits before printing the URL. This wait time allows asynchronous objects to load on the page.

Bug Fixes

The following bugs were resolved in this release of WebGrabber.





Uninstalling a Remote installer results in an error message. The message varies slightly with each remote installer, but will be similar to, "On Pre Uninstall, Line 20: attempt to call global 'val'(a nil value)."

The remote installer uninstallation routine was updated.


Using CreateFromHTML with special characters results in unexpected output.

Special characters are no longer converted, and are instead contained in an xml CDATA block.


Calling MediaType = 1 does not retain the screen CSS in WebGrabber Enterprise.

Use WebGrabber 2013 to call MediaType.


Calling CreateFromHTMLText results in output that is missing lines.

Special characters are no longer converted, and are instead contained in an xml CDATA block.


CaptureRequestXml is implemented in the .NET dll but not in COM.

CaptureRequestXml was implemented in the COM ATL.


Setting Impersonation = true with DoPrint in ASP.NET fails with a NetNamedPipe WCF exception.

Using impersonation with DoPrint no longer results in an exception.


When calling the CreateFromHTMLText property for certain HTML files, the conversion results in an exception.

Special characters are no longer converted, and are instead contained in an xml CDATA block.


.NET and Native Engine Only: When CreateFromHTML is called before the HTMLTextToFile property, the text is not printed to the output PDF.

HTML written to CreateFromHTMLText prior to setting HTMLText to file is now included in the output PDF.


Configuration Manager (UI) Only: Attempting to save a WebGrabber profile results in the error, "waitbeforePrinting is invalid."

The Print Wait option was assigned a default value of 0.


IE Engine Only: The IE Engine uses IE7 compatibility mode by default and ignores the compatibility level set in the browser itself. This can only be changed by setting the appropriate registry setting for the application or by having the X-UA-Compatibility header in the html.

A new setting was added to the UI for Browser Emulation. To set the compatibility level, edit the WG Profile in the Configuration Manager. Select a Browser Emulation Option: Internet Explorer 10, Internet Explorer 10 Emulate, Internet Explorer 9, Internet Explorer 9 Emulate, Internet Explorer 8, Internet Explorer 8 Emulate, Internet Explorer 7, EDGE or Undefined.


An exception occurs when converting a text file over 24KB with the CreateFromHTMLText property.

CreateFromHTMLText functionality was updated to save the html to a file prior to conversion.


COM Only: Calling ClearHTMLText does not clear CreateFromHTMLText.

CreateFromHTMLText functionality was updated.


Converting a PDF containing an item list results in different output for each engine (Native and IE). The Native Engine produces output with the item list in a table, while the IE Engine does not contain the item list.

The WaitBeforePrinting property was added to the IE Engine. Setting the value to 1 second provides enough time for the IE Engine to render the content.


When a timeout occurs, the Timeout property returns the wrong code (-12 or -30) instead of -99. This issue occurs as an Exception error (-12) when using the .NET dll with the IE or Native engines, and as -12 with COM and the Native engine.

The Timeout property was updated to return -99 on timeout.


The WGIELogin is not FIPS-compliant, and returns the following error when a user is added, "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms."

Updated the WebGrabberLogin.exe and the service to use a FIPS-compliant algorithm. When installing or running the executable and there is data stored by the older encrytion scheme, the login displays an error and the dialog box shows no data. This is expected behavior.


A basic default font test including the following fonts fails, as the output PDF does not match the expected result: MainFont, FontNormal, FontAddress, FontBlockQuote, FontDir, FontExample, FontHeading1, FontHeading2, FontHeading3, FontHeading4, FontHeading5, FontHeading6, FontListing, FontMenu, FontPreformatted.

Basic font functions apply styles to the HTML prior to printing.


SetPageNbrParams is not cleared after disposing of the WebGrabber object.

Header and footer page number parameters are cleared when the WebGrabber object is released.


COM Only: FooterHTML does not apply the page numbers set in SetPageNbrParams.

The ATL DLL correctly sets header and footer page number parameters.


Converting a Web page in Hebrew with CreateFromHTMLText results in a -12 exception.

Pages with Hebrew text are converted and an exception is no longer thrown.


Add WaitBeforePrinting functionality, which was previously available only for the Native Engine, to the IE Engine.

The WaitBeforePrinting property was added to the IE Engine specify the time (in seconds) that WebGrabber waits before printing the URL. This wait time allows asynchronous objects to load on the page.


Attempting to convert HTML containing a ScriptX object with the IE Engine results in a -12 exception. The log file reads, "Result Exception: Only one ScriptX object can be used per browser window."

Added a check for an existing ScriptX factory in the HTML.


FILE SPECIFIC: WebGrabber does not return error codes or write a log file in the event of a failed conversion via Remote Connection.

A syntax error in the script prevented it from properly executing. When the script was edited to call oWG.ConvertToPDF, rather than WG.ConvertToPDF, WebGrabber returned -30, as expected.

Known Issues

This section lists known WebGrabber 2013 R1.1 issues. When a known issue is fixed, it is moved to the Bug Fixes table. NOTE: The availability of a workaround does not imply that a particular issue will not be fixed.


Known Issue



When using page breaks, the bottom cell of a page is split improperly, resulting in the text being split between two pages.

Use page-break-inside, where applicable. See Resolving Table Rows Split Across Pages for instructions and cautions.


When converting HTML to PDF, the first page of the output PDF has a larger amount of space before the first line of text than do subsequent pages.

This is an issue with a third-party component. See HTML to PDF Conversion with the Native Engine Results in Inconsistent Spacing for a workaround. Alternatively, use the IE Engine.


PDF hyperlink locations are shifted when the linked text is located within a table, and when margins are applied to the output (Native Engine only).



EmbedFlash does not work for an absolute path.

Use a virtual path rather than an absolute path.


SetOutputSecurity encrypts the title when no metadata is passed.

Pass in metadata via the API or the UI.


Native Engine Only: Field Borders on some text boxes are cut off on conversion.

Use the IE Engine.


Text at page break is cut off when SetMargins is used. (Native Engine only)

Use the IE Engine.


Japanese characters in text areas are garbled in the output PDF. (Native Engine only)

Currently, the workaround is to use the IE Engine. NOTE: PDF text boxes will not be preserved. This issue will be resolved in a future release.


Converting Right to Left languages results in paragraphs that are not properly aligned. In addition, extra pages appear for page-breaks in the output PDF.

In some cases, removing the first page-break-after in the HTML and changing the remaining page breaks to page-break-before will resolve the issue.


Intermittently, dynamic charts created with Google Chart Tools are not included in the output PDF. (IE Engine only)

Current workaround is to use the Native Engine.


FILE SPECIFIC: Converting an HTML file containing Kendo UI graphs results in the following error, "This page contains the following errors: error on line 1 at column 891: Expected '#' or '[a-zA-Z]', but got ' '.
Below is a rendering of the page up to the first error." (Native Engine only)

Charts should be modified to utilize HTML character codes for special characters in embedded titles (i.e. replace "&" with "&").


HTML anchor links are not handled correctly in the output PDF.

Feature Request #246 has been created to support creation of internal PDF links when converting files with anchor links.


FILE SPECIFIC: There are extra horizontal and vertical lines inside the output PDF.

The HTML should be updated to ensure that the border is inside the <div> tag, rather than inside the table cell.


Including a .PNG image in the input HTML results in an increase in the text font weight, causing it appear bold.

Current workaround is to use the IE Engine. This will be resolved in an upcoming release.


A dotted line that is clearly visible on a web page, appears as a solid line, or a randomly broken line in the output PDF. Zooming may make the line appear dotted.

Current workaround is to use the IE Engine. This will be resolved in an upcoming release.


Conversions using IE9 and IE Engine result in output file size increases by 80 - 100% over that of files converted using IE7 or IE8.

See ActivePDF WebGrabber Conversions with Internet Explorer 9 for workarounds.


Values of text input boxes or text areas are not preserved in the output. (Native Engine only)

Current workaround is to set HTML form fields font property to use one of the Base14 fonts. Alternatively, use the IE engine (NOTE: Text boxes are not preserved with the IE engine.)


Native Engine and COM Only: When using the preserve settings, such as PreserveTextboxes and PreserveCheckboxes, the resulting form fields are misaligned.

Use IE Engine with COM, or use Native Engine with .NET.


Native Engine Only: The content, including radio buttons and text boxes, appears cut in half between pages when FitToPage = true.

Use the IE Engine.


IE Engine Only: Form content is cut off at page break in the output PDF.

Use the Native Engine.


Native Engine Only: The checkmarks within checkboxes are distorted in the output PDF.

Use the IE Engine.


Native Engine Only: When using the HTML tag <body style='background-color:blue;'>, the background color is not completely filled in.

Use the IE Engine.


The size specified in the HTML for an SVG image is not respected, and results in an extremely small image in the output PDF. (Native Engine only)

Current workaround is to use the IE Engine.


Font names in Document Properties > Fonts of the output PDF are garbled in conversions using the IE Engine with IE9.

See ActivePDF WebGrabber Conversions with Internet Explorer 9 for workarounds.


Calling SetSecurity Methods (i.e. SetPDFSecurity, SetPDFSecurity128, SetPDFSecurityAES, SetOutputSecurity or SetOutputSecurity128) with linearize methods (i.e. LinearizePDF or LinearizeDocument) produces an undesirable output PDF.

Do not attempt to call SetSecurity methods along with linearize methods.


The output PDF is not editable. The error, "All or part of the selection has no available system font. You cannot add or delete text using the currently selected font," appears when attempting to edit the PDF.

See ActivePDF WebGrabber Conversions with Internet Explorer 9 for workarounds.


Visit the ActivePDF Examples site to see updated examples for WebGrabber 2013:



See the following link for the Legacy section of the Getting Started Guide (including installation instructions) and the WebGrabber 2013 API Reference: