Connector Exception 14: File Download Failure Due to File Deletion on the ThingWorx Platform Before Agent Downloads It
If a file that is to be downloaded to an agent is deleted from the ThingWorx Platform before the agent has downloaded it, this exception is generated. For more information, refer to
Observation 9: Platform-initiated file downloads are not downloaded by asset.
The following scenario results in this exception:
1. Start ThingWorx Platform.
2. Start eMessage Connector.
3. Make sure that the agent is not running on the remote device.
4. Call the Copy service of the File Transfer Subsystem with queueable set to true. The subsystem places the file download in the queue.
5. Delete the file from the SystemRepository of the ThingWorx Platform before the agent pings to check for egress messages.
6. Start the agent on the remote device so that it checks for the pending file download.
In this scenario, the download fails when the eMessage Connector attempts to calculate the checksum of the file from the SystemRepository because the file no longer exists. Here are some lines from the error that is logged:
... [NettyClient-NIO-2] ERROR c.t.protocol.emessage.EmessageCodec -
failed to process file checksum for download 'SystemRepository:/download.txt',
transferInfo={sourceRepository=SystemRepository, transferMode=write,
targetFile=download.txt, targetPath=/Downloads/download.txt,
description=Axeda package to download a file., transferPath=/Downloads/download.txt,
packageVersion=1, packageName=Download File Package, transferId=...
sourceFile=download.txt, userId=admin, sourcePath=/download.txt}
...RequestException: Server returned an error with status STATUS_INTERNAL_ERROR and
message: Unable to dispatch [ uri = ...
Unable to Invoke Service GetFileChecksum on SystemRepository :
/ThingworxStorage/repository/SystemRepository/download.txt (No such file or directory)
...