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
neeraj_chauhan Absent Member.
Absent Member.
3020 views

Borland Enterprise Server License error[1005] in Visibroker 8.5

Hello there,

I am new to Visibroker.

I am developing an application that was using Visibroker 8.0 earlier and was working fine with it.

We used to provide Visibroker settings using following arguments to our application:

-Dborland.enterprise.licenseDir=C:\Borland\VisiBroker\var -Dborland.enterprise.licenseDefaultDir=C:\Borland\VisiBroker\license -Dvbroker.orb.admDir=C:\Borland\VisiBroker\var\vbroker\adm

Recently, we have started using Visibroker 8.5.

And unfortunately, following error has started coming at the launch of the application:

Unable to locate or read license [Borland Enterprise Server License error[1005]: License setting is not valid, can not find license in your installation. Please obtain a valid license and/or configure appropriately.]

Does anybody has any idea, as what we are missing here?

Thanks in advance.

neeraj

0 Likes
1 Reply
Highlighted
IngoBrettel Absent Member.
Absent Member.

RE: Borland Enterprise Server License error[1005] in Visibroker 8.5

Hello Neeraj,

Did you convert your VisiBroker license, or did you use the VisiBroker 8.0 license key to register the produce?

If you did not convert the license, that is the reason.

Please call the support hotline, they can assist you with the key conversion:

www.microfocus.com/.../assistance.aspx

You can check the installed license with the lmadm tool.

- Open a console prompt

- run "lmadm -i console" in C:\Borland\VisiBroker\bin

- select option 2 to list the installed licenses

The output should be similar to "VisiBroker 8.5 FULL PROD - Enable", followed by details about the installed key.

If the license is ok, you can verify your application settings.

Try to run the Server of the bank_agent example first.

- located in /examples/vbroker/basic/bank_agent

- compile with "nmake -f Makefile_java"

- start an osagent "osagent"

- start the server "vbj Server"

- There should be a message that the server was started

If that works, you can check the settings the vbj starter makes and compare with your application settings

- run "vbj -debug"

If the problem is more complicated, please open a support incident and we will be in contact with you to solve it.

0 Likes
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.