Thingworx File Transfer Error: <myfile> not found in open files list
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thingworx File Transfer Error: <myfile> not found in open files list
I am trying to transfer some log files from a remoteThingWithFileTransfer to a FileRepository with the tw file manager. It appears that I can transfer the data correctly, but the logs report the following error:
[ERROR] 2020-02-17 14:28:18,163 SDK: twFileManager_FinishFileTransfer: File: myLog.log not found in open files list
Have I misconfigured the FileRepository thing? Again, I can see the updated logs through the Thingworx composer and I get a VALIDATED file transfer notification so this error seems strange. I would be happy to send the complete logs in a PM if that will help.
Thanks,
Connor
Solved! Go to Solution.
- Labels:
-
Troubleshooting
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
We were able to fix this issue by changing "msg_timeout" to 30000 in the ws_connection section of config.json (default is 10000).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello Connor,
Based on your comments you are getting this message even when the File Transfer to the Platform completes successfully. To confirm you are able to open the file and access it from within the Repository? Does this happen for every transfer to this Repository?
Perhaps some additional error stack logging will help us out here. You can enable this by navigating to LoggingSubsystem > Configuration > Enable stack tracing. With this on please reproduce and provide the ErrorLog.log and ApplicationLog.log file from ThingworxStorage.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Yes I can open the files on the repository and also yes each file reports this error one time each.
I sent you the logs in a private message.
Thanks again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello Connor,
I am in reception of the logs and will review. Depending on my findings it may be best to open a case via the PTC Support Portal to diagnose further. I will let you know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thanks, I opened a case #15295379
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thanks Connor.
I have picked this case up and will work with you on it. Once we have a solution I will update this thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
We were able to fix this issue by changing "msg_timeout" to 30000 in the ws_connection section of config.json (default is 10000).