Seafile Server 5.1.11 Pro files not unlocking

cat1510 · October 6, 2016, 4:10pm

Hi,

we have problem with unlocking files after editing. It is mostly xlsx & docx created with Office 2016.
Clients are Win10 WITH Anniversary Update Build 1607.
Seafile Client is 5.14

Procedure:

Client A opens xlsx file
Seafile Client A locks the file and shows this by yellow icon in explorer.
Seafile Client B syncs the state of the file and shows this by a red icon(locked by another user)
Seafile Client A closes file after editing
On Client A in the explorer the file remains locked.
Reopening and closing the file multiple times has no effect.
On Client B it remains locked too all the time
The file remains locked indefinetly. Only manual unlocking makes the file usable again.

It is possible to unlock the file on Client A manually via context menu.

In the Logfle seaf_ext.log (propably the explorer extension log) we found the following:

[16/10/05 16:56:37] D:/dev/pkg/seafpkg/build/seafile-msi-build/seafile-client-5.1.4/extensions/commands.cpp(line 167) parseResponse: [GetFileStatusCommand] status for /Bestellungen, Rechnugnen und Auftragsbestätigungen/Faber Lederwaren/~$Rechnung Faber 15.07.2016.xlsx is nostatus, raw_resp is none

[16/10/05 16:58:28] D:/dev/pkg/seafpkg/build/seafile-msi-build/seafile-client-5.1.4/extensions/commands.cpp(line 167) parseResponse: [GetFileStatusCommand] status for /Bestellungen, Rechnugnen und Auftragsbestätigungen/Faber Lederwaren/~$Auftragsbestätigung GräsIchen 14.07.2016.xlsx is nostatus, raw_resp is none

[16/10/05 17:19:30] D:/dev/pkg/seafpkg/build/seafile-msi-build/seafile-client-5.1.4/extensions/commands.cpp(line 167) parseResponse: [GetFileStatusCommand] status for /Bestellungen, Rechnugnen und Auftragsbestätigungen/Ranzenfee & Koffertroll/Rechnung R&K 30.09.2016.xlsx is nostatus, raw_resp is none

Thank u

CAT

Vertex · October 6, 2016, 4:16pm

If you are running a virus protection software it could be a problem like this

Jonathan · October 7, 2016, 12:55am

What can you see in seafile.log?
The client use the existence of ~$* file to detect office file open. Perhaps that file is not removed for some reasons. Could you check whether that file exist?

cat1510 · October 7, 2016, 3:30pm

Hi Vertex, hi Jonathan,

you both were right.

Kaspersky blocked the Acces to the Explorer Extension.
After uninstalling it worked as tested on our own system.
There were a lot of ~$* files in the synced Seafile Lib.
After deleting them it worked fine too.
Sometimes Office seems to be too stupid deleteing the temp files.

Special Note for Office ~$ files: They are not ~$ (tilde dollar). It is a high tilde and dollar.
You can see this by showing the properties of a file in Win Explorer.

Thank you for fast support and keep up ur very good work.

kind regards

CAT