Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

License Error Codes

[[wiki:VisiBroker - World class middleware - Wiki|Back]]

VisiBroker requires for most use cases a valid license. For any license related problems an error message with an error code is printed out.

This page gives an overview of common license warning and error codes with links to articles explaining the possible error scenarios and their solutions.

The page is not entirely complete yet. The content will be published in a series of updates over the next weeks.

1000

Janeva License error[1000]: License is not valid or could not be located. Please obtain a valid license and/or configure appropriately

Indicates general problems, such as license is not installed or license location is not correctly configured.

Before investigating further, VisiBroker 8.5 users should ensure that the VisiNet P1 Patch was installed. Without the patch any configuration results in this error. The patch can be obtained through SupportLine.

Details of the license configuration are described in the KB article Janeva License error[1000]: License is not valid or could not be located.

1005

Borland Enterprise Server license error[1005]: License setting is not valid; cannot find license in your installation. Please obtain a valid license and/or configure appropriately.

Generally indicates that the product license was not found which has a number of root causes. A checklist is provided in the KB article Borland Enterprise Server license error[1005]: License setting is not valid.

A reason why the license was not properly installed may be that it was copied to the wrong location, read also Where to save VisiBroker/AppServer license activation file. The error is also seen if VisiBroker 8.5 was registered with a VisiBroker 8.0 license key, more details in Can a VisiBroker 8.0 key be used to register VisiBroker 8.5, and vice versa?.

If the license registration worked and the license either disappears in lmadm directly after the registration, or the error suddenly appears in a working system with no obvious changes some license relevant host properties may have changed, read also VisiBroker license cannot be listed after registration. For shared installations or High-Availability systems with fail-over support the license setup may be more complicated. Further information you can find in the KB articles Steps to setup two licenses using shared installation of VisiBroker and VBE 6.5: License error when failing over to backup server.

1011

Borland Enterprise Server license violation[1011]: Non-compatible licenses are detected. Please use license tool to reconfigure your license.

Two or more licenses which are incompatible with each other were installed. The KB article Borland Enterprise Server license violation[1011]: Non-compatible licenses are detected explains which license types cause the incompatibility.

1017

Borland Enterprise Server license warning[1017]: License is trial or termed, you have only xx days left.

Is seen on systems with a TRIAL or TERM license installed. Details are explained in the Knowledge Base article Borland Enterprise Server license warning[1017]: License is trial or termed

Other related error codes are 1020 ( run-time restriction of TRIAL / TERM ) and 1021 ( replaces 1017 when license expired ).

1019

Borland Enterprise Server License violation[1019]: License directory system property is not set.

The configuration for VisiBroker where to locate the license is missing or incomplete. The different configuration possibilities for both the C++ and Java ORB are explained in the KB article License violation[1019]: License directory system property is not set. If in VisiBroker for Java the license properties are configured in code, it is important to create them as system properties. The correct implementation is described in the KB article Can VBJ license properties be put into a java.util.Properties and pass into org.omg.CORBA.ORB.init()?.

1020

Borland Enterprise Server license violation[1020]: Limited license term exceeded.

Indicates the automatic shutdown of the ORB after 10 or 72 hours ( dependent on VisiBroker version ). Applies to TRIAL, TERM and DEV licenses. Details are explained in the Knowledge Base article Borland Enterprise Server license Violation[1020]: Limited license term exceeded.

Related error codes are 1017 ( valid TRIAL / TERM license ) and 1021 ( expired TRIAL / TERM license ).

1021 

Borland Enterprise Server License violation[1021]: One or more of your trial/termed license(s) have expired. Please use license tool to remove the expired license.

Prevents the ORB to start-up since the TRIAL or TERM license expired. License needs to be replaced by a valid one. Details are explained in the KB article Borland Enterprise Server License violation[1021]: One or more of your trial/termed license(s) have expired.

Related error codes are 1017 and 1020 ( seen before the license expired ).

1022

Borland Enterprise Server License error[1022]: license.ini file is corrupt or invalid. Please contact Tech Support or reinstall the product.

Can be a problem of the ORB configuration, the user has insufficient access rights, or the file is missing or corrupted. Details how to verify and solve the different issues are described in the KB article Borland Enterprise Server License error[1022]: license.ini file is corrupt or invalid.

If access rights cause this license error, check if VisiBroker was installed by the root user. In that case additional issues need to be solved, described in the KB article VisiBroker installation with root account.

1023

Borland Enterprise Server License error[1023]: Sanctuary Initiation Error

A critical error of the license manager, often due to severe problems with the license files or license manager libraries. Some common scenarios and their solutions are explained in the KB article Borland Enterprise Server License error[1023]: Sanctuary Initiation Error.

1024

Borland Enterprise Server License error[1024]: Sanctuary Runtime Error :Internal Error

An unexpected error condition, rarely happens in customer systems. To resolve this problem create a support incident with SupportLine for investigation.

1025

Borland Enterprise Server License error[1025]: Sanctuary Runtime Error :Cannot connect to license server

A concurrent license located on a Belize License Server was installed, and the license server cannot be reached. Steps for diagnosis are described in the KB article Borland Enterprise Server License error[1025]: Sanctuary Runtime Error :Cannot connect to license server.

1031

Borland Enterprise Server license error[1031]: No license found for this product.

Happens usually when a license is installed, but either the license itself or the run-time libraries for the license manager are incompatible with the used product version. How to debug if an incompatible license manager library was linked is explained in the KB article Borland Enterprise Server License error[1031]: No license found for this product. The error scenario when VisiBroker 8.0/8.5 installations and licenses are mixed is explained in the KB article Can a VisiBroker 8.0 key be used to register VisiBroker 8.5, and vice versa?.

If no license at all was installed, error 1005 is seen.

2000

General License Internal error[2000]: License Manager can not support this product id

Only expected in VisiBroker for Java if loaded jar files are not consistently sourced from the same product version. Details are explained in the KB article General License Internal error[2000]: License Manager can not support this product id.

 

[[wiki:VisiBroker - World class middleware - Wiki|Back]]

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-07-29 08:32
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.