Troubleshooting > Troubleshooting File Transfers > Error: Entity <name> does not exist or is not yet associated with a Thing
Error: Entity <name> does not exist or is not yet associated with a Thing
When a file is uploaded to an Azure Storage Container, the Azure IoT Hub Connector fires a FileTransfer event on the ThingWorx Platform. This event is fired on the cx-server.protocol.file-upload-events.repository-thing-name Thing specified in the configuration file of the Connector. If there is not a AzureStorageContainerFileRepository Thing with a name that matches the repository-thing-name, an error similar to the following error is logged in the ThingWorx Platform Error Log:

2019-09-04 21:51:24.910+0000 [L: ERROR] [O: c.t.w.p.APIProcessor] [I: ]
[U: ConnectorUser] [S: ] [P: ] [T: WSExecutionProcessor-1]
Unable to dispatch [ uri = /Things/file-uploads/Events/FileTransfer/]:
Entity file-uploads does not exist or is not yet associated with a Thing

2019-09-04 21:51:24.911+0000 [L: ERROR] [O: c.t.s.s.w.p.WSExecutionInstance]
[I: ] [U: ConnectorUser] [S: ] [P: ] [T: WSExecutionProcessor-1]
error executing APIRequest Message: Entity file-uploads does not exist or is
not yet associated with a Thing, sending ERROR ResponseMessage to caller!
com.thingworx.common.exceptions.InvalidRequestException:
Entity file-uploads does not exist or is not yet associated with a Thing
at com.thingworx.webservices.processors.APIProcessor.
fireEvent(APIProcessor.java:350)
at com.thingworx.webservices.processors.APIProcessor.
dispatchRequest(APIProcessor.java:103)
at com.thingworx.system.subsystems.wsexecution.processor.
WSExecutionInstance.run(WSExecutionInstance.java:49)
at java.util.concurrent.ThreadPoolExecutor.
runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.
run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
* 
The Connector loads and caches all configuration settings during startup. Any changes that you make to the configuration when troubleshooting are ignored until the Connector is restarted. If you make a change to the configuration, you MUST restart the Connector so that the change takes effect.