Skip to main content

Enable the Jet Excel add-in in a clustered environment

Overview

When working in a clustered environment, the Jet Excel add-in must be installed on each server in the cluster and must be enabled within Excel on each server for each Jet user.

Methods to enable Jet in Excel

There are three methods an organization can enable Jet within Excel on each server in the cluster.

  1. Method 1 - Use Jet Reports shortcut

    After the Jet Excel add-in is installed, users can create a Jet Reports App shortcut on the desktop. When you use the Jet Reports shortcut to launch Excel, the Jet Excel add-in is automatically enabled before the Excel is opened.

  2. Method 2 - Run the Enable Jet Add-in application

    Whenever a user accesses a system where the Jet add-in is not yet enabled, they should enable it by running the Enable Jet Add-in application as an administrator from the Windows Start menu.

    jet_not_present.png

  3. Method 3 - Modify login script

    A system administrator should modify the login script for each Jet user so that the script calls the Jet Enable Utility (C:\Program Files (x86)\JetReports\Jet.Activator.exe) when a user logs in.

Troubleshooting - Admin can examine Windows Registry

A system administrator can examine the Windows Registry of a Jet user who is experiencing issues with enabling the Jet add-in.

Following is the Registry key where the enable add-ins for Excel are tracked:

HKEY_CURRENT_USER \ Software \ Microsoft \ Office \ {version of Office} \ Excel \ Options

Under that key, there is a subkey created for each installed add-In. The subkey is called "OPEN", "OPEN1", "OPEN2" etc. depending on how many add-ins are installed and enabled.

The value of each subkey is the path to the VBA add-in (.xla or .xlam) to which the key corresponds.

The path to the Jet add-in should appear in that list.  It is also necessary that the individual user have sufficient permissions to read the Registry settings.

e.g.,

registry.png

Related Articles

Was this article helpful?

We're sorry to hear that.