Hi,

Thanks for asking here.

I don't know the answer, but I have a question: could it be that the location where the user selects the file from is read-only, or that the file is read-only? I think we had some problem with that a long time ago. Perhaps that problem is back.

If the user tries the exact same thing (same file, from the same computer) but using IFSAPP, does it work then?

/Mathias
 

Hi @Mathias Dahl, Thank you very much. I will ask the user to check the file location.

We didn’t try to upload the same file in same computer with IFSAPP.

We will check that one too.

I really appreciate your suggestions, will check those and let you know. 

Hi Mathias, Thank you for the guidance. This is because of the location where the user selects the files from. This is fixed by granting the write permissions to the user for that folder (folder that he is trying to upload from).

Thanks again 

Thanks for reporting back, good to know the reason behind the problem.

As a background, I know we once had some code that, for some reason, moved the file before it was checked in to IFS. That is not there anymore, but there seems to be some remnant left. We should not have to have write access to the folder where the user selects files to be uploaded/checked in from. If you like you can file a support case for us to look into. If not, that is, you are happy with the workaround you found.