Article - CS332199
"Entity <ID> does not exist or is not yet associated with a Thing” is seen in the Integration Runtime log when connecting Integration Runtime with ThingWorx Platform/ThingWorx Navigate
Modified: 16-Jan-2025
Applies To
- Windchill Navigate (formerly ThingWorx Navigate) 1.9.0 F000 to 9.5
- ThingWorx Platform 8.0 to 9.5
Description
- Navigate IntegrationRuntime log error Entity <ID> does not exist or is not yet associated with a Thing
- ThingWorx and Kepware connection failed and reported Engity<ID> does not exist or is not yet associated with a Thing in Kepware Event Log
- Entity <ID> does not exist or is not yet associated with a Thing is seen in the IntegrationRuntime log for ThingWorx Navigate
- Red square on ThingWorx Navigate edit tailoring webpage
- Failing to save Tailoring
- Error in <ThingworxStorage>\logs\AplicationLog.log:
-
[L: ERROR] [O: c.t.s.s.w.p.WSExecutionInstance] [I: ] [U: <User>] [S: ] [P: ] [T: WSExecutionProcessor-21] error executing APIRequest Message: Entity <Entity> does not exist or is not yet associated with a Thing, sending ERROR ResponseMessage to caller! [L: ERROR] [O: c.t.w.p.APIProcessor] [I: ] [U: <User>] [S: ] [P: ] [T: WSExecutionProcessor-22] Unable to dispatch [ uri = /Things/<Entity>/Properties/*/]: Entity <Entity> does not exist or is not yet associated with a Thing [L: ERROR] [O: c.t.s.s.w.p.WSExecutionInstance] [I: ] [U: <User>] [S: ] [P: ] [T: WSExecutionProcessor-22] error executing APIRequest Message: Entity <Entity> does not exist or is not yet associated with a Thing, sending ERROR ResponseMessage to caller! [L: ERROR] [O: c.t.s.s.e.QueuedEvents] [I: ] [U: SuperUser] [S: ] [P: ] [T: https-jsse-nio-8443-exec-3] Failed to dispatch event. Invalid Thing In Event Type.Thing:Entity.<Entity>:Event.DataChange:Property.isConnected:<Entity> [L: ERROR] [O: c.t.s.s.e.QueuedEvents] [I: ] [U: SuperUser] [S: ] [P: ] [T: https-jsse-nio-8443-exec-3] Failed to dispatch event. Invalid Thing In Event Type.Thing:Entity.<Entity>:Event.AnyDataChange:<Entity> [L: WARN] [O: c.t.c.s.c.j.Jsr356ServerConnection] [I: ] [U: SuperUser] [S: ] [P: ] [T: https-jsse-nio-8443-exec-3] Server WebSocket closed unexpectedly, unregistering from Server Endpoint [ws session id: 1, endpoint id: 2, endpoint name: <Entity>] null
-
- One of the following sets of errors in IntegrationRuntime.log:
-
[vert.x-worker-thread-2] ERROR c.t.i.ThingworxEdgeVerticle - Error Setting Runtime Status com.thingworx.common.exceptions.GenericHTTPException: Entity <Entity> does not exist or is not yet associated with a Thing at com.thingworx.communications.client.BaseClient.writeProperties(BaseClient.java:537) -
[vert.x-worker-thread-1] ERROR c.t.i.ThingworxEdgeVerticle - Error registering routes com.thingworx.common.exceptions.GenericHTTPException: Unable to dispatch [ uri = /Subsystems/IntegrationSubsystem/Services/CollectConnectorRoutes/]: Entity IntegrationSubsystem does not exist or is not yet associated with a Thing at com.thingworx.communications.client.BaseClient.invokeService(BaseClient.java:422) at com.thingworx.communications.client.BaseClient.invokeService(BaseClient.java:372) at com.twx.integration.ThingworxEdgeVerticle.configureConnectorRoutes(ThingworxEdgeVerticle.java:58) ... ... [Timer-0] ERROR c.t.i.u.RemoteServiceUtils - Error while invoking Health Check on Thingworx com.thingworx.common.exceptions.GenericHTTPException: Unable to dispatch [ uri = /Subsystems/IntegrationSubsystem/Services/IsLocalRunning/]: Entity IntegrationSubsystem does not exist or is not yet associated with a Thing at com.thingworx.communications.client.BaseClient.invokeService(BaseClient.java:422) at com.thingworx.communications.client.BaseClient.invokeService(BaseClient.java:372) at com.twx.integration.client.things.IntegrationRuntimeServer.invokeService(IntegrationRuntimeServer.java:101) ...
-
- Seeing many Things related to Integration Connectors and Integration Runtime show up as Unassigned in ThingWorx Platform
- Unexpected Entities related to Integration Connectors show up in Composer with a Question Mark icon:
- Remote thing is connected with SDK, however, property sync is not updated
- Attempting to tailor an app shows a red square error
- Unable to edit or save during tailoring
This is a printer-friendly version of Article 332199 and may be out of date. For the latest version click CS332199