Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Desktop client can't sync some files, says WindowsError: 5 Access denied #3906

Closed
ImaCrea opened this issue Oct 19, 2021 · 9 comments
Closed

Comments

@ImaCrea
Copy link

ImaCrea commented Oct 19, 2021

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Expected behaviour

Files should synchronize between cloud and desktop client.

Actual behaviour

Some files are not being synchronized because of this error showing:

Capture d’écran 2021-10-19 à 12 32 54

It may happen on all sorts of files, no matter the type. Majority of them is synchronized well but I'd say about 5~10% encounters this error. Files are well shared in the organization and the user has access to them through their browser without issues. It's the local synchronization through the desktop client that is not happening.

Steps to reproduce

  1. Start sync
  2. See errors coming : WindowsError : 5 Access Denied

Client configuration

Client version: 3.3.5

Operating system: Win 10

OS language: French

Server configuration

Nextcloud version: 20.0.13.1

Storage backend (external storage): S3

Logs

  1. Client logfile:

You can find the zip of logs at this link 👉 https://nuage.liiib.re/s/LgJ6DDH9Wnp4s3D

Thanks for your dear help and to all NC contributors! 🤗

@ImaCrea ImaCrea added the bug label Oct 19, 2021
@FlexW
Copy link

FlexW commented Oct 20, 2021

@mgallien That looks similar to the issues you once had with one customer where the client had trouble renaming files for no reason. The logs are full of errors because of renaming not only the tmp files.

@mgallien
Copy link
Collaborator

@ImaCrea can you please test again with 3.4.1 and sends us back log files ?
the current link as expired and I was not able to copy them locally before

@ImaCrea
Copy link
Author

ImaCrea commented Jan 12, 2022

hey @mgallien I'm sorry but not comfortable anymore sharing it since I've seen into the archive that data are not anonymized. I don't want risking a breach of privacy here. Thanks for understanding.

@mgallien
Copy link
Collaborator

hey @mgallien I'm sorry but not comfortable anymore sharing it since I've seen into the archive that data are not anonymized. I don't want risking a breach of privacy here. Thanks for understanding.

there is always the option of sending it directly to us as we have in any case strong obligations regarding confidentiality
without the logs and because we do not reproduce the error, we cannot fix it

@danir-de
Copy link

danir-de commented Mar 14, 2022

We had the same issue on an instance where virtual files were disabled, just before I found this issue.
We solved it by completely deleting the user profile and enabling virtual files while logging back in.
Will try to get some logs, if I encounter this again.

Edit: Something weird: On said device it's not possible to remove the folder, because the user seemingly lacks access to delete it, even when recursively given via the explorer security advanced tab.

@joshtrichards
Copy link
Member

Possibly related: #4894

@joshtrichards
Copy link
Member

Possibly similar to #5473 and was remedied via #6053.

@ImaCrea Are you still experiencing this / able to reproduce this behavior in newer versions of the client?

@ImaCrea
Copy link
Author

ImaCrea commented Sep 9, 2024

Possibly similar to #5473 and was remedied via #6053.

@ImaCrea Are you still experiencing this / able to reproduce this behavior in newer versions of the client?

Hi there, sorry this was a while ago and I'm afraid I can't reproduce it at the moment.

@claucambra
Copy link
Collaborator

Hello, since the issue seems to not be reproducible I will close this issue -- please feel free to reopen if the problem reappears

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants