[Bug]: Couldn't update placeholder info

[dierre72]

⚠️ Before submitting, please verify the following: ⚠️

• [X] This is a bug, not a question or a configuration issue.
• [X] This issue is not already reported on Github (I've searched it).
• [X] Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• [X] I agree to follow Nextcloud's Code of Conduct

Bug description

System Windows 10 Enterprice Version 10.0.19045 Build 19045 Nextcloud Client 3.8.2 Using virtual files plugin: wincfapi

Last month the client stopped to sync and received back a lot of these errors: "Couldn't update placeholder info"

Following an advice from the community I reinstalled it https://help.nextcloud.com/t/make-sure-nextcloud-is-running-on-your-pc-and-couldnt-update-placeholder-info/161123

But now after a couple of months, this morning I have the same issue. I checked if I close nextcloud client and restart the file are shown but if I try to open or keep on device a file I receive the error: Make sure Nextcloud is running on your PC, then try again Obviously Nextcloud is running

I didn't know how to reproduce this bug it seems to be random. At the moment I reinstalled 3 times in the past without resolve this issue. Last Test: I tried to delete the folder into AppData/Roaming/Nextcloud Changed the Nextcloud temp directory on HD instead external SSD Nextcloud client started with the connection request, I connected the client again but without success I need to reinstall again

Steps to reproduce

I do not know how to reproduce

Expected behavior

No error

Which files are affected by this bug

All files in Windows

Operating system

Windows

Which version of the operating system you are running.

System Windows 10 Enterprice Version 10.0.19045 Build 19045

Package

Appimage

Nextcloud Server version

25.0.3

Nextcloud Desktop Client version

3.8.2

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

Are you using an external user-backend?

• [X] Default internal user-backend
• [ ] LDAP/ Active Directory
• [ ] SSO - SAML
• [ ] Other

Nextcloud Server logs

{"reqId":"ZILXRYlQx4fi5CuSsi43VgAAAE8","level":3,"time":"2023-06-09T07:39:49+00:00","remoteAddr":"192.168.1.60","user":"ncp","app":"no app in context","method":"PUT","url":"/remote.php/dav/files/ncp/Backups/GPS/4Sqaure%2014.11.13.rss","message":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.","userAgent":"Mozilla/5.0 (Windows) mirall/3.8.2stable-Win64 (build 20230516) (Nextcloud, windows-10.0.19045 ClientArchitecture: x86_64 OsArchitecture: x86_64)","version":"25.0.3.2","exception":{"Exception":"Sabre\\DAV\\Exception\\BadRequest","Message":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.","Code":0,"Trace":[{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":1137,"function":"put","class":"OCA\\DAV\\Connector\\Sabre\\File","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/CorePlugin.php","line":492,"function":"updateFile","class":"Sabre\\DAV\\Server","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/var/www/nextcloud/3rdparty/sabre/event/lib/WildcardEmitterTrait.php","line":89,"function":"httpPut","class":"Sabre\\DAV\\CorePlugin","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":472,"function":"emit","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":253,"function":"invokeMethod","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":321,"function":"start","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/apps/dav/lib/Server.php","line":360,"function":"exec","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/apps/dav/appinfo/v2/remote.php","line":35,"function":"exec","class":"OCA\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/remote.php","line":171,"args":["/var/www/nextcloud/apps/dav/appinfo/v2/remote.php"],"function":"require_once"}],"File":"/var/www/nextcloud/apps/dav/lib/Connector/Sabre/File.php","Line":297,"message":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.","exception":{},"CustomMessage":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."}}
{"reqId":"ZILXcIlQx4fi5CuSsi43XAAAAEA","level":3,"time":"2023-06-09T07:40:33+00:00","remoteAddr":"192.168.1.60","user":"ncp","app":"no app in context","method":"PUT","url":"/remote.php/dav/files/ncp/Backups/GPS/4Sqaure%2014.11.13.rss","message":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.","userAgent":"Mozilla/5.0 (Windows) mirall/3.8.2stable-Win64 (build 20230516) (Nextcloud, windows-10.0.19045 ClientArchitecture: x86_64 OsArchitecture: x86_64)","version":"25.0.3.2","exception":{"Exception":"Sabre\\DAV\\Exception\\BadRequest","Message":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.","Code":0,"Trace":[{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":1137,"function":"put","class":"OCA\\DAV\\Connector\\Sabre\\File","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/CorePlugin.php","line":492,"function":"updateFile","class":"Sabre\\DAV\\Server","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/var/www/nextcloud/3rdparty/sabre/event/lib/WildcardEmitterTrait.php","line":89,"function":"httpPut","class":"Sabre\\DAV\\CorePlugin","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":472,"function":"emit","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":253,"function":"invokeMethod","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":321,"function":"start","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/apps/dav/lib/Server.php","line":360,"function":"exec","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/apps/dav/appinfo/v2/remote.php","line":35,"function":"exec","class":"OCA\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/remote.php","line":171,"args":["/var/www/nextcloud/apps/dav/appinfo/v2/remote.php"],"function":"require_once"}],"File":"/var/www/nextcloud/apps/dav/lib/Connector/Sabre/File.php","Line":297,"message":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.","exception":{},"CustomMessage":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."}}
{"reqId":"ZILXvmc-S6PZdE1cP4zqjAAAAAQ","level":3,"time":"2023-06-09T07:41:51+00:00","remoteAddr":"192.168.1.60","user":"ncp","app":"no app in context","method":"PUT","url":"/remote.php/dav/files/ncp/Backups/GPS/4Sqaure%2014.11.13.rss","message":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.","userAgent":"Mozilla/5.0 (Windows) mirall/3.8.2stable-Win64 (build 20230516) (Nextcloud, windows-10.0.19045 ClientArchitecture: x86_64 OsArchitecture: x86_64)","version":"25.0.3.2","exception":{"Exception":"Sabre\\DAV\\Exception\\BadRequest","Message":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.","Code":0,"Trace":[{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":1137,"function":"put","class":"OCA\\DAV\\Connector\\Sabre\\File","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/CorePlugin.php","line":492,"function":"updateFile","class":"Sabre\\DAV\\Server","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/var/www/nextcloud/3rdparty/sabre/event/lib/WildcardEmitterTrait.php","line":89,"function":"httpPut","class":"Sabre\\DAV\\CorePlugin","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":472,"function":"emit","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":253,"function":"invokeMethod","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":321,"function":"start","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/apps/dav/lib/Server.php","line":360,"function":"exec","class":"Sabre\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/apps/dav/appinfo/v2/remote.php","line":35,"function":"exec","class":"OCA\\DAV\\Server","type":"->"},{"file":"/var/www/nextcloud/remote.php","line":171,"args":["/var/www/nextcloud/apps/dav/appinfo/v2/remote.php"],"function":"require_once"}],"File":"/var/www/nextcloud/apps/dav/lib/Connector/Sabre/File.php","Line":297,"message":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.","exception":{},"CustomMessage":"Expected filesize of 1746463 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."}}

Additional info

No other info

[dierre72]

Today the same problem reappeared... I have to uninstall than re-install nextcloud

[shivangjhalani]

I am facing the same issue, any updates?

[dierre72]

I am facing the same issue, any updates?

No, on my side the only way is uninstall, restart the pc and re-install again the software.

[shivangjhalani]

No, on my side the only way is uninstall, restart the pc and re-install again the software.

I used bulk crap uninstaller to uninstall and deleted all the nextcloud app related files, the issue still pops up sadly, will try to do that once more.

[dierre72]

Reading on several sites seems the issue is relative to the desktop client but unlucky I did not understand in which way. Someone speaks about a crash of the app that corrupts one or more files. I tried to delete only configuration files but with no effect... The only way is a complete uninstall. I looked for a solution for a long time before open this bug but all my searches are without result. At the moment, my app has been working for a month but when I am out of home I put it in pause

[PhilippSchlesinger]

There is a PR https://github.com/nextcloud/desktop/pull/5890 which will likely fix the problem you describe. The fix is part of the latest release https://github.com/nextcloud/desktop/releases/tag/v3.9.1

[shivangjhalani]

I am using the latest 3.9.1 version, the issue is still there even after a reinstall..

[HEtchevers]

I have the same issue but the original error message: Couldn't update placeholder info.

This has happened when I wanted to "Always keep on this device" for folders with Gb of data.

I believe this happened AFTER the last release was automatically installed, as the first thing I check now when I get weird client errors if is there is an update and I had already been up to date with Version 3.9.1 (Windows). I can try to reinstall it but that is the most I can do on the client end.

All our IT is on vacation until after August 16th locally (and does not offer support in any case for Nextcloud, it's "just a service" offered to enable university employees to have access to cloud storage - maybe @SCD-Aix-Marseille-Universite knows who manages AMUbox, but I don't know where to turn).

[romanbatt]

I have the same issue, except it only affects some of my pictures that are auto-uploaded from my phone. Newer PDF's and even some instant upload photos are fine, and there seems to be no issues.

[mr-manuel]

I have the same issue. I checked the access logs on Nextcloud for the files where the message appears and there is no entry. Therefore the problem should be in the Nextcloud client. A force resync does not change anything.

Windows 11 22H2 Nextcloud Client 3.10.1

[cederron]

I have the same issue

[zolokonst]

I have the same issue. I am using 2 clients: 3.10 on Win11 and 3.12.3 on Win10. The virtual folders is ON. Server version 28.0.4 The client cert on 3.10 is used. (BTW I have troubles with the recent client versions while using this feature) I see the "Couldn't update placeholder info" for files which should be excluded with exclude list only. But these files are appear on the server. Like "~Newfile.txt"

[HikeAndMap]

Same issue here - on two computers

[HikeAndMap]

Same problem - happens to me as well - all I can do is remove all data, delete everything, uninstall, re-install. and losing a day of my life.

[ph818]

I have this issue as well. For me it is affecting me on hidden files from mac and Thumbs.db

I ended up deleting the ._ files and renaming the various Thumbs.db to Thumbs-bak.db, and that cleared the errors... for now.

[SergeTarasov]

Same problem. Had to delete files causing the error from the cloud.

[joshtrichards]

Related: #5955

[bigretromike]

Desktop client 3.15.0

All "error" files are on my local machine with option to always keep them on this machine.

Related to those files logs are

2024-11-29 09:04:57:980 [ info nextcloud.sync.statustracker C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\libsync\syncfilestatustracker.cpp:239 ]:	Investigating "Desktop/Inkscape.lnk" OCC::SyncFileItem::NoStatus CSyncEnums::CSYNC_INSTRUCTION_SYNC OCC::SyncFileItem::Down
...
2024-11-29 09:04:57:986 [ info nextcloud.sync.propagator C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\libsync\owncloudpropagator.h:221 ]:	Starting CSyncEnums::CSYNC_INSTRUCTION_SYNC propagation of "Desktop/Inkscape.lnk" by OCC::PropagateDownloadFile(0x241b1ad65d0)
2024-11-29 09:04:57:987 [ info nextcloud.sync.vfs.cfapi.wrapper C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\libsync\vfs\cfapi\cfapiwrapper.cpp:337 ]:	updatePlaceholderState "E:\\nextcloud-test\\Desktop\\Inkscape.lnk" 1726694276
2024-11-29 09:04:57:988 [ warning nextcloud.sync.vfs.cfapi.wrapper C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\libsync\vfs\cfapi\cfapiwrapper.cpp:925 ]:	"Couldn't update placeholder info" "E:\\nextcloud-test\\Desktop\\Inkscape.lnk" : **"Tej operacji nie można wykonywać na przypiętych plikach w chmurze."**
2024-11-29 09:04:57:988 [ warning nextcloud.sync.propagator C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\libsync\owncloudpropagator.cpp:288 ]:	Could not complete propagation of "Desktop/Inkscape.lnk" by OCC::PropagateDownloadFile(0x241b1ad65d0) with status OCC::SyncFileItem::NormalError and error: "Couldn't update placeholder info"
2024-11-29 09:04:57:990 [ info nextcloud.gui.folderwatcher C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\gui\folderwatcher.cpp:252 ]:	Detected changes in paths: QSet("E:/nextcloud-test/Desktop/Inkscape.lnk")
2024-11-29 09:04:57:991 [ info nextcloud.gui.folder C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\gui\folder.cpp:647 ]:	Ignoring spurious notification for file "Desktop/Inkscape.lnk"
...
2024-11-29 09:05:00:195 [ debug com.nextcloud.owncloudgui C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\gui\owncloudgui.cpp:471 ]	[ OCC::ownCloudGui::slotShowTrayMessage ]:	Going to show notification with title: ' "Synchronizuj aktywność" ' and message: ' "Desktop\\Inkscape.lnk i 4 inne pliki nie mogą zostać zsynchronizowane z powodu błędów. Sprawdź szczegóły w dzienniku." '

What stand out for me is **"Tej operacji nie można wykonywać na przypiętych plikach w chmurze."** which translate: this operation cannot be executed on files that are pinned to cloud.

[CrysK]

I have the same problem since updating from 3.14 to 3.15. Also only with lnk-files. And only in folders with virtual files. On folders with "real sync" lnk-files are still workling

[RTechSn]

I'm having the same problem after switching to virtual files.

[bigretromike]

@RTechSn on 3.15.2 with server being 29.0.10 ?

Currently after 3.15.2 somehow it fixed itself, but I will be monitoring this.

[RTechSn]

@RTechSn on 3.15.2 with server being 29.0.10 ?

Currently after 3.15.2 somehow it fixed itself, but I will be monitoring this.

3.15.1 and server 30.0.4 Updating to 3.15.2 now, will report on results.

[RTechSn]

Updated to 1.15.2, the error seems to be gone. But there is another issue: .lnk files aren't stored locally, despite me selecting this option. Upon selecting "always keep on the device" they have green checkbox, but after next re-sync they have blue cloud icon again.

[Eisteed]

This error keeps on coming back again & again from time to time. I didn't identify what exactly is the cause for my part but eventhough I add *.lock file to exclude list I get errors on .lock files Couldn't update placeholder info. The file doesn't exist locally but exist on my server (how was it synced in the first place no idea I'm only using windows client). Only fix is to manually delete all file causing the Couldn't update placeholder info error then the windows client can sync again.. Quite annoying.

[Rello]

Hello,

recent releases include various fixed for e.g. .lnk files. if the issue persists with the current version, please report back to get the ticket reopened.

[jr1973]

I am having this problem with ipynb files (Python Jupyter Notebook files). I share files across different computers. Can you please address this issue? Thanks

[Unimbecille]

I have the same problem with some backup file of ms-sql. I backup them on cloud to make an off-site backup. The file are uploaded but the error is coming out everytime.

[nickel-w]

I have the error "couldnt update placeholder info" today after the update to 4.0.3 on Windows. I have to nextcloud-instances connected, on different nextcloud-versions, for both I am getting the error

[PintjesB]

I have the error "couldnt update placeholder info" today after the update to 4.0.3 on Windows. I have to nextcloud-instances connected, on different nextcloud-versions, for both I am getting the error

Same!

[apdev-2023]

I have the error "couldnt update placeholder info" today after the update to 4.0.3 on Windows. I have to nextcloud-instances connected, on different nextcloud-versions, for both I am getting the error

Happened to me too!