Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

"Invalid Configuration Location" after installing the tool

[Deleted User]
[Deleted User] Posts: 0 admin
in C/C++test

If the following window appears when a User is trying to launch the Parasoft tool:

Invalid Configuration Location pop up.

This message is reported by the Eclipse platform used by the Parasoft Tool when there are some problems with caching Eclipse internal data in the folder "configuration", usually located under parasoft/test/9.X. There might be a couple reasons for this behavior:

1) Permissions are not set correctly for files under parasoft/test/9.5/configuration
This sometimes happens when the Parasoft Test tool was used on one user's account, and then another user is trying to use the same installation. Eclipse uses its configuration directory also for caching some common data files, so when multiple users try to use the same installation this kind of conflict may occur.

2) Your Linux file system does not support file locking. This does not happen often, but some Linux distributions have this problem.

To resolve this behavior, you can follow one of the following solutions below:

  1. Tell C++test's Eclipse to use per-user configuration area to avoid conflicts (the best solution). To do so, please, go to the folder

...../parasoft/test/9.X/configuration

backup the existing config.ini file (just in case), and then add the following line

osgi.configuration.area=@user.home/.cpptest_configuration

where @user.home will be expanded automatically by Eclipse to $HOME, which means that each user will have his/her own copy of the configuration folder. The next time you start the Parasoft tool through the GUI or CLI, you will see the folder created automatically in the current user's $HOME.

  1. Make the parasoft/test/9.X/configuration folder and its subfolders writable for everyone, and make sure umask setting of all users is not preventing others from writing to the files. E.g. umask of 002 should ensure appropriate group permissions. However, this solution may be too insecure for many organizations.

3) Add the following argument when running the Parasoft tool commands:
-data -J-Dosgi.locking=none
-data -J-Dosgi.locking=none

For example, to launch C/C++test with this:
cpptest -data -J-Dosgi.locking=none
cpptestcli -J-Dosgi.locking=none

  1. Similar to solution 3, apply "-Dosgi.locking=none" in the eclipse.ini file used by the Eclipse that the Parasoft Tool is plugged into.
Tagged:

Categories

Tagged