Paul, Hendie, Francisco, et al
Read-only problems: Read-only's are generally related to timing issues between the server and the client.
The basics of the autocad save procedure is:
1. Autocad verifies the file lock that it created previously (either at file open or on last save)
2. Autocad creates a new temporary file, and locks it. The current drawing information is written to the temporary drawing.
3. Autocad deletes the .bak file.
4. Autocad sends a remove lock request for the original .dwg.
5. Autocad tries to rename the .dwg to a .bak. General problem location: Usually when a read only occurs the server has not
completed the remove lock request. The rename is then treated as a sharing violation and the rename request is denied by the
server.
6. Autocad unlocks the temporary drawing.
7. Autocad renames the temporary drawing to the original drawing name. The read only problem can occur here as well, as if the file
lock is not removed before the rename request is made, there is a sharing violation and the rename request is denied.
8. Autocad then re-locks the original drawing name.
Things that can cause these problems are as follows:
Very fast workstations and a "slow" server.
Network saturation
Excess server workload
Virus protection on the client
Virus protection on the server
"Misbehaving" network drivers on the client or on the server.
Bruce McCallum indicates updating his video drivers solved a problem that he was having with this, which doesn't make much sense,
but as dependant as Autocad is on the video interface, is a possible candidate.
This problem isn't necessarily an autodesk problem
, but a network timing issue. The fix for
this problem is illusive and sometimes expensive (new servers, additional servers, faster networks, more isolated (switched)
networks, etc). Autodesk people that I have spoken to have indicated that every time that they've seen this (actually seen it, at a
customer site) the solution was to increase client to server throughput. Without fail, that's been the solution. The problem is more
evident with Autocad, because of the complicated write. There are more chances for things to fail with so many file locks, un-locks,
and renames. Autodesk's file write method is completely compliant with Microsoft's API requirements, but when the server doesn't
respond within the designated period, the write fails (actually the rename fails) and the user is left with a temp file.
jason martin
frankfurt-short-bruza
"hendie" wrote in message news:f09a4ff.8@WebX.maYIadrTaRb...
> If you find a cure let me know. We've got the same problem here. NT4 server, 1 NT PC, 1 Win2000 PC, both running Acad 2000. I've
been running with Win2K for some time now but the problem only appeared earlier this week for me and today for my compatriot and
it's killing us. I can be working on a drawing for some time, carry out saves regularly, then for some reason I get the message
"File is being accessed by another session" and changes my open file to read only. I then have to go through the rigmarole of
"saving as" locally. exiting Acad and manually moving my "new" file to the correct location. Sometimes I even have to reboot in
order to get the file to overwrite the original. I've seen loads of messages referring to the same problem and every now and then
they refer to Knowledge base this or Knowledge base that but never seem to point to a proper cure. SOMEONE PLEASE HELP !!!!!
>