Bug 80923 - FILEOPEN: LO problem open file in Win Server 2008
Summary: FILEOPEN: LO problem open file in Win Server 2008
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: x86-64 (AMD64) Windows (All)
: low minor
Assignee: Not Assigned
Depends on:
Reported: 2014-07-04 18:51 UTC by MarcoG
Modified: 2016-09-19 16:48 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

TestThisFile (466.81 KB, application/vnd.oasis.opendocument.text)
2014-07-04 18:59 UTC, MarcoG
File with problem (629.68 KB, image/bmp)
2015-02-19 19:13 UTC, MarcoG
File correct (587.06 KB, image/bmp)
2015-02-19 19:14 UTC, MarcoG

Note You need to log in before you can comment on or make changes to this bug.
Description MarcoG 2014-07-04 18:51:45 UTC
When I try to open a ".odt" file in a folder on server, LO send that "Document already in use because is already in use by unknown user.

This is very annoying for my company that forces us to work with LO 4.0.3.

Operating sistems:

Server: Win Server 2008 R2 Foundation SP1 64 bit

PC: Win 7 Home Premium SP1 64bit, LO > 4.0.3

Best regards,
Comment 1 MarcoG 2014-07-04 18:59:00 UTC
Created attachment 102282 [details]
Comment 2 Yousuf Philips (jay) (retired) 2014-07-06 02:04:12 UTC
Hello MarcoG,

Please test if this same issue happens with LO 4.2.5 or 4.3.0 and if so, we can look into the issue. You can install the portable version if you dont wish to install it permanently on your company computer.
Comment 3 MarcoG 2014-07-07 16:54:30 UTC
Thanks Jay P., 
just tested with both versions: 
LO and LO 

The bug is still present with both versions.

With version seems to reoccur less frequently, but there is and continues to occur without any apparent logic.
Comment 4 Yousuf Philips (jay) (retired) 2014-07-10 01:43:06 UTC
Thank you for confirmed it with the latest version. I'm passing this issue to the development team to have a look into it.
Comment 5 Buovjaga 2014-12-30 19:30:28 UTC
Is it only a specific .odt file?
Is there a .~lock file corresponding to the .odt in the same folder (you must enable viewing of hidden files)?
If yes, remove the lock file and the problem should be gone.

It should be possible to disable file locking completely by disabling the environment variable SAL_ENABLE_FILE_LOCKING. Unfortunately, I don't know how to do this on Windows.

Setting to NEEDINFO, change status to RESOLVED NOTABUG or back to UNCONFIRMED according to your results.
Comment 6 MarcoG 2015-02-19 19:04:15 UTC
Good Morning,
doing some tests I found that files with problems opening were "defective".

All files were defective in a subfolder of a shared folder on the network. In Windows Explorer by clicking the right mouse button, properties, Security tab, the information of the file gave problems.
The situation is shown on the attached file.

Then I also discovered how to correct the problem:
just copy the file to the desktop PC and the security section of the file back to normal.
So you have to copy the file to the shared network BUT NOT IN A FOLDER (S: \ for example).
By doing so it seemed to me that the security part of the file is written correctly.
So finally you can copy the file to the desired shared network drive in the desired directory (D: \ Book1 \ for example)
Carry the same correct file attached.

In doing so the problem does not reappear when opening the file.

Unfortunately I have noticed that sometimes the problem reoccurs even if a file is in place: we must repeat the procedure above and everything will return to normal.

Sorry for the English: the fault is Google Translate :)
Comment 7 MarcoG 2015-02-19 19:13:11 UTC
Created attachment 113520 [details]
File with problem

property Security file with problem
Comment 8 MarcoG 2015-02-19 19:14:52 UTC
Created attachment 113521 [details]
File correct

property Security file correct
Comment 9 Buovjaga 2015-02-20 10:20:27 UTC
MarcoG: bug 67534 seems to be the same as yours and it got fixed. The fix will be in 4.4.1. Please test and report here. You can close this as duplicate, if you notice the problem is gone in 4.4.1

Thanks to Matthew Francis for spotting the dupe.
Comment 10 QA Administrators 2015-09-04 02:55:53 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2015-10-14 19:48:52 UTC Comment hidden (obsolete)
Comment 12 Robinson Tryon (qubit) 2015-12-18 10:24:08 UTC Comment hidden (obsolete)
Comment 13 Xisco Faulí 2016-09-19 16:48:08 UTC Comment hidden (obsolete)