Sorry for the caps in the title. I was using it to draw emphasis to my specific problem. I have been unable to find anything relating to this specific inquiry, so I decided to include the aforementioned emphasis in my post title.
I am managing a file storage solution for some internal clients. This solution utilizes SharePoint. We have a process set up with two document libraries - one document library accepts user files and the other document library is being used as a read-only permanent store. I have several Microsoft Flows in place, one of which is responsible for moving files from the "upload bucket" library to the permanent store library.
Now, to get into the issue. I have some users who don't store files locally on their machine (i.e. some C:\ drive folder). These users store files on a shared network drive (not a SharePoint drive) and work with them from the network drive. The SharePoint solution we created is supposed to store their files when these users are done working on them. However, when they attempt to upload a file from the network drive, they get the following error:
Error=Value=StoreBusyRetryLater, Tag=0x0121d3da, Message=Exception=Microsoft.SharePoint.SPException, Message=The file LibraryName/FileName.pdf has been modified by <ASystemAdministrator(Me)> on <DateTime>, Chained=(Value=2164391991, Message=The file LibraryName/FileName.pdf has been modified by <ASystemAdministrator(Me)> on <DateTime>.)
Given the error message, it would appear that I am the one who is keeping the file from making it into the Library; but this does not make sense to me, as I am certainly not modifying the file and the file doesn't actually exist until they upload it. For each file that fails this way, SharePoint is creating 0kb files with the name and extension of the failed document.
As an experiment, we tried to move these files to a folder under the user's C: drive, and the file makes it in no problem. This is what led me to believe that the issue originates from trying to upload a file from a network drive.
Has anyone else experienced an issue like this? How would I go about working around this problem?