https://bugs.documentfoundation.org/show_bug.cgi?id=167198
--- Comment #7 from [email protected] --- (In reply to Christian Lohmaier from comment #5) > 2025-06-25 10:44:03+0200: rename_file: failed to rename file - src: > X:\Path\LibreOffice\Stable/program/types/oovbaapi.rdb, > dst:X:\Path\LibreOffice\Stable/program/types/oovbaapi.rdb.moz-backup, err: 13 > 2025-06-25 10:44:03+0200: ### execution failed The File "oovbaapi.rdb" is not write-protected and Administrators/System has full Access. I can also rename the file manually if soffice.exe is terminated. So thats not the issue why the file couldn't be renamed. But the soffice.exe has a handle on this file. And those lines, make me believe that the MAR-Updater tries to shutdown soffice.exe but fails: NS_main: callback app file open attempt 10 failed. File: X:\Path\LibreOffice\Stable\program\soffice.exe. Last error: 32 NS_main: callback app file in use, continuing without exclusive access for executable file: X:\Path\LibreOffice\Stable\program\soffice.exe If I am right, that the soffice-process should be terminated but fails to do, then its logical that files that are in use can't be renamed. Anti-Virus is the same then on the other machine were the update worked, so I don't think its an AV-Issue. Also disabling the AV doesn't improve situation. I also fired up Sysinternals Process Monitor, to see any reasons why "oovbaapi.rdb" can't be renamed, but it doesn't show any errors in conjunction with that file. In "PM" it looks like there isn't even a try to rename the file, because on "uno.exe" which was renamed before, I can see a "SetRenameInformationFile"-operation, but for "oovbaapi.rdb" I can't see that event in the PM-Log. Maybe a timing-issue, with not all handles being closed before updater.exe starts its job? But I'd expect to see that in process monitor... > So X:\Path is kinda unusual/stands out here (also at the top of the log), > and the other log lists P:\… which is also unusual. Yes, its a custom-Install path. X is for anonymous reasons and the "other" letter is evidence that I wasn't successful in fully "anonymizing" the logs :( It should be "X" everywhere.. > So do you remember anything special about your installation – apart > obviously not using the standard installation path? > > Did you at some point move the installation? No > Did you select/deselect > components during installation Yes. LibreLogo is usually deselected on my installs. But that applies to both computers the same way. > Do you maybe have a overzealous antivirus > running that did block creating the backup file for the oovbaapi.rdb file? As said, same AV on both machine and also disabling it doesn't solve the issue. > Was another instance of LibreOffice still running maybe? No. All instances of soffice.exe and soffice.bin were terminated before the test. But for testing I open up a ODS-File, so in that moment one instance of soffice.exe fires up. In process monitor log I can see, that soffice.exe is terminated when I would expect the MAR to rename the file. -- You are receiving this mail because: You are the assignee for the bug.
