printpraxis

This doesn't change the behavior. Please see attached screenshots. Does CSP immediately scan the temp file InDesign creates? And therefore InDesign runs into a timeout because it sees its own file locked? To me it doesn’t look like the network connection is the problem here.

Hi there, I’m experiencing a very annoying problem when trying to open InDesign files from a networked server volume. What I have found out today is: When opening files from a network server, InDesign copies the server file to the local drive as described here: https://helpx.adobe.com/indesign/kb/indesign-preferences-support-file-locations.html This causes the ESET daemon to do something that makes InDesign believe that it cannot create the local file. What I can see in Console on the first try of opening an InDesign file is this: 04.01.17 15:16:57,305 esets[319]: summ[013f0400]: ESET Daemon: vdb=31953, agent=fac, name="/Users/jason/Library/Caches/Adobe InDesign/Version 11.0/de_DE/DBTmp29566249456662", virus="", action="", info="Ereignis beim Erstellen einer neuen Datei.", avstatus="not scanned" Therefore InDesign stops opening the file and I can see a temp file on the server. If I re-open the file from the server, the file opens just fine. Shutting down the ESET application doesn’t solve this. But when I kill the ESET daemons in Activity Manager, I can open files directly from the server again. Obviously this is no solution for working with networked files. What can I do to have CSP working AND being able to open InDesign files from my network server? Best, Jason