cancel
Showing results for 
Search instead for 
Did you mean: 

Kerberos + CIFS 3.3g MS Word document corruption

loftux
Star Contributor
Star Contributor
I've notice what I believe is a serious document corruption bug in CIFS (3.3g nightly from may 27)
It's file under https://issues.alfresco.com/jira/browse/ALF-3071

What happens is that if you use Kerberos with CIFS in 3.3g, whenever you save a document in MS Word, the file gets corrupted / not saved, and leaving temp files around.
This only happens for Word, Excel works (and possibly others, but those are the ones tested).
In the log (see issue for details), you can see a security exception thrown when words tries to rename/delete all its temporary files.

I've checked with node browser on all the temp files, and user has full access as coordinator to those files. Still access exception.

If user is added to ALFRESCO_ADMINISTRATORS it all works.
Also tried 3.3 release version, and it all works there with the same config (but there you have the check out/in bug).

Is there some other possible workaround besides doing everyone to admin? Like setting owner aspect with a javascript or something.
2 REPLIES 2

peterjackson
Champ in-the-making
Champ in-the-making
I have exactly the same behaviour modifying Word documents in the Share environment via CIFS.  If the user is not site coordinator, then temp files are not deleted upon closing the document.  The problem does not occur for site coordinators.

loftux
Star Contributor
Star Contributor
Are you also on 3.3g (what build if so)?
Are you able to actually save the documents, and the only problem is that you have temp files being left? Or does word hang, and when you try to open the document again it is corrupted.

Can you try this:
1. in Company Home, create a space called test (or whatever you like)
2. Assign a user a with Coordinator role to that space
3. Login to cifs, create a word document, open and try to do edits.
Report back what happens.

Reason I'm asking is that no matter what role the user has been assigned, even a role with full permissions, the save error is present. And that look likes it is a bit different that your error. But I havent actually tried to edit within the Sites path, only for a test space in Company Home as described above.