In UbuntuEclipse, startingInstallationManager: InvalidConfigurationLocation appears.

In UbuntuEclipse, startingInstallationManager: InvalidConfigurationLocation occurs: a foreigner has an article dedicated to the reasons. In fact, in linux, common users cannot modify the file Problem (Abstract) IBMInstallationManagerisinstalledinnon created by the root account.

Ubuntu Eclipse may encounter starting Installation Manager: Invalid Configuration Location:

A foreigner has an article dedicated to the reasons. In fact, common users in linux cannot modify the files created by the root account.

Problem (Abstract)

IBM Installation Manager is installed in nonadministrator mode. A super-user tries to start Installation Manager. Installation Manager is disabled and cannot be started by the nonadministrator user.

Symptom

A super-user starts an instance of Installation Manager that was installed by a nonadministrator user. Installation Manager fails with the errors:

CRIMCEB884626E ERROR: The Installation Manager cannot be started. The registry information does not exist or does not match with this executable. This may happen if you are trying to run Installation Manager installed by another user.

00:03.02 ERROR [main] com.ibm.cic.agent.internal.application.
HeadlessApplication run

The Installation Manager cannot be started. The registry information does not exist or does not match with this executable. This may happen if you are trying to run Installation Manager installed by another user.

When the nonadministrator user starts Installation Manager, the following errors occur:

Invalid Configuration Location:

Locking is not possible in the directory "/InstallationManager/bin/eclipse/configuration/org.eclipse.osgi". A common reason is that the file system or Runtime Environment does not support file locking for that location. Please choose a different location, or disable file locking passing "-Dosgi.locking=none" as a VM argument.

/InstallationManager/bin/eclipse/configuration
/org.eclipse.osgi/.manager/.file TableLock (EDC5111I Permission denied.)

 

Cause

When a super-user starts Installation Manager, the ownership of the following subdirectories in/InstallationManager/bin/eclipse/configuration/Directory are changed to the super-user:

org.eclipse.core.runtime

org.eclipse.equinox.app
org.eclipse.osg

'

As a result, the nonadministrator user cannot write files in these directories.

 

Resolving the problem

To resolve this issue:

1. Login as a super-user.

2. Run the command:cd /InstallationManager/bin
/eclipse/configuration

3. Change the ownership of the following directories to the nonadministrator user.

A. If Installation Manager is installed in nonadministrator mode, run the command:
chown -Rh imadmin org.eclipse.core.runtime org.
eclipse.equinox.app org.eclipse.osgi

B. If Installation Manager is installed in group mode, run the command:
chown -RH imadmin:imgroup org.eclipse.core.
runtime org.eclipse.equinox.app org.eclipse.osgi

4. Delete/tmp/ciclogs_superadmiDirectory.

5. Login as the nonadministrator user.

6. Start Installation Manager.

However, I did what he said, but it still didn't work.

In the end, there are two ways to solve this problem.

1. Use the su command to switch to the root account, and then run./eclipse

2. Use chmod 777 ***/workspace-R and all the folders in the workspace.