Ah, for Linux (and Mac) I HIGHLY recommend doing a user install rather than
an admin install because making sure that IM is started as root to
correctly apply licenses and stuff can be inconvenient. Failure to run IM
as root can lead to permissions issues in the IM repository that will cause
licensing problems
So in your case I would suggest removing RDI (and anything else) using IM
then uninstall IM itself
To re-install go into ...\disk1\InstallerImage_linux_gtk_x86_64 and run the
userinst script (or similar for the stand-alone IM installer). This
should result in a "My IBM Installation Manager" that you will used to
apply licenses and manage your installs that is run just by your userid and
does not require elevation (being run by root) to administer licenses, etc.
Hopefully this makes some sense to you.
Mike
Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 2018/07/05 09:21
Subject: Re: [WDSCI-L] com.ibm.LUMClient.LumCoreClient (initialization
failure)
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
This is on linux, so some of your instructions are N/A.
I'm reasonably certain i had the base 9.6 licensed.
IM didn't create a shortcut to a licensing wizard, all i have are IM and
an uninstaller. If you know the executable, i can try running it directly.
I exported the problem analysis data and will submit it to my existing PMR.
Thank you
________________________________________
From: Mike Hockings [hockings@xxxxxxxxxx]
Sent: Thursday, July 5, 2018 6:07 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries
Subject: Re: [WDSCI-L] com.ibm.LUMClient.LumCoreClient (initialization
failure)
Hi Justin,
Has this RDI install been licensed before? If not then try applying your
activation kit to it.
If it was previously licensed then it would appear that the IM registry has
been damaged so what I would suggest then is to uninstall all package
groups using that version of RDI then re-install it and re-license it.
License using IM started from the Start menu NOT from the licensing button
that appears in the product. You can run into this kind of problem if you
have the Windows UAC turned down so that programs that should run elevated
are allowed to run without elevation (such as IM started from within RDI
for licensing).
Should you see the same message when starting IM's Manage Licensing wizard
then you will likely need to uninstall all the package groups with IM then
use Windows to uninstall IM, then delete the IM data and re-install from
the start (using Run-As-Administrator to initiate the install)
If you open a PMR then what I would want to see is the IM diagnostic data
(menu: Help > Export Data for Problem Analysis).
Mike
Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 2018/06/29 23:15
Subject: [WDSCI-L] com.ibm.LUMClient.LumCoreClient (initialization
failure)
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
I'm getting this error dialogue on virtually everything I try to do:
An internal error occurred during: "&1".
com.ibm.LUMClient.LumCoreClient (initialization failure)
My main workspace would let me connect, but I got the error when it tried
to reload my last source member list. I tried a Verify Connection, and I
got the same error again. The exact location specified in the error
changes, but the message itself is the same. I cleared my cache and tried
a -clean startup, but the error persisted. I created a new workspace, and
now I'm getting this error on Connect.
This is on my laptop RDi, which I don't use all the time. I know it hasn't
worked since the last update, but I can't say the last working version.
Any suggestions?
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l
.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l
.
midrange.com
