Page 1 of 1

Network & User File Issues

PostPosted: Fri Jul 22, 2011 2:21 pm
by Neil Blanchard
Hello,

A couple of times recently, we have been able to accidentally open a file that someone else has open and *not* get the usual warning that they have the file open. In the first couple of occasions, we got an error message when trying to save the file, and were asked where to save it locally. On the more recent occasion, the second person to close the file caused the loss of a day (or two) of work by the other person to get lost. Luckily, we renamed a DBK file and recovered the work.

On one of the computers, Sessions was not enabled (they are now!) and for some reason, the most recent Session file was from back in May!? This is rather odd as well, since the machine where the 2 days of work was done did have Sessions enabled to 4.

Sorry if this is confusing, but has anybody had the problem of not being warned when someone else has a file open? Most of the time, this has worked correctly, but not every time...

Re: Network & User File Issues

PostPosted: Fri Jul 22, 2011 3:23 pm
by joshhuggins
Yeah this has been happening I think since version 11. I have not been able to figure out what causes it. Seems to happen a lot more the longer the file has been opened and possibly a long time between force saves? I've logged quite a few posts on it in the past as have a few others. It's something to do with the files over the network possibly being released by the system or something that allows the second users to open the files. It's been a while since I've dug into the whys and hows of it. We just do a save as to a temp file and then do a save back to the original when there is only one person working on a file. When there are two or more, then we have to stop and figure out who last saved when and what has been done between the files. It's a bit of a pain. This is one of the reasons we enabled session too. Did you check the sessions paths to maybe see if the sessions were going to another location that expected? We have them set to each users system so we can have redundant sessions per user. I have a batch script that runs in the mornings that keeps things cleaned up on the users systems. Below is the part that removes session files older than 14 days.
Code: Select allROBOCOPY "C:\Datacad Sessions" "C:\Session Clean" /r:0 /w:0 /s /MINAGE:14 /MOVE
RD /s /q "C:\Session Clean"