Troubleshoot Activation Errors

Use this article to troubleshoot errors that occur when activating Dotfuscator.

Dotfuscator Is Not Activated

You may encounter:

You must activate Dotfuscator Professional to execute command-line builds. Run the Dotfuscator Config Editor to enter your License Key.

This error occurs when Dotfuscator has not been activated on the current machine. For more information, see Activation.

Serial Number Was Previously Used

You may encounter:

This serial number (...) has previously been used to register. Please submit a request for registration assistance or to purchase additional licenses.

This error occurs when your license does not permit activation on another machine.

If the error appears in an automated build log, Dotfuscator may be activating through:

• The DOTFUSCATOR_LICENSE environment variable.
• A command-line argument.

When builds run on dynamically provisioned build agents, each job registers a new machine for the license. This environment requires a Floating License. Other license types produce the error.

For more licensing information, see Contact PreEmptive.

Internet Connection Errors

You may encounter one of the following errors:

• There is a problem reaching the activation server: "...". This license type requires access to the PreEmptive activation server before a build. Contact PreEmptive support for help.
• Error: Could not verify the subscription for this license. "..." This license type requires access to the PreEmptive subscription server before a build. Contact PreEmptive support for help.

These errors occur when Dotfuscator encounters a network problem while contacting PreEmptive servers:

• During activation.
• Before a build that uses a Floating License.

An internet connection is required in these cases. Dotfuscator retries a failed connection once before displaying the error.

Troubleshoot the Activation Tool

Activation through the Windows Installer or Config Editor uses the Dotfuscator Activation Tool.

The tool opens a browser where you can sign in and activate the Dotfuscator installation. After activation, the browser sends the required information back to the Activation Tool, which verifies and saves the activation.

Windows Firewall Displays an Alert

The Activation Tool listens on a TCP port for the localhost hostname so that it can receive information from the browser.

This may cause Windows to display the following security alert:

Windows Defender Firewall has blocked some features of Node.js: Server-side JavaScript on all public and private networks.

The alert refers to client-activation-bridge-win.exe, which is part of the Activation Tool and runs using Node.js.

Because the Activation Tool listens only on localhost, it does not require a firewall exception.

To dismiss the alert:

1. Clear all the checkboxes.
2. Select Cancel.

Activation Tool Does Not Continue After Browser Activation

If the browser’s HTTP request to the Activation Tool is blocked or fails, the browser may report that activation was completed while the Activation Tool continues to wait.

To complete activation manually:

1. Locate the Activation Token in the browser’s success message.
2. Copy the token.
3. In the Activation Tool, select Click here to activate manually.
4. Enter the activation token.
5. Select Activate.