About the log error Thing[xxxx] is not running

[pliu1]

The platform log shows that Thing[xxxx] is not running. In this case, all services in this thing cannot be executed successfully. If any service log in this thin thin is executed, this error will be reported. Maybe it will recover on its own after a while, or maybe it will have to be done by restarting Thingworx. Can't find the reason? Is it possible that the service takes too long to execute or is called too frequently as an interface, leading to the exhaustion of memory resources, has anyone else encountered similar problems, and further in-depth analysis to reach a conclusion and solution ?

[Rocko]

If it's not running, it's because it can't be initialized or started. Check out the Error.log on disk (not ScriptErrorLog)

Could be a misconfiguration in the Config table, missing drivers, or any other exception thrown in the things init phase.

[pliu1]

The thing works normally, only suddenly not after a while
running, not from the beginning, you or err.log specifically refers to the error log in what location and path

[Surya_Tiwari]

Hi, @pliu1   can you share your application, and error logs here?

[pliu1]

由于某种原因，粘贴显示日志不方便

[Surya_Tiwari]

Hi @pliu1  Attached the logs in the drag-and-drop file attachment.

[Rocko]

ErrorLog.txt and ScriptErrorLog.txt in ThingworxStorage/logs directory where you installed Thingworx.

You can also enable Stack Tracing and Script Stack Tracing in Subsystems>LoggingSubsystem.