Why is a plugin or dropin not loading?
You need to obtain debug information on the plugins and dropins so you can investigate the cause of the failure.
Description
One or more plugins or dropins are not loading. You might be missing some library dependencies or some platform conditions are not being met.
Solution
Run IXIA CCMS Desktop in debug mode with an ".options
" file to produce the debug.txt file which contains special
debug information on each loaded plugin or dropin.
To obtain the debug.txt:
- Create a text file containing the following content:
org.eclipse.equinox.p2.core/debug=true org.eclipse.equinox.p2.core/reconciler=true org.eclipse.equinox.p2.director/debug=true org.eclipse.equinox.p2.engine/debug=true
- Save the file as .options in the same
folder as the eclipse.ini file IXIA CCMS Desktop. For example, the file can be saved as .options in C:\eclipses\eclipse-Prod42. Note: To rename the file .options, you can open a command prompt and run the rename command in the folder where you created the file; for example,
C:\eclipses\eclipse-Prod42>ren foo.txt .options
, which will rename foo.txt to .options. - Right-click the IXIA CCMS Desktop shortcut.
- Click Properties.
- Click the Shortcut tab.
- Copy the contents of the Target box so you can revert to it easily later.
- In the Target box, change the target as follows:
- Change eclipse.exe for eclipsec.exe.
- Add these parameters to the end of the line:
-clean -console -consoleLog -debug
- Add the following at the end of the line after the parameters:
>debug.txt 2>&1
. For example:C:\eclipses\eclipse-Prod42\eclipsec.exe -clean -console -consoleLog -debug >debug.txt 2>&1
- Click OK.
- Double-click the shortcut to launch the Eclipse Client.
- Review the debug.txt.
- When you no longer need debug mode, revert the contents of the Target box to the original target.