Problem with reference class TaCoKitCache

[7map]

I have a problem when opening a project on my studio. 

When opening some (but not all) projects I get the following error : 
Generation Engine Initialization in progress...
"Can't find service reference for class 'org.talend.sdk.component.studio.metadata.TaCoKitCache'"

This error prevents me from opening any jobs on the Talend Studio
The error looks like it's "spreading" as I now have new project that I can't access too 

What I've tried so far : 

Deleting the workspace foder
Reinstal Talend Studio (8.0.1 R2026 - 01)

Any idea ? 

[Greg_Taffer]

This Talend error indicates a corruption in the Component Kit (TaCoKit) cache, often caused by plugin conflicts or incomplete metadata updates during startup. To resolve, close Studio and delete the .metadata folder within your workspace (specifically \workspace\.metadata\.plugins\org.talend.core and \workspace\.metadata\.plugins\org.talend.sdk.component.studio) to force a cache rebuild. 

Key Troubleshooting Steps:

• Clear Component Cache: Navigate to your workspace directory and delete the folder \workspace\.metadata\.plugins\org.talend.sdk.component.studio. Restart Talend Studio to trigger a fresh component scan.
• Clear Metadata Cache: If the above fails, delete the .metadata folder entirely. Note: This will reset your Studio settings (perspectives, connection history), but not your jobs.
• Check for Corrupt Plugins: If the error "spreads," it often indicates a corrupted custom component or a faulty plugin installed in studio/plugins.
• Restart with Clean: Launch Talend Studio using the -clean option in the .ini file to force a refresh of the OSGi bundle cache. 

[7map]

Thanks for the answer I've tried your suggestions. 

I had no \workspace\.metadata\.plugins\org.talend.core  or \workspace\.metadata\.plugins\org.talend.sdk.component.studio folder so I tried to delete the .metadata folder. 

After relauch of the Studio I got the error back when trying to open the job. I then tried the -clean without success. 

I realized that one thing the two corrupted project have in common is a job that I worked on. This job utilise tHTTPClient (a component we didn't used before) but nothing custom.
(I've worked on this job on a first project until it became corrupted then worked on a second project)

Also, here is my .ini file after modification : 
"-clean
-vm
C:\Talend\.Talend_R2025-02\zulu17.48.15-ca-jdk17.0.10-win_x64\bin\javaw.exe
-vmargs
-Xms512m
-Xmx4096m
-Dfile.encoding=UTF-8
-XX:+UseG1GC
-XX:+UseStringDeduplication
-XX:MaxMetaspaceSize=512m
--add-modules=ALL-SYSTEM
-Dosgi.requiredJavaVersion=17
--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.util=ALL-UNNAMED
--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.base/java.util.stream=ALL-UNNAMED
--add-opens=java.base/java.util.regex=ALL-UNNAMED
--add-opens=java.base/java.lang.invoke=ALL-UNNAMED
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens=java.base/java.nio=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--add-opens=java.base/sun.nio.ch=ALL-UNNAMED
--add-opens=java.base/sun.nio.cs=ALL-UNNAMED
--add-opens=java.base/sun.security.action=ALL-UNNAMED
--add-opens=java.base/sun.security.pkcs=ALL-UNNAMED
--add-opens=java.base/sun.security.x509=ALL-UNNAMED
--add-opens=java.base/sun.util.calendar=ALL-UNNAMED
--add-opens=java.security.jgss/sun.security.krb5=ALL-UNNAMED
--add-opens=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED"

[Denis_Segard · Accepted solution]

Hello,

Could you test the following steps :

Stop Talend Studio 

Delete the folder  <STUDIO_FOLDER>\configuration\Talend 

Update the file <STUDIO_FOLDER>\configuration\config.ini in order to have the 2 lines :

org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/bundles.info
eclipse.p2.profile=profile

Start the Studio , in the project selection popup window , click Preferences and be sure the Update URL is set to the version of Talend Studio ( and not latest )

Kind regards

[XRocq1696001865]

Hello,

In order to undersand.

The root cause is because of the update settings set to "latest" version instead of the specific we are using (2026-01) ?

If we patch to 2026-03 which is the latest one, do we need to put "2026-03"  to Don't have this problem again when the future 2026-0X will be available ? 

[durantepj]

Is this the actual solution?  We just upgraded from 2025-01v2 to 2026-02 and we are now getting this same error.
I've tried the above solution but it didn't help.