Perpetual (legacy) Licensing

This article covers license keys for the various Windward Studios products; common licensing software errors; licensing restrictions; license key corruption issues; and other licensing tips.

Please use these links to jump to your section of interest.

How Do I Retrieve My License Keys?

When Must I Update My License Keys?

How Do I Update My License Keys?

Important License Information

License Key Tips

License Key Exceptions

License Key Corruption

Internal Communication Protocols and Ports

Licensing Restrictions

License Copy Protection

How Do I Retrieve My License Keys?

If you have not yet purchased keys or need to upgrade them, please email

  1. Point your browser to
  2. Click on 'Login'
  1. Enter your login info. If you've forgotten your information you can request it via this screen.
  1. Copy your keys from your browser then paste them to the appropriate place for your product (see How Do I Update My License Keys? below).

Keys are listed in two sections: version 9.x and higher and version 8.x and lower.

When Must I Update My License Keys?

When you purchase a maintenance agreement in conjunction with your Windward Studios product license, you are entitled to install all Support Releases for your version and earlier versions of the software, as long as your maintenance contract is current. 

As a general rule, the license key you are assigned will work with the current version of a Windward Studios product; will also work for previous versions; but will not work for subsequent releases. However, if your maintenance contract is up to date, you simply retrieve a new license from the Windward store (see How Do I Retrieve My License Keys?).

If you have upgraded any of your Windward Studios products (a Report Designer or a Report Engine), you may receive a license error similar to this:

"This license is only valid up to version 15.*.*"

If you see this error, your keys are only valid up to the version current at the time you downloaded them (in this case version 15). To fix this, login to the Windward Store and retrieve your current license keys.

When we make any changes to your current keys, such as changing the length or date of your maintenance contract; adding new products; or changing license restrictions (e.g. extending a Report Engine license from two to four cores); you must go to the Store to download your updated keys.

How Do I Update My License Keys?

How to update your license keys varies depends upon the Windward Studios product you're licensing.

Licensing for Report Designer Office Edition

For the Report Designer, to see the key you have installed, open MS Word, Excel, or PowerPoint. In the ribbon, click the AutoTag Manager tab and click the License button. (You may see a prompt asking if you want to allow the program to make changes to your device - just click 'OK'.) A window will appear with your license key.  

Important License Information

  • You must have a separate license for each system where a Windward Studios product is installed and executed.
  • You don't need a client license for machines running a browser used to view generated output, only for the machine the output was generated.
  • One license per machine is required.
  • You must purchase support and upgrades for either all licenses or none.
  • The "Standard Server" license runs an unlimited number of reports daily. A single license for a server allows it to be run on one machine only. It is not a license to install the product on an unlimited number of machines.
  • Where the WindwardReports.jar or WindwardReports.dll file is located is irrelevant— a license is needed for each machine where a Windward Studios product is installed and executed.
  • You do not need a separate license for a cold backup system as long as the cold backup system has the same IP address as the hot server.
  • Your Report Engine version should always be equal to or newer than the version of the Report Designer you're using. This is because newer versions of Report Designer may use newer features that older versions of the Report Engine don't recognize.

License Key Tips

Here are some tips on using Windward Studios licenses:

  • When changing a key in a Report Engine, you must restart the application or service embedding that Report Engine for the new license key to take effect.
  • In the Java Report Engine's file, you can enter a multi-line key but you need a "\" (backslash) at the end of every line except the last line.
  • In the .NET Report Engine's <app>.exe.config file, ensure the entire key is in double quotes, e.g. "BDjfsrtf".

Internal Communication Protocols and Ports

The Windward Studios licensing mechanism communicates using both TCP and UDP network protocols on the ICANN-registered port 1707

During the Report.Init() process the license key file is read and the following license key properties are broadcast:

  • license key number
  • total number of machines on which the key is valid to run 
  • total number of threads or cores per machine for which the license key is valid

 A running total is kept of the following values, each of which are updated when a broadcast is received on a system where a Windward Studios product is running:

  • current total number of machines on which the license key is used
  • current number of threads or cores allocated for the reporting process on each machine where the license key is used

 For additional details about how these requests operate refer to the License Copy Protection section below.

License Copy Protection

This section contains detailed information about running Windward Studios products on multiple workstations or servers. It is provided to help the system administrator and third-party developers understand how Windward Studios licensing works.

All editions of the Report Designer and Report Engines have a copy protection mechanism that checks for license violations. The licensing mechanism in each product works the same but are independent of each other. In other words, the Report Designer checks for Report Designer license violations, but does not check Report Engine license violations. The Java Report Engine checks Java Report Engine license violations but does not check for .NET Report Engine, etc.

In each case, when the product starts, it asks all other systems running using the same license to identify themselves. Each system that is already running will respond to that request, identifying itself.

A license specifies the number of machines for which the license is valid. If that number of machines responds to the Report Engine that just started, then the license is in full use and the Report Engine just starting will fail with a license exception and not generate output. A license exception will not be thrown by any of the existing running Report Engines.

The Report Designer starts when Office (Word, Excel or PowerPoint) starts. It ends when all copies of Office on a user’s workstation exit.

A Report Engine starts when ProcessReport.init() is called or the first time output is generated. It ends when the JVM or CLR which called it exits. So if ProcessReport.init() is called and no output is generated for two weeks, but the VM is still running, that system is still using the license and will be counted against that license. If ProcessReport.Init() is not called and the first output is generated two weeks after the Report Engine starts, that is when the Report Engine will determine if it complies with its license restrictions for its server.

One license is good for a single VM running under a single set of credentials. If you have two VMs on a single physical machine, they require two licenses. If on a single VM you run two applications embedding a Report Engine under two sets of credentials, they require two licenses. 

The licensing mechanism is designed so licenses can move between machines. Keep in mind that if you want to stop using a license on a specific server, you must stop all VMs on that server that called a Report Engine.

Each license has a unique ID. Two systems have the same license if and only if they have the same ID and the same restrictions such as product, number of reports, etc. If you purchased three server licenses, and then later two server licenses, you probably have two different licenses and each will have a different ID and will only check for use of itself. In this case, if you would prefer a single license good for five servers (or any number of valid licenses), contact us and we can swap those licenses for a single license good for your five servers.

If a Report Engine running within a VM fails with a license exception, it will continue to do so on subsequent calls even if other Report Engines have decremented the machine count by exiting. The VM must be restarted for the Report Engine running within it to try again.

The license exception is a runtime exception and therefore does not require there be try/catch blocks for it. This decision was made because a license exception will only be thrown when the Report Engine starts, and if there is a license problem, it will always be thrown. There are a large number of methods that can throw this exception, so it would have required additional try/catch blocks around almost all calls to Report Engine APIs. While your program does not require try/catch blocks for license exceptions, you may implement them if you wish.

The class (in the Java Report Engine Utilities jar) will list all machines running the Report Engine by IP address. In the Report Designer the About box lists the IP addresses of all machines running Report Designer. The utility finds all systems regardless of license ID and settings and only reports IP address and host name.


Add your comment

E-Mail me when someone replies to this comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.