I’m in the habit of pressing Ctrl-S to save Excel files but Excel 365 nearly always throws up this prompt. Nobody else is working on the file although it is in a group folder. I don’t get the same with Word. Any ideas? It’s rather annoying…
I select “Overwrite changes”. I can then press Ctrl-S to my hearts content - the prompt doesn’t occur unless I come back to the document (say) 5 minutes later and save it again.
Windows 11 Pro and pretty recent (like month) version of Nextcloud with latest client.
Maybe even stranger…
I have the same issue with Excel of Microsoft Office Professional Plus 2016 on Windows 11 Home.
The Excel files are in a folder which is synchronised by NextCloud to my Raspberry Pi.
My latoptop is the only one synchronizing this folder so the files are not shared with anyone.
My Laptop used to be Windows 10 and did not have this issue until I upgraded Windows from Windows 10 to Windows 11.
Office and everything else was not upgraded.
So it is just me changing in Excel 2016 in a not shared NextCloud folder and the issue is there since the upgrade of Windows 10 to 11.
Maybe it is a Windows 11 thing.
I can confirm this also happens on Windows 10 and I believe has been a problem for a couple of months (or so). I am also using a group folder and this is a file that only I will be changing. Are you using a group folder @JackV ?
NextCloud on a RaspberryPi, Excel file in My Documents so I am the only one with access to it and not always, but most of the times I get the message and I choose for overwrite.
Whilst this is a multi-user Nextcloud instance, nobody else will be editing the file. I also use OneDrive (another client) and Seafile (personal) - don’t get the same problem there. I wonder if it’s something to do with the temporary lock file that Excel creates:
Perhaps but they’re not new and are apparently ignored according to that screenshot (which makes sense because you wouldn’t want them syncing). A useful test would be to pause (or perhaps exit) the sync client and confirm that the problem goes away. If so we can probably raise a bug report on Github against the sync client repo.
It looks like a similar ticket has been raised here but is perhaps too specific (e.g. I’m using the virtual file system).
As expected, pausing the sync client removes the problem. After resuming sync, waiting a few minutes (not worked out the exact time frame) and saving the excel file, the prompt reappears once more.
Sadly not, should probably raise a bug report. Somebody remind me how to do that? It doesn’t occur with all Excel documents but it is darn annoying. This only effects Nextcloud. I regularly use Seafile, OneDrive, Dropbox and Google Drive. Never seen it with them.
I am almost afraid to mention this but for me the issue seems to be gone. Already for some time now. In the meantime I always upgraded the client and upgraded my server when there was a new version. Maybe they fixed it ? My client is at the latest and my server is 27.0.0 and I see 27.0.1 is available now.
So I ran the upgrade and after that some indexes were missing so I ran:
sudo -u www-data php /var/www/nextcloud/occ db:add-missing-indices
and will let you know if the issue comes back.
I’ve started getting this with Notepad++ as well but here is a bit of key information. Notepad++ has a handy feature whereby it prompts you if the timestamp of an open file has changed - very handy when you’re monitoring an updating log file.
This is what I’ve just observed. I saved the file and immediately got the ticks count:
Note how the last seven digits get zeroed. This is repeatable. Save the file again and get 638269319508677205 ticks. Wait a minute or so and it changed to 638269319500000000.
So I’m going to make a guess that those last 7 digits are a very small time change. Bit suspicious that it’s zeroing last last 7 digits as ticks represents one hundred nanoseconds or one ten-millionth of a second.
Sort of - from my reply above I’ve determined what happeneds but not why. When you save the file to the Windows file system, it has a milliseconds component. When the file synchronises with Nextcloud, the milliseconds is lost/zeroed - hence the reason apps (like Excel and Notepad++) think somebody else has changed the file. In effect, something has - Nextcloud has changed the timestamp.
