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


Recommended Posts

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.

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.

post-14624-1262718971.jpg

But see the temp file created in the share.

post-14624-1262719062.jpg

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.

post-14624-1262721062.jpg

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.

  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...?

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 ;)

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.

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

post-14624-1262895758.jpg

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. >.<

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • RIP Hotlips..... IMHO, her best scenes were the few where she dared to let her REAL feminine side show through from underneath all that crappy, worn-torn soldier facade that she had to keep up with...she instantly lit up every room or situation where she was featured !
    • Helium Converter 3.3.69.0 by Razvan Serea Helium Converter is a free Windows utility for converting audio files between formats such as MP3, FLAC, AAC, WMA, OGG, and WAV. It supports batch conversion, preserves or updates tag information, and offers features like volume normalization. With a simple interface, it's ideal for users who need to convert large music libraries quickly and efficiently while retaining metadata. Helium Converter key features: Supports file formats: MP3, MP4, FLAC, AAC, M4A, WMA, WAV, OGG, OPUS, APE.... Batch conversion for large music libraries Preserves and edits metadata (ID3, Vorbis Comments, etc.) Volume normalization to equalize loudness Album art extraction and embedding Drag-and-drop interface for quick file selection Adjustable encoding parameters (bitrate, sample rate, channels) Uses internal codecs for consistent performance Supports CUE sheets for split track conversion File renaming based on tags during export Unicode support for international file and tag names Logging of conversion processes for troubleshooting Multi-core CPU support for faster conversions Download: Helium Converter 3.3.69.0 | 25.1 MB (Freeware) Links: Helium Converter Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Since it's been quite a while since the last episode aired, would it be fair (or cruel) to refer to Peggy as a MILF, or even a SMILF ?  HAHAHAHAHAHA
    • Their computers are not gonna stop working in October
    • Crowdstrike the same service provider that caused millions of in damages? I hate disliking a company for a singular failure but they really screwed up.
  • Recent Achievements

    • One Year In
      WaynesWorld earned a badge
      One Year In
    • First Post
      chriskinney317 earned a badge
      First Post
    • Week One Done
      Nullun earned a badge
      Week One Done
    • First Post
      sultangris earned a badge
      First Post
    • Reacting Well
      sultangris earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      171
    2. 2
      snowy owl
      122
    3. 3
      ATLien_0
      122
    4. 4
      Xenon
      116
    5. 5
      +Edouard
      93
  • Tell a friend

    Love Neowin? Tell a friend!