cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

Encountered an error retrieving a Thing in Composer

pascal_kardex
1-Visitor

Encountered an error retrieving a Thing in Composer

Dear all. We constantly receive the error "encountered an error retrieving <Thing>" when opening the composer when the server runs for a certain amount of time. Restarting the Tomcat and recreating the thing helps. However we are productive now and cannot restart the server every 48 hours. What should be done?

On the Frontend of Utilities when a Thing shows this behavior, we cannot change the properties, e.g. we cannot change the alerts.

There is nothing concrete in the application log. The Error is empty.

Help Appreciated.

4 REPLIES 4

Hello, Pascal.

You might be encountering a 'ghost entity' in ThingWorx. The below article describes how these are created, how they can be detected, and possibly prevented.

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS198580

Check that out and see if it is helpful with this.

-- Craig A.

Hi Pascal Waldvogel​,

Are these Things created by some Code or manually from Composer? If it created by code/service; it could be an issue of Ghost entities as suggested by Craig.

Hi Ankit Gupta​, they are created manually. It must be from the services as we added quite the complex ones.

What I don't understand, why is Thingworx not globally including a fallback that this shouldn't happen? Why are WE responsible to make sure that ghost entities are not created?

Is there anything done about this?

There is absolutely NO way of telling which service is making this - as there is NO log

An Advice?

visla
14-Alexandrite
(To:pascal_kardex)

Customer confirmed this was not related to Ghost Entities (they don't create Entities programmatically and "Ghost Entities Cleaner" was not finding any Ghost Entity when issue was occurring).

They solved the issue on their own and this community thread can be closed.

Announcements


Top Tags