Skip to main content

Hello everyone,

We have a custom component so we can give our users the option to upload certain files to their database and their TW application. This sometimes, in the test and Staging environments (which run on Azure), goes wrong and it returns this error in the live error log:
 

Somehow it is used by another process, which should be impossible as our users will just give the files to the custom component, these files won't be opened in any form or way. It cannot be used by a process on the user's pc, what is Indicium potentially detecting as the other process? This only happens in our Azure environments.

To make matters a bit more difficult, it only happens when the customer uploads a larger batch of files, which we programatically upload in smaller batches of about 50 files. So it doesn't have to process as many requests at once.

Hey ​@SanderAdam,

Does the location point to a folder on the user’s pc? Some things off the top of my head that might be causing this:

  • Is a virus scanner running on the machine? It may be trying to index the newly created temp file and block access
  • How are the batches being created? Could it be that this somehow results in a temp file that has the same name as an already existing one?
  • Perhaps the component is trying to move on to the next batch of files and trying to delete the old one while the upload is still in progress?

This is what comes to mind. We would need to see further logs to accurately detemine what is happening here. Let me know if this helped or if you found what is causing this issue.

Terms & ConditionsCookie settings