Hi Jeff -
This is a topic that's been discussed quite a bit in this news groups.
The following information is copied from an old post:
(snipmode=1)
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
retardant suit>, 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.
(snipmode=0)
hth
jason martin
"jeffva" wrote in message
news:f0fe21d.-1@WebX.maYIadrTaRb...
> I'm using AutoCAD 2000 on an SBS 2000 network. My workstation is a win '98
and I'm trying to find out why I sometimes have issues saving drawings up to
the netowork. I now there are some issues of losing permissions on the
network (verified this with MiscroSoft) but this time all my mapped drives
are OK and other applications can save. The message that I recieved from
AutoCad is:
> Unable to save to drawing x:\Cad Files\2524 as it is being accessed by
another session. Drawing saved to x:\Cad Files\sav27ba9.ac$.
>
> I have had this error in the past and assumed that it was a network
problem. It is odd however because if someone else is trying to access the
same drawing they would be forced to open it as read only?
>
>
