Resolutions for Common WebGrabber Error Codes

Resolutions for more commonly encountered error codes.

-1 General exception from the Agent.

Probable Causes

  • There is an issue with the Agent. Turn on verbose logging to view detailed
  • If this is a remote submission, you may be using the wrong port.


  • The error is a general error and is difficult to diagnose without the data from the verbose log. See
    Turn on Verbose Logging For WebGrabber
    for instructions.
  • For remote submissions, ensure you are using the correct port. For COM, use Port 52525. For .NET, use Port 57975.

-12 Error displayed in the COM environment, Error message in .NET: "Error with ConvertToPDF".

This issue can occur in both the COM and .NET environment.

When using COM, a -12 error occurs "Exception caught printing PDF".

In the .NET environment, the this exception displays:

Error with ConvertToPDF
Exception caught printing PDF.

The log file in both environments records:

"Unable to cast COM object of type 'mshtml.HTMLObjectElementClass' to interface type 'ScriptX.Factory'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{BCE02EE6-7566-42E2-8FE3-48CED948908E}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

Probable Cause

ActiveX is not enabled in IE 11.


For instructions on how enable ActiveX in IE 11, see the KB titled: Enabling ActiveX Controls in IE 11.

-12, -30, -3005 Error Codes

Probable Causes

Usually occurs when WebGrabber is configured with the wrong IP address or port.

If an incorrect IP address or port number is used:

  • COM returns -3005 or -30 error code.
  • NET returns -12.


A. DoPrint, ConvertToPDF, and port assignments

DoPrint was deprecated and replaced with ConvertToPDF method. Make sure to:

  • Change your code so that it uses ConvertToPDF rather than DoPrint
  • Check the port assigned to WebGrabber, use Port 52525 for COM services and Port 57975 for .NET services.

    Note: In legacy versions, by default the assigned port was 54545 for .NET deployment, and 90 or 58585 for COM deployment.

B. Remote application points to the wrong IP address

If your application is running in the same machine as the WebGrabber installation, the IP address is typically (localhost).

If the application is accessing WebGrabber from the remote machine, the application needs to point to the correct IP address of the machine that is running WebGrabber.

For example: is the machine where WebGrabber is installed. is the remote machine that has the application. The application should point to in the ConvertToPDF method.

-101 Core service exception.

Probable Cause

There was an unknown exception with the ActivePDF Core Service.


Restart the ActivePDF Core Service.

-383 When attempting to create a PDF.

Probable Cause

Occurs when the output folder does not have correct permissions to create the resulting PDF. Typically, Everyone/Full Control permissions are given. However, the permissions can be adjusted to allow at least Read/Write access.


If restricting users, the user under whom the application is run should have access to the output folder.

-10099 Error code.

Probable Cause

This error occurs when attempting to write to a UNC path as the output directory and the services associated with WebGrabber do not have read/write access to the UNC path.


Resolution: Write the output to a local drive, or ensure that all services have read/write access to the UNC path.

  1. Ensure that WebGrabber is installed using a Local Administrator account or Domain account in the Local Admin group of the machine.
  2. Open Windows Services.
  3. Right-click ActivePDF Com Service, and then select Properties.
  4. Click the Log On tab.
  5. Select This account, and then type the account information for the Local Administrator (or Domain Account in local admin group of the machine) account used to install WebGrabber.
  6. Click OK.
  7. Right-click ActivePDF Com Service, and then select Restart.
  8. Create an identical user (local admin) on the UNC machine with the same user name and password. (Ex. DCAdmin)
  9. Add the user to ensure access to the folder(s).

NOTE: Be sure to provide the correct paths in your application.

-10099 Using WebGrabber with DotNetNuke.

Probable Cause

Session credentials are not being passed to the WebGrabber object.


Ensure that you are passing on the session credentials to the WebGrabber object. Consult your system administrator for further details on permissions with DotNetNuke.

-10147 Requested job has failed to find an agent (after submitting a PDF generation request).

Probable Cause

The requested job failed to find an available application to perform the operation. This error typically occurs if the ports used by the ActivePDF software are blocked by the system's firewall.


ActivePDF products require that certain assigned ports remain open and available to the software services in order to generate PDF output. On some systems, a firewall can prevent these ports from being accessed and cause requested operations to fail. In order to correct this issue, the firewall should be modified to permit the necessary ports.

NOTE: The process for adding permissions/exceptions may vary if using a firewall other than Windows Firewall.

To change permissions for Windows Firewall:

  1. Click Start, then select Control Panel. Double-click Windows Firewall.
  2. Select the Exceptions tab, and then click Add Port.
  3. Enter the Name and Port number for the port to be allowed through the firewall. The ports to be added will depend on your installed product(s):
    • All Products
      • 53536 (ActivePDF Agent Service Port)*: Used to receive Agent registration messages (UDP) and status verification messages (TCP).
      • 11100 (First Aid Service Port)**: Used by First Aid agent to perform job requests.
      • 11101 (First Aid Message Port)**: Used by First Aid to process UDP/TCP communications.
      • 54545 (ActivePDF Core Service Port)*: Used for Remote .NET calls to the Core Services (both from API and intra-job processing).
      • 57975 (ActivePDF NotDotNet Proxy Port)*: Used for Remote non-.NET calls to the Core Services (from API).
    • ActivePDF Server
      • 10800 (ActivePDF Server Agent Service Port): Used by the Server Agent to perform job requests (PSToPDF, ImageToPDF, etc…).
      • 10801 (ActivePDF Server Agent Message Port): Used by the Server Agent to process UDP/TCP communications.
    • ActivePDF WebGrabber (Enterprise/Cluster Editions)
      • 11000 (ActivePDF WebGrabber Agent Service Port)**: Used by the WebGrabber Agent to perform job requests (DoPrint, ConvertHTML, etc…).
      • 11001 (ActivePDF WebGrabber Agent Message Port)**: Used by the WebGrabber Agent to process UDP/TCP communications.
    • ActivePDF DocConverter
      • 10900 (ActivePDF DocConverter Agent Service Port)**: Used by the DocConverter Agent to perform job requests (Submit, Hot Folder conversion, etc…).
      • 10901 (ActivePDF DocConverter Agent Message Port)**: Used by the DocConverter Agent to process UDP/TCP communications.
  4. Select TCP as the protocol and click OK.

* Denotes ports which, in a clustered environment, only require access on the Cluster Controller machine.

** Denotes ports which, in a clustered environment, only require access on the Node machine(s).

Note: Once you have added the necessary ports, you may need to restart the corresponding Agent Services for the changes to take effect.