For some reason I didn't see your post containing the network guy's explanation. So I was basically saying the same thing, just that I've never bothered to confirm if the reason was technical or procedural. This may not have any bearing as it isn't related to FTP, but I think it is related to virtual drives... We have a directory on the network that we generate to and for some reason it decided that if anyone was viewing any file in that location, it wasn't possible to update the project. At that point we tried generating to a separate directory, then publishing to the original location, on the assumption that maybe that would allow the files to be updated correctly. This wasn't the case unfortunately. We now use a work-around where we generate to one location, email the techs to kick off anyone looking at that location (or sub folders) then manually copy the project across. 1. Generate to "staging area". 2. Techs view use some tool to view all users in that folder and subfolders, and forcibly disconnect them. I believe this is a standard Windows tool, but am not sure of the details. 3. Copy and paste the "staging area" to the "live area". I've been told that this is a "feature" of the technology used and cannot be changed. I think it's a whole bunch of disks that "pretend" to be a set of mapped drives. No explanation was offered for why it worked in that configuration for awhile, then broke, and I eventually gave up trying to find out. We were confused for a long time because sometimes it would work and sometimes not. We came to the conclusion that sometimes people weren't viewing it when we did the release and sometimes they were and obviously we (the writers) don't have any visibility on that and the error message just said it couldn't be generated, not that someone was viewing a file. It couldn't hurt to check with your tech to see if this is a possibility, given that no other suggestions have worked (although booting your users off the webserver isn't ideal).
... View more