ArchonSoft
Programmer
I am trying to save a ms word file and it always tell me that the file is read only. But I have look at the read only attribute and the box is unchecked, so what's going on?
How to solve that?
How to solve that?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
read only attribute
- Thread starter ArchonSoft
- Start date
- Status
- Thread starter
- #21
ArchonSoft
Programmer
This problem has not been completly solve, the reoccur sometimes.
Thanks for your helpI have had the same read only problem and it never occurs on my network with Win 2000 pcs only Win XP. And it only occurs if the files are saved to the network share drive not the local hard drive. Only the administrator (myself)and the individual have full control to this folder. I spoke to Microsoft, who sent me a fix for this problem to run on all of the Win XP pcs. However this only decreased the occurrence of this problem - they said if it didn't fix it completely then there was something else causing this problem. I have been waiting for Service Pack 2 to be released hoping that it will fix the problem. What you might find is that if the file has been opened before, then closed, it leaves a temp file in the same directory that I think causes this read only problem. You might also see that in Computer Management on your server, under open sessions, that the file says that person still has it open which is not the case. In the meantime, I know logging in and out of the network, eradicates this but it definitely is a very annoying problem.
- Thread starter
- #26
ArchonSoft
Programmer
frogger can you please send me this fix to mbourbeau@claisse.com.
This is not the SMB signing problem.
This is due to a problem with opportunistic locking.
The Microsoft Knowledge Base reference is:
The explanation: This problem occurs when the redirector flushes the contents of the file, and writes to a file handle with read-only access instead of to a file handle with write access. When the redirector received an opportunistic lock break to none, it purged the cache for the file, but did not uninitialize the cache for the file. The redirector also needed to purge and uninitialize when the set end of file occurs because the opportunistic lock break is asynchronous. Because it did not uninitialize the cache for the file, it wrote to the incorrect file handle.
You can obtain, free, a fix for the problem by calling Microsoft and referring to the Knowledge Base Article linked above. In the alternative, use the workaround:
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To work around this problem, disable opportunistic locking on the file server:
Click Start, and then click Run.
In the Open box, type regedit, and then press ENTER.
In Registry Editor, locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\LanmanServer\Parameters
In the right pane, click EnableOplocks, and then press ENTER.
In the Value data box, type 0, and then press ENTER.
Quit Registry Editor.
This is due to a problem with opportunistic locking.
The Microsoft Knowledge Base reference is:
The explanation: This problem occurs when the redirector flushes the contents of the file, and writes to a file handle with read-only access instead of to a file handle with write access. When the redirector received an opportunistic lock break to none, it purged the cache for the file, but did not uninitialize the cache for the file. The redirector also needed to purge and uninitialize when the set end of file occurs because the opportunistic lock break is asynchronous. Because it did not uninitialize the cache for the file, it wrote to the incorrect file handle.
You can obtain, free, a fix for the problem by calling Microsoft and referring to the Knowledge Base Article linked above. In the alternative, use the workaround:
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To work around this problem, disable opportunistic locking on the file server:
Click Start, and then click Run.
In the Open box, type regedit, and then press ENTER.
In Registry Editor, locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\LanmanServer\Parameters
In the right pane, click EnableOplocks, and then press ENTER.
In the Value data box, type 0, and then press ENTER.
Quit Registry Editor.
Also Microsoft are saying that we may receive an error message that is similar to one of the following:
Cannot read file. File is locked
Access Denied
Lock Error
I don't receive this error me. The problem is that when we open the file, its openening it with the title like example "Test.doc (read only)"
Cannot read file. File is locked
Access Denied
Lock Error
I don't receive this error me. The problem is that when we open the file, its openening it with the title like example "Test.doc (read only)"
- Thread starter
- #31
ArchonSoft
Programmer
Yes the problem is the one mentioned by jfguenet, not a file locking one.
jfguenet,
The registry change is at the server, not client.
The error messages vary. They are application specific in some cases.
The error message you gave an example for above is exactly in conformance with the Knowledge Base article.
One other subtlety: some Lan adapters exhibit this same root problem. If you are using 3Com adapters they have driver relases to fix the problem.
The registry change is at the server, not client.
The error messages vary. They are application specific in some cases.
The error message you gave an example for above is exactly in conformance with the Knowledge Base article.
One other subtlety: some Lan adapters exhibit this same root problem. If you are using 3Com adapters they have driver relases to fix the problem.
jfguenet,
Sort of going crazy here with several servers being thrown at me.
In general, if you face read-only errors from XP clients the source is likely a problem with opportunistic locks. The fix for Microsoft Win2k servers is as I linked above.
For networe the patch of three weeks ago should be applied. It deals with exactly the issue I spoke to: a miscommunication/timing issue related to the opportunistic locking features of XP clients.
A summary:
The NWFS.SYS in NC483SP2.EXE adds support for Opportunistic Locking type 2 (OpLock2). OpLock2 allows users to open files on traditional NetWare volumes without placing a lock on the file. The file will not be locked until the user actually attempts to write to the file. This has resolved performance problems with Microsoft Office Excel Spreadsheets.
If the supported NetWare server is running a mixture of traditional and NSS volumes, the OpLock2 functionality will not be available with the NSS volumes, however normal operations should be unaffected with those volumes.
Sort of going crazy here with several servers being thrown at me.
In general, if you face read-only errors from XP clients the source is likely a problem with opportunistic locks. The fix for Microsoft Win2k servers is as I linked above.
For networe the patch of three weeks ago should be applied. It deals with exactly the issue I spoke to: a miscommunication/timing issue related to the opportunistic locking features of XP clients.
A summary:
The NWFS.SYS in NC483SP2.EXE adds support for Opportunistic Locking type 2 (OpLock2). OpLock2 allows users to open files on traditional NetWare volumes without placing a lock on the file. The file will not be locked until the user actually attempts to write to the file. This has resolved performance problems with Microsoft Office Excel Spreadsheets.
If the supported NetWare server is running a mixture of traditional and NSS volumes, the OpLock2 functionality will not be available with the NSS volumes, however normal operations should be unaffected with those volumes.
I have a fix from Microsoft that supposedly resolve the issues listed above for Windows XP Pro Running Office XP Pro with a Windows 2000 SBS. The hotfix basically from what I can see is one of many that is due for release with Win XP SPK2. It resolves all the File locking and Read Only issues that I am expeirencing and Off-line Folder Storage disconnection issues with Win XP Pro. I did try the link for opportunistic locks but I'd did this a month agao but the problem returned. I'm not sure if I'm supposed to share it as it has a weekly password.
I won't be able to try this fix out until next Tuesday/Wednesday but please feel to try it.
(
There are two passwords as it will change shortly but try the first on and then the second if it fails.
Password: mxovk+3_Vm
Next Password: X3e4PX^oXi
Good Luck!
I won't be able to try this fix out until next Tuesday/Wednesday but please feel to try it.
(
There are two passwords as it will change shortly but try the first on and then the second if it fails.
Password: mxovk+3_Vm
Next Password: X3e4PX^oXi
Good Luck!
- Status
Similar threads
- Locked
- Question
