Quantcast
Channel: Excel IT Pro Discussions forum
Viewing all articles
Browse latest Browse all 11829

Excel looses write "currently in use, try again later" when another user opens in read only

$
0
0

Hi,

There are numerous threads about similar Excel problems, but none of those seems to fit. Perhaps I have missed something, and someone could point me to the right direction.

We have a network share on a Windows Server 2008 R2 Sp1 server, fully patched quite recently. There is a stable network connection, user has Modify NTFS permissions on a folder, where the file.xlsx is placed, file is inheriting permissions from a folder. Share permissions set to FullAccess.

User1 opens file.xlsx with Windows 7 Sp1 Excel 2010 Sp1 for editing. Everything is fine, file server shows read&write permissions on both, the file.xlsx and the temporary ~$file.xlsx.

User2 opens the same file.xlsx, and gets a prompt, that another user has this file open. So User2 chooses "Read-Only" option. Everything is normal here.

But after the excel file is opened for User2 in Read-Only, server shows, that User2 has read&write, and User1 has only read permissions on file.xlsx. User1 still has read&write to temporary ~$file.xlsx though. After several seconds, even the read connection is gone for User1.

Thus, User1 is unable to save any changes, and gets "File file.xlsx is currently in use. Please, try again later". User2 also cannot save any changes, because he has a file open in read only, even though, the server shows he has read&write permissions on an open file from a network share.

After the User2 closes file.xlsx, User1 is able to save his changes again, no warnings or errors thrown. File server then indicates one Read connection of User1 to file.xlsx, and a separate write connection of the same User1 to the same file.xlsx.

Am I missing something, or is this a bug of some sort?

Thanks in advance,
Vince


Viewing all articles
Browse latest Browse all 11829

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>