read only problem

[groovyfill]

hi ,

i have an sbs2000 domain xp clients ..

somethimes people have complaints about read only documents ..

when they open a random word document or an excell document
about 4 times a day they have a raed only file ..
but when they close it and re-open it the file is not read only ...

1 i am sure the files are not used by another person .
2 premissons on server is ok
3 security one server is ok


what can it Be ?

xp bug ?
office bug ?
w2kserver bug ?


who knows an answer ?

greetz groovy

 

[linney]

Here's some light reading for you.



176313 - WD: Troubleshooting Guide: File Locking in Master Documents

http://support.microsoft.com/default.aspx?scid=kb;EN-US;176313

255908 - WD2000: Part 1: General Information About Master Documents

http://support.microsoft.com/default.aspx?scid=kb;EN-US;255908

WD2000: Part 2: General Information About Master Documents

http://support.microsoft.com/default.aspx?scid=kb;en-us;257919&FR=1&PA=1&SD=HSCH

322743 - WD2002: A Beginner's Guide to Troubleshooting Problems in Word 2002

http://support.microsoft.com/default.aspx?scid=kb;en-us;q322743&FR=1

Word 2002 Error Message Resource Center

http://support.microsoft.com/default.aspx?scid=fh;EN-US;wd2002err&FR=1

Support Center Word for Windows

http://support.microsoft.com/default.aspx?scid=fh;EN-US;wrd&FR=1&PA=1&SD=HSCH

 

[groovyfill]

sorry dude ,

has nothing to do with master documents etc

it happens frequently let us say when i open 10 files ...one get read only , until i close it and re-open it then its a read-write file


strang don't you think

 

[bcastner]

This is likely either SMB signing issues, opportunistic locking issues, or the subject of MS Knowledge Base Article 321733.

If you call Microsoft and give the KB Article number, they will not charge you for the call.

For opportunistic locking issues: <

http://support.microsoft.com/default.aspx?scid=kb;EN-US;812937>

For SMB signing issues: <

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q329170>

Both articles have either registry edits you can make, or a direct download source for the patched files. This issue has been discusser earlier in this Forum several times. A search here may give you other possible remedies without having to call Microsoft.