I just wanted to use my statements to create incentives for troubleshooting.
I don't own the Kepware server myself, but rather the weaker version of the OPC aggregator.
That means I can't give you exact locations, only possible directions.
Regarding authorization,
the Kepware server reads the machine at some point, so it has to connect to it, a user may be stored here for the connection, the question here is whether he is authorized to read out exactly this data. From my experience, even without reading rights, you can initially see and set up the tags of the data but cannot access the content if the rights are missing, which can lead to these errors.
The thing with the server times:
A time will expire on the machine and a time will also expire on your thingworx server. The question could be whether these are drifting very far apart. I could then imagine that thingworx could then assume that no new signals might come here if they are "older" on the server.
Reinitialize the connection:
When I go to the "Kepware" server in the menu under runtime - connect, disconnect, reinitialize
And that's what I mean by simply re-establishing the connection. When creating in Thingworx, it can happen that when saving, a small connection error occurs that can be quickly remedied.
