This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

TMP files created when saving to remote computer, fixed by ticking Exclude Remote Files

Hi,

I'm working on a site that has an issue with TMP files being created when saving to a network drive.  This can be resolved by us ticking "Exclude Remote Files" in Policy, however we'd rather not use that option for obvious reasons.  The tmp file is created during the save process, it does not complete the whole save process and leaves an alpha-numeric temp file on the network and sticks the only working version of the file into local cache on the machine that has attempted the save.

Is there any more information  on this?  Microsoft say that the fault is with Anti-Virus(all types too, including their own) but other than suggesting to turn off Remote File scanning they offer no solution. 

I guess I'm asking if this is a common fault,  whether going to version 10 of Endpoint will resolve it, or if there are known tweaks to stop this happening.

It should be noted that this mostly happens with people detected as slow link, though does seem to affect people over LAN too from time to time.

Any clues?

:26267


This thread was automatically locked due to age.
Parents
  • I wouldn't recommend "scan all files" but it's hard to say that is the cause;  clearly it's timing related so the less that is taking place the more likely it is to work.  Turing off scanning all files may reduce the frequeuncy somewhat and might be worth trying.

    If you can reproduce it, it will certianly make fiddling easier :)  Settings in http://support.microsoft.com/kb/296264 could be one option to look into.  

    Is it just when a certain server OS is involved? I assume an Excel doc from all those servers OSs has had the same problem at some point?

    Does a UNC path have the same problems as the mapped drive?

    The ProcMon log again would be useful if you can re-create it?

    Being able to re-create it, even if it's one in 10 will be the way forward I think so see what combination causes the problem.

    Good luck with the birth!

    Regards,

    Jak

    :26529
Reply
  • I wouldn't recommend "scan all files" but it's hard to say that is the cause;  clearly it's timing related so the less that is taking place the more likely it is to work.  Turing off scanning all files may reduce the frequeuncy somewhat and might be worth trying.

    If you can reproduce it, it will certianly make fiddling easier :)  Settings in http://support.microsoft.com/kb/296264 could be one option to look into.  

    Is it just when a certain server OS is involved? I assume an Excel doc from all those servers OSs has had the same problem at some point?

    Does a UNC path have the same problems as the mapped drive?

    The ProcMon log again would be useful if you can re-create it?

    Being able to re-create it, even if it's one in 10 will be the way forward I think so see what combination causes the problem.

    Good luck with the birth!

    Regards,

    Jak

    :26529
Children
No Data