Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 41911 views
  • Users 0 members are here
Options
Suggested
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

Neil_C

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.
  • 0

    HI,

    Are these Office documents that are being edited?

    Does it help to turn of on-rename scanning for a test client with the issue but keep remote file scanning enabled?

    Regards,

    Jak

    :26273
  • 0

    Hiya,

    These are Office documents, and mostly Excel spreadsheets, though I think that's because it's mostly spreadsheets that are edited by many users here.

    Unfortunately, On-Rename wasn't turned on.  I can see where you're going with that though,  it's a shame because that would have helped!

    :26457
  • 0

    HI,

    A few more questions :)

    What OS are the files stored on or are they on a filer?

    Does the server end have SAV installed?  Is that set to scan on-read, on-rename, on-write?

    Does it help to turn the scanning off at the server end?  Is it a combincation of client and server scanning settings?

    Can you re-create the issue with Process Monitor running on the client to see the events taking place?  If so, can you make the PML file available somewhere?

    Does the client had just on-read set?

    Thanks.

    Regards,

    Jak

    :26463
  • 0

    Hiya,

    Ok :smileyhappy:

    These files are on Fileservers, mapped drives.

    The Servers are running either Windows 2000 (I know, I know), 2003, and 2008 R2.

    The Policy running on those does not have on-access scanning set at all, they just run scheduled scans of an evening.

    The clients have (under Scanning) Read set but nothing else.  They are (Under exceptions) set to Scan All files, and under Windows Exlclusions do not have Exclude remote files ticked.

    My test policy has Exlude remote files ticked, and for those test machines we have had no more occurances.

    It's worth noting that this happens majoritively on laptops over VPN (which could be being picked up by windows 7 as a slow connection, which is why the file ends up in the clients Sync Centre)  however it does occur with desktops from time to time, but rarely.

    Microsoft refuse to troubleshoot without a chargable call but state that this problem is with the Anti-Virus and remote scanning (even their own version causes this failure apparently)

    Recreating this could prove difficult due to its very intermittant nature, however I'll give it a shot with a laptop over VPN to see if I can recreate it.

    By the way, I may not respond for a week or so suddenly as I'm 2-3 days away from becoming a father again, so if I stop responding, I'll be doing nappies but will return! :smileyhappy:
     

    :26505
  • 0

    as I'm 2-3 days away from becoming a father again

    All the best, Neil :smileyhappy: 

    Christian

    :26509
  • 0

    Thanks!

    I'm hardly nervous at all! :-)

    :26513
  • 0

    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