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

    • Over regulation is bad. That's why the EU is behind the US. But, it's a good thing the EU stepped in, in this case.
    • Thanks to the EU, Windows 11 is now a little more tolerable.
    • Microsoft will finally stop shoving Edge down your throat, on one condition by David Uzondu Avid Windows users must be familiar with the dirty tactics Microsoft employs to push its Edge browser. It's a song as old as time; remember when Internet Explorer was primarily used as a tool to download Chrome or Firefox because it was the only thing available? Shortly after IE died, Edge inherited that legacy, becoming the browser you often had to use just to get the browser you actually wanted. Even Microsoft knows this: For years, we have endured the relentless pop-ups after updates, third parties being blocked from changing the default browser on Windows 11, banners appearing when you dare visit a competitor's download page, a fake "how to uninstall Edge" guide, and links within Windows apps that just had to open in Edge, regardless of your set preferences. Microsoft has announced it is dialing back some of this aggressive behavior, promising a reprieve from the constant Edge bombardment. But (and it's a pretty big but) this only applies if you're in the EEA. This shift isn't Microsoft suddenly having a profound change of heart and deciding to respect user choice out of the goodness of its heart. No, this is all thanks to the Digital Markets Act, a major EU rule that targets big online platforms, what they call "gatekeepers", because these companies have a huge impact on how the digital market works. So, what is actually changing for users in the EEA? For starters, Microsoft Edge will not prompt you to set it as the default browser unless you actually open it directly, like by clicking its icon on the taskbar. This specific change started rolling out with Edge version 137.0.3296.52. Other Microsoft apps will also stop bugging you to reinstall Edge if you dared to remove it, with updates for this rolling out in June to Windows 10 and 11. And speaking of default browsers, this is where a significant improvement lies. Previously, hitting "Set default" for your browser in Windows was half baked, only grabbing basic web links like http and https and HTML files. Now, if you're in the EEA, setting your default browser will also cover more obscure link types like ftp and "read," plus a wider array of web-related file formats such as .mht, .svg, .xml, and even .pdf files, provided your chosen browser says it can handle them. The Bing app and those Windows Widgets, which previously had a nasty habit of ignoring your browser choice, will also start opening web links in your default browser. Hallelujah. Users in the EEA will also gain the ability to uninstall the Microsoft Store entirely later this year, though apps previously installed from it will still receive updates. Windows Search is also getting an upgrade in the EEA. Right now, searching from the taskbar mostly just sends you to Bing, no matter what browser you use. But for users in the EEA, other apps will be able to plug into Windows Search and show web results too. If an app registers as a web search provider, it'll start working as soon as you install it. You'll also be able to see results from multiple providers in the search interface, not just Bing. The usual scoping tabs will still be there if you want to filter things, but the default view will be more varied. And yes, you'll even be able to reorder the providers in Settings. These changes are already in Windows Insider builds and are expected to roll out to Windows 10 and 11 in early June.
    • A few things I am wondering about for S3: A.  What's Pike doo gonna look like this time around....yea I've watched the trailers & it looks poofed up, but still.... B. When will the unintelligible, physco-babbling Pelia go away (or at least learn how to speak English properly, without that crappy, slurred accent that sounds like she's on crack, Mary Jane, & LSD at the same time) ?  Hopefully Scotty's arrival will mean her departure is near.... C.  When do we get to see more of the stunningly gorgeous No. 1, preferably in regular/civilian clothes that show off her physical attributes better ? D. Is Spock EVER gonna get laid properly, human style ?  I feel certain that Christine could make any Vulcan-human horizontal bomp a thing to remember for a LONG time  E.  Can we PLEEEEEEZE get rid of the hatchet-head/buzz cut hair styles on Ortega & anyone else that has it....  But otherwise, as Pike says:  HIT IT !  
  • 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
      172
    2. 2
      ATLien_0
      124
    3. 3
      snowy owl
      123
    4. 4
      Xenon
      118
    5. 5
      +Edouard
      92
  • Tell a friend

    Love Neowin? Tell a friend!