It's all about the answers!

Ask a question

License error when installing Rational Publishing Engine 2.1


Jorge Alarcon (411122) | asked Jun 27 '16, 9:23 p.m.
Hi
I am getting the following error when trying to test my new RPE 2.1.0 installation:

Error 400: RPENG license checkout failed. Error is: java.net.ConnectException: Connection timed out: connect

I've make sure that
TELELOGIC_LICENSE_FILE enviroment variable is on the OS with value 27000@<server>.

Can you please advice?

Regards

3 answers



permanent link
Sunil Shenoy U (362) | answered Jul 06 '16, 2:11 a.m.
JAZZ DEVELOPER
Hi Jorge,
Could you share the environment details on which you are trying to set up RPE.

I assume you are trying to setup RPE 2.1 on RHEL with WAS ND as the Application Server +DB2? ( based on the other recent query w.r.t RPE 2.1  on Jazz.net )

My suggestion would be
- Create a TELELOGIC_LICENSE_FILE env variable in Websphere Application Server( incase it doesn't consider the system env variable) under Application Server->server1(Profile_Name)>Process Definition-> Environment Entries and restart the WAS Server.
E.g
TELELOGIC_LICENSE_FILE=port@server_host

-Check the License server details under $HOME/.flexlmrc in and make sure that the value of TELELOGIC_LICENSE_FILE is pointing to the valid license server.

Regards
Sunil Shenoy

permanent link
Subramanya Prasad Pilar (4.6k16) | answered Jun 28 '16, 2:24 a.m.
Please restart browser and access http://server:port/rpeng again. Also, make sure DGAAS_URL property is set (to http://server:port/dgaas) in Administer -> Runtime Variables.
BASE_URL should be http://server:port/rpeng.

Comments
Jorge Alarcon commented Jun 30 '16, 10:13 p.m.

Already did that and I'm still getting the same


permanent link
Jorge Alarcon (411122) | answered Jul 06 '16, 2:23 p.m.
The problem was actually on the License Key Server, I had other licenses on that server and somehow it was messing up with the ones for RPE

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.