Skip to main content
A
AntonioFar12-Amethyst
12-Amethyst
November 21, 2023
Solved

Search Form don't show anything (Group, Project, Users) in Composer

  • November 21, 2023
  • 1 reply
  • 1510 views

Hello everyone, today I came across this strange error. When I try to search a Form for a Project, Group or User, I can't display the entities on my Thingworx server.
I can't understand why, has this ever happened to you?

Best answer by AntonioFar

I solved it by deleting the webapps folder in Tomcat 9.0. Restarting the server automatically regenerates the folder, which solves the problem. The problem was related to a corrupt file in the webapps folder, the post api services were already working correctly before restarting the server and restoring the files.

1 reply

A
AntonioFar12-AmethystAuthor
12-Amethyst
November 21, 2023

When I click on the + button, this error appears in the browser console:

 

Unhandled rejection e@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:22066:26 c</e.prototype.compileAndAttach@https://**************/Thingworx/Composer/scripts/thingworx-ui-bundle-8.4.9-1582125740.js:1:31547 B</e.prototype._openMainPopover/<@https://**************/Thingworx/Composer/scripts/thingworx-ui-bundle-8.4.9-1582125740.js:16:24308 r@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9903:54 [15]</t.exports/i.prototype._settlePromiseFromHandler@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9395:220 [15]</t.exports/i.prototype._settlePromise@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9427:83 [15]</t.exports/i.prototype._settlePromise0@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9446:97 [15]</t.exports/i.prototype._settlePromises@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9492:50 [15]</t.exports/i.prototype._fulfill@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9459:143 [16]</t.exports/s.prototype._resolve@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9612:74 [16]</t.exports/s.prototype._promiseFulfilled@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9623:71 [15]</t.exports/i.prototype._settlePromise@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9430:88 [15]</t.exports/i.prototype._settlePromise0@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9446:97 [15]</t.exports/i.prototype._settlePromises@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:9492:50 [1]</r.prototype._drainQueue@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:7981:46 [1]</r.prototype._drainQueues@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:7985:38 r/this.drainQueues@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:7884:35 a@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:5056:98 M/<@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:5066:38 u@https://**************/Thingworx/Composer/scripts/vendor-bundle-8.4.9-1582125740.js:2209:37


Could not load content for https://**************************/Thingworx/Composer/node_modules/bootstrap/js/src/index.js (HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE)

Rocko
Rocko19-Tanzanite
19-Tanzanite
November 24, 2023

This looks to me like server down, server disk full, incomplete restore or similar. Other than that and restarting the server and session, I would advise to contact support.

A
AntonioFar12-AmethystAuthorAnswer
12-Amethyst
December 13, 2023

I solved it by deleting the webapps folder in Tomcat 9.0. Restarting the server automatically regenerates the folder, which solves the problem. The problem was related to a corrupt file in the webapps folder, the post api services were already working correctly before restarting the server and restoring the files.

Terms & ConditionsAccessibility statement