Skip to main content
P
PG_CG8-Gravel
8-Gravel
May 22, 2025
Question

Removing Custom Extension

  • May 22, 2025
  • 3 replies
  • 520 views

We had accidently built custom extension using java 17 whereas the environment was on java 11. Upon importing this extesnion on ThingWorx the environment was not coming up and below error was observed in tomcat logs:

 java.lang.UnsupportedClassVersionError: com/thingworx/extensions/sshExtension/SshServerThing has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0.

 

Removed the extension entry from postgresDB by deleting the corresponding entries from table extensions, extensionpackage_model and model_index after this the environment became accessible. Also, the entry was deleted from thingpackage_model and widgel_model.

Post that also when we are trying to import the correctly build extension its giving below error:

Unable to delete Extension zip file from storage. This is likely due to other errors: [1,018] Data store unknown error: [Error occurred while accessing the model provider.]

 

Anyone has any idea on this how to fix this error so as import the correct extension.

3 replies

Rocko
Rocko19-Tanzanite
19-Tanzanite
May 23, 2025

Hard to say, as you have worked directly on the tables you could be in an undefined state. Probably worth a support ticket.

 

Some things to check:

-Database logs and Error log, they could tell you on which object the issue is. Maybe enable stack tracing for this and/or SQL logging

-Extensions are also stored in the ThingworxPlatform file system. make sure it is removed there as well or it might get redeployed on restart

-Try to run the service to remove ghost entities (platform subsystem IIRC) and restart the platform.

 

 

J
Jimwang16-Pearl
16-Pearl
May 26, 2025

 

1> Enable the stack trace by going to Subsystem > LoggingSubsystem> Configuration, and select the option "Enable Stack Tracing"

2> Go to Monitoring > ApplicationLog, set the logger level to Debug under the Configure (Please note: Don't set the debug level in Production system)

3> Re-import the Extension

4> Turn off the Application Debug loglevel

 

Check Application log and Error log, it will give some helpful information. You can upload the two log files here for check also if you can't find the cause.

S
slangleyCommunity Manager
Community Manager
June 5, 2025

Hi @PG_CG 

You have received a couple of responses to this post.  If you have been able to resolve your issue, please mark the appropriate response as the Accepted Solution.  If you are still experiencing issues, please provide further details so we can assist further.

 

Regards.

 

--Sharon

Terms & ConditionsCookie settingsAccessibility statement