Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X
In my Thingworx composer, I created an industrial connection, then I tried deleting it but failed. "Unable to dispose thing" always show when I delete it. I then found I can only create but can not delete industrial connection. I used Administrator account. I googled this question but found nothing can help. Hopefully here someone can help.
Solved! Go to Solution.
Hi @eyli.
It appears that the issue was resolved by upgrading to 8.4.9. The issue was not reproducible under the supported releases of 8.5 and 9.x.
If you agree that this was the solution, please mark this response as the Accepted Solution for the benefit of others with the same issue.
Regards.
--Sharon
I just created a industrial connection without other settings. The I tried deleting it and failed with "Unable to dispose thing". May I know how I can know if it is connected or not?
You can check the isConnected property to verify the connection status and also there is connection icon on the left of the thing name as shown below,
I did a quick test, I created a new industrial connection and was able to delete it on 8.5.7 and 9.1.
Regards,
Sachin
It show "Now Active" when I put cursor on the connection icon. I also saw the isConnected property value is 0.
Hi @eyli.
Are you still having a problem deleting it? If so, check the logs located at \ThingworxStorage\logs for clues.
Regards.
--Sharon
Thanks for hint. I didn't see logs related to when I tried the deletion action. I also tried rebooting the computer but it didn't work. What should I do next to troubleshoot?
Hi @eyli.
I think at this point it would be easier to open a case. I will be happy to open one on your behalf with your approval. We will come back to this post to provide the solution once the case has been worked.
Regards.
--Sharon
Hi slangley,
Case 15820236 has been created for this.
Thanks and Regards
Edward
Hi @eyli.
It appears that the issue was resolved by upgrading to 8.4.9. The issue was not reproducible under the supported releases of 8.5 and 9.x.
If you agree that this was the solution, please mark this response as the Accepted Solution for the benefit of others with the same issue.
Regards.
--Sharon
I did it manually.