Read Only Mode not working when two users open the same file

[angushui]

Hi all,

I am currently using a Windows Server 2003 as our shared drive. However, when two users open the same files, it doesn't shows the "read only" message.

Because generally, when two users open the same file, the second user who open it should receive a "Read Only" pop-up message, to avoid they overwrite the other person edit. But now this doesn't work. It allows both users open the file at the same time and save at the same time. THis cause a lot of problem as many files in our shared drive may edit by different users.

Anyone know how to solve this problem?

Thanks a lot for the help in advance.

[Joel]

What type of file are we talking about here? You'll never see a warning for a text file, for example. The warnings you see are generated by the program you use to open the file with, not the server.

[angushui]

I am talking about Office files, such as .doc, .xls etc...

Thanks.

[Joel]

Then what you're describing is impossible. There are temp files created in whatever directory the file resides in that warns other users' Office applications that the file is in use.

[+BudMan MVC]

If for whatever reason the share has permissions set to say the file permissions allow for changing - but the directory does not allow the creation of the temp file -- then you would not get the popup your talking about where it gives a user name

So for example.. Se here when I open this file from 2 different machines.

I get the popup - gave username of user that had file open.

But see the temp file created in the share.

If I change the permissions in such a way that the user can open/change the file - but does not have permissions to create that temp file.. When no temp file created in the dir -- then the second user to open the file would get a popup like this.

As to why you would not get any popup -- hmmm What are the permissions on the file in question exactly, and the directory for the 2 users in question. Are we sure the users are opening up the same file -- and not a local copy?? I have seen this a few times to be honest.

Had a user tell me they were making changes to a file -- but they were not saving.. Come to find out they were using a local copy of the file on their machine vs the network file, etc.

[Joel]

  BudMan said:

If for whatever reason the share has permissions set to say the file permissions allow for changing - but the directory does not allow the creation of the temp file -- then you would not get the popup your talking about where it gives a user name

Yes, that would be a reason. Bad setup if so, though.

  BudMan said:

Are we sure the users are opening up the same file -- and not a local copy?? I have seen this a few times to be honest.

Or the copy that was emailed to them...?

[+BudMan MVC]

Im getting curious on the cause of this -- since even if the permissions were setup so they can not create the temp file in the directory the file is -- the user still gets a popup.. Just does not say which user - since the file is opened with a lock, etc.

But the user says they don't get a popup at all??

Have to wait for them to come back -- but since they only have 2 posts, we may never find out what the real issue was ;)

[angushui]

Firstly, Thanks a lot for all your help.

I am very sure both people open the same file in the shared drive. I have tested it many times, and the read only pop-up doesn't appear.

However, if two users open in a local NAS shared drive, it work perfectly. The read-only pop up immediately when two person open the same file. So I don't think is a client side problem, it should be related to the setting in the Windows Server 2003.

Based on my observation, it seems it doesn't create the temp file at all, is there any place in the Windows Server can particular blocked the temp file function??

THanks a lot for your help again.

[+BudMan MVC]

Please post the permissions of the directory and the file in question. has the file been set as shared? is it an excel file? If so then 2nd user will not get popup

[angushui]

Hi all,

We have found this info:

http://support.microsoft.com/kb/821464

In the KB article, it said the symptoms are:

- If multiple users try to access Microsoft Office documents on the server, the "File is locked for editing" message does not always appear when the second user opens the file.

- You receive an error message that is similar to one of the following messages when you try to connect to a shared resource:

System error 53. The network path was not found.

System error 64. The specified network name is no longer available.

We got both of the above problem, but this article is only apply to Windows Server 2000, however we are using Win 2003. Ahhhh..... is seems this is the cause, but is not apply to Win Sever 2003. >.<

[+BudMan MVC]

And are you getting the event log entries talked about here?

http://support.microsoft.com/kb/822219/