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
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.
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.
"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 !!!!!
Here's something that you might want to check out. Does this problem also come with a strange occurance with multiple self induced logical drive mappings? To the point that all of the mapped drives fill the entire alphabet? If it does, then you might want to institute the solution below. It might cure the problem....
0221 » Explorer maps network drives by itself.
This automapping only occurs if one of the following is true:
. You search using the open or advanced find function of an Office 97 application and the search discovers a shortcut that contains a drive letter mapped to a network drive.
. FindFast is installed in your startup group and it indexs a drive which contains a sortcut that uses a drive letter mapped to a network drive.
These behaviors should not occur if you have SP3 installed.
To avoid the problem:
. Don't search folders that contain shortcuts with mapped drive letters.
. Change your shortcuts to use UNC names (\\Server\Share). See tip 177 <../tip0100/rh0177.htm>.
. Disable FindFast <../../SUBA/tip0400/rh0417.htm> (a good idea in any case as this application sometimes leaks memory
and only benefits those you have many thousands of documents that require indexing.
177 » Do your shortcuts attempt to resolve to another computer?
If some of your shortcuts resolve (or attempt to resolve) to a UNC path or a drive letter on a different computer, you can fix the shortcut with SHORTCUT.EXE from the NT 4.0 Resource Kit + Supplement One.
If you don't have the resource kit, you can disable link tracking for all shortcuts by editing:
Add the LinkResolveIgnoreLinkInfo value as type REG_DWORD and set it to 1.
See tip 422 <../../SUBA/tip0400/rh0422.htm>.
0422 » Freeware SHORTCUT.EXE replacement.
In tip 177 <../tip0100/rh0177.htm> we talked about using SHORTCUT.EXE to disable link tracking for a shortcut.
SCUT.EXE <> is a freeware program which, while not as flexible, can disable link tracking for an entire drives shortcuts because it supports wildcards:
SCUT C:\*.LNK -s -q will disable link tracking for all .Lnk files on the C: drive.
If you can't connect, download SCUT from here <../../\dl\scut11.zip>.>
>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.
Strange as it may seem, that was actually the problem.
Note, however, that we are running Win98 clients, WinNT servers and a
Maxtor NAS4000 file server. The office network is all patched through
a 10/100 switch. No timing issues since we replaced the old 10BaseT
hub with a fast switch.
Seems to be our problem also, though we are 100 Mbit full duplex. At this
time we have not had a problem for a couple weeks and I am assuming that it
is because we have massive amounts of leave being used. I did give this to
IS for them to work on, but today is the last day for the person who could
pursue the solution until next year, so we are in a wait and see mode.
Thanks for your help.
"Bruce McCallum" wrote in message
> >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
> Strange as it may seem, that was actually the problem.
> Note, however, that we are running Win98 clients, WinNT servers and a
> Maxtor NAS4000 file server. The office network is all patched through
> a 10/100 switch. No timing issues since we replaced the old 10BaseT
> hub with a fast switch.
> Bruce McCallum
> Network Administrator
> MQLN Architects
I know this thread is a month old, but it caught my eye because we are
having a simaler problem.
We have two different machines (Both Dell's but different models) and both
running the Network version of Autocad 14.01 The user cannot open nor save
a drawing to a Network folder called U:\My Documents but he can open or save
to U:\My Documents\
The drawings do not have a Read only attribute and he does have full access
to his U:\My Documents. He does not have this problem with any other
application (i.e. MS Word, Excell, etc.) it is only with Autocad.
Has anyone come up with a solution to this problem?
"paul_h" wrote in message
When a user tries to save a drawing an error message appears stating
'UNABLE TO SAVE TO DRAWING [drawing location] AS IT IS BEING ACCESSED BY
ANOTHER SESSION. DRAWING SAVED TO [drawing location/SAVBE833.AC$]'. They
then have to rename that file and move it back to the folder it was
origonally in. Then they try to attempt this in Windows Explorer (NT4) they
recieve another error message which reads
'CANNOT MOVE [drawing name] THERE HAD BEEN A SHARING VIOLATION. THE SOURCE
OR DESTINATION FILE MAY BE IN USE.'
I have confirmed that no other files are in use on the network. The
workstations are Windows NT4 and the licenses and all on the workstations,
not on the network. The licenses also expire which require re-registering
them on a regular basis........CAN ANYONE PLEASE HELP ME??!!???
Thanks in advanced.