Platform-initiated file uploads do not reach ThingWorx Platform
User Actions
The user must perform the following actions when faced with this error:
Check if you received any errors when file uploads were placed in the queue by the Copy service of the File Transfer Subsystem. Ensure that you have set the values of the following parameters correctly:
Selected the queueable and async properties (or set to true) for edge-controlled file uploads.
Have set the sourceRepo property to the edge Thing Name.
Have set the targetRepo property to a valid File Repository Thing, such as SystemRepository.
Check if you have set the sourceFile or sourcePath properties to valid values that the agent can handle.
Check if the agent is still polling and if the lastConnection property of the Thing is updating. In case of any issues, refer to Observation 2: The lastConnection property of the Thing does not update.
Verify if you created a subscription to monitor FileTransfer events on either the source repository (edge Thing) or the target repository (SystemRepository Thing).
Check the agent log. If possible, enable debugging log messages at the edge for the agent. Verify if your agent can receive upload file egress from the Connector. Also, verify if the agent can upload chunks without error.
Check if the upload failed due to a violation of the maximum size of the offline queue used by the File Transfer Subsystem. To do this, review the following configuration settings:
Max Edge-Controlled File Transfers Allowed
Max Edge-Controlled File Transfers Allowed Per Thing
Timeout for Edge-Controlled File Transfers
Additionally, monitor the results of the GetActiveTransferJobs service to check if the count reaches the maximum threshold allowed value or the maximum allowed per Thing threshold value:
Determine why transfer jobs are not being completed and eventually timing out, thus delaying the start of agent-initiated file uploads.
Administrator Actions
In addition to the steps that the user performs, the administrator must perform the following steps when faced with this error:
Check if ThingWorx Platform file repository used for file uploads has run out of disk space.
Review the Connector logs to determine if any exceptions are present. If exceptions are present, refer to Exceptions Observed in the Log for eMessage Connector.
Verify that you have set the emessage.file-transfer.upload.url connection configuration option to the correct value. The syntax is : https, EXTERNAL host name, port.
Was this helpful?