An internal error occurred during: "Tools Activation Job". Cannot invoke (IEP-1541)

[Phypom]

An internal error occurred during: "Tools Activation Job".
Cannot invoke "org.eclipse.cdt.lsp.config.Configuration.qualifier()" because "this.configuration" is null

Using the IDE version 3.3.0 works normally, but after updating to 3.4.0, IDF cannot be installed properly (for any version). The warning seems to be that the tools report an exception, and there is no relevant solution found.

[github-actions]

Hi @Phypom! This is an automated response.
If you don’t find the answer helpful, please check the ESP32 IDE forum (https://www.esp32.com/viewforum.php?f=40) or GitHub issues (https://github.com/espressif/idf-eclipse-plugin/issues) to see if the issue has already been discussed.

---

The error you are encountering after upgrading from Espressif-IDE 3.3.0 to 3.4.0 appears to be related to missing or incompatible dependencies during the update process. According to the Espressif-IDE documentation, if the next version of the plugin requires updated dependencies (for example, a change in the minimum CDT version), you must ensure these dependencies are updated during installation from the update site. If dependencies are not updated, you may see errors similar to what you described.

Recommended Solution:

1. When the installer displays an error, click Show original error and build my own solution.
2. Select both:
   • Update items already installed
   • Remove items already installed

This process will allow the installer to update or replace any conflicting components and should resolve the issue with tool activation and configuration after upgrading to 3.4.0. For more details, refer to the official Update Site Installation Guide.

If the problem persists after following these steps, please check the Error Log in the IDE via Window > Show View > Error Log for more details, as suggested in the troubleshooting section.

[kolipakakondal]

Hello, Could you please provide the error log to troubleshoot further ?
https://docs.espressif.com/projects/espressif-ide/en/latest/troubleshooting.html#error-log

[sigmaaa]

Hi @Phypom,

It looks like a required dependency is missing, and Eclipse is unable to retrieve the service for the ClangdConfiguration API. Was the installation process smooth? Did you follow the official upgrade guide during the update?
Upgrading from Espressif IDE 3.3.0 to 3.4.0

Could you also share the Product Information log? You can find it by navigating to:
Espressif → Product Information

In the meantime, I recommend checking for any missing updates:
Help → Check for Updates,
then try reinstalling the plugin. Sometimes, dependencies can be skipped during the initial installation.

Let me know how it goes! Thanks

[Phypom]

I downloaded version 3.4.0 from idf-eclipse-plugin and reinstalled IDF. However, the same problem still occurred. Please find the error log attached. I hope to identify the anomaly and help me solve it.

errlog.log

[Phypom]

The latest version has been updated.
It's not certain if it's an issue with the environment variables, but the environment variables have always been automatically configured by IDF.

[sigmaaa]

Have you encountered the same issue on a fresh installation of Espressif IDE 3.4 (not an upgrade from 3.3)?
https://dl.espressif.com/dl/idf-eclipse-plugin/ide/Espressif-IDE-3.4.0-win32.win32.x86_64.zip

[sigmaaa]

Hi @Phypom,

One more thing worth checking from the log: in the PATH environment variable, there's an entry like:

";C:\Program Files\Java\jdk1.8.0_144\jre\bin";
This entry contains double quotes ("), which are not valid in file paths. These quotes are causing the exception:
java.nio.file.InvalidPathException: Illegal char <"> at index 0: "

This could be affecting the installation manager as well. I recommend checking your system PATH environment variable and removing any leading or trailing quotes from paths.

Let me know if that helps!

[Phypom]

https://dl.espressif.com/dl/idf-eclipse-plugin/ide/Espressif-IDE-3.4.0-win32.win32.x86_64.zip
the current test is directly from the 3.4.0 zip file after decompression. I have tried many versions. I installed and upgraded to version 3.4.0 on 5.3.1 IDF and 3.1.0 IDE offline, and I encountered the same problem.

[Phypom]

The environment variables should be normal. There should be no extra quotes or semicolons in the JAVA_HOME configuration.

[sigmaaa]

The environment variables should be normal. There should be no extra quotes or semicolons in the JAVA_HOME configuration.

From the logs, I can see that two entries for JDK 1.8.0 appear in your PATH variable. One looks normal, likely coming from the JAVA_HOME variable, but the other appears to be corrupted:
C:\Program Files\Java\jdk1.8.0_144\bin;";C:\Program Files\Java\jdk1.8.0_144\jre\bin"

Could you please click on "Edit text" for the system Path variable and check the entries there? The edit text window on path variable should look like this:

[Phypom]

The environment variables should be normal. There should be no extra quotes or semicolons in the JAVA_HOME configuration.环境变量应该是正常的。JAVA_HOME 配置中不应有额外的引号或分号。

From the logs, I can see that two entries for JDK 1.8.0 appear in your PATH variable. One looks normal, likely coming from the JAVA_HOME variable, but the other appears to be corrupted:从日志中，我可以看到 JDK 1.8.0 的两个条目出现在您的 PATH 变量中。一个看起来很正常，可能来自 JAVA_HOME 变量，但另一个似乎已损坏： C:\Program Files\Java\jdk1.8.0_144\bin;";C:\Program Files\Java\jdk1.8.0_144\jre\bin"C：\Program Files\Java\jdk1.8.0_144\bin;“;C：\Program Files\Java\jdk1.8.0_144\jre\bin”

Could you please click on "Edit text" for the system Path variable and check the entries there? The edit text window on path variable should look like this:您能否单击系统 Path 变量的“Edit text”并检查其中的条目？path 变量上的编辑文本窗口应如下所示：

Yes, I discovered a minor issue. I attempted to make a change to see if it resolves the JDK problem.This semicolon is used to distinguish the path of jre. Maybe it's not necessary.

[sigmaaa]

This semicolon is used to distinguish the path of jre. Maybe it's not necessary.

Since the JDK (bin) contains all the tools required for compiling and running Java applications, referencing the JRE separately in the environment variables is unnecessary.