No saves and temp files

[Liamnacuac]

I have more and more users that experience a situation where thay can't save or even save-as a file across our network. I've heard there is a .tmp file created during this, and deleting the temp files clears the problem. I was looking for a .dwl maybe not releasing the files, but was told this problem happed before, but no answer was ever found (other than deleting the .tmp files) to solve this. Some of the users were thinking it was a particular server (I checked with IT, no strange events occured), another thought it was a bad connection to the server (again, no event). I thought maybe the refedit function might not be releasing the reference files... I don't know what creates the .tmp file.
We're running 2009 or 2011 mep with CadDuct on Windows 7 and Windows Server 2003
.

[rkmcswain]

I can tell you this much...

When you save a DWG, it...

A) writes the file to a TMP file
B) renames the current DWG to BAK (assuming BAK creation is enabled)
C) renames the TMP to DWG.

The temp files you are talking about are probably the ones in the %temp% directory - these are usually undo, redo, and or autosave files. I have seen machines with thousands of these files without any effect on QSAVE.

It sounds like you have network issues. You may be able to use FileMon (or it's later replacement) to watch the file activity in real time and diagnose this better...

(The .DWL files are created by WhoHas - and have no effect on anything except that application)

[Liamnacuac]

AH, thanks RK. I'll get with IT about chaecking the server as well.

[Misteracad]

In a previous life, I experienced a similar issue with a remote office on more than one occasion. I can't tell you what the ultimate cause was, but the solution was to restart the server at the remote location.

[Liamnacuac]

Apparently, we asked Autodesk about this problem, and they suggested we talked to Microsoft. Microsoft looked at the data, and determined it was a problem with some file called "acad.exe"...
Go figure

We're re-booting our server soon, and there are quite a few updates, so maybe one of these will clear up the problem for a while...