Hi Chris,

Where does the tiff image reside in relation to the location of the DIV?

Are the folders where the tiff image resides and where the DIV is located 1) local paths; 2) referenced via a mapped drive to another system; or 3) referenced via UNC paths to another system?

Are you running Photoshop on the same system as XPP?

As far as you know does this only happen with specific tiff images or with all tiff images? If the problem only happens with some tiff images, what is different about the tiff images that cause the problem to occur (e.g. specific type of tiff image)?

I know Support has probably asked you all these questions, but the community needs to know some more details in order to brainstorm as to what might be the problem (or even to perhaps try to see if they can reproduce your problem).

Also, you have not mentioned what version of XPP you are running and what O/S (e.g. what version of Windows) and what version of Photoshop?

Sorry for all the questions.

Mark Hutchinson might be on the right track as a "permission" problem, since you making a copy of the DIV (at least on Windows) can give you different permissions on the copied folder than the original one. Although I'm not sure how the DIV permissions would come into play as far as doing a save of the edited image in Photoshop unless the image lives under the DIV (or JOB if you're actually first copying the whole JOB).

Don't know anything myself about how Photoshop works as far as how it accesses the image file when you edit it and then try to save it.

As far as the "technical details" of what happens with access to an image file in an open DIV in the XyView, for tiff (and jpeg) images the XPP code converts on-the-fly to PS to include in the PS generated for the display of the page (no converted file is stored by XPP in a .xyconvert or .xyconvertpdf folder, like is done for other image types). So the image file is opened by XPP, read in, and then the file is closed - no file locking is done on any image files by the XyView (file locking involves mainly the job.dpd file in the DIV folder). Although on Windows having a file open sometimes acts like a "lock".

Of course, the actual XPP code processing tiff images is separate from that for processing jpeg images. However, if there was a bug in XPP where it was leaving a tiff image file open then I would expect that Support would have been able to reproduce the problem.

Sure seems like a mystery.

Great details, Chris.

Need a few more details and clarification to make sure I understand, because the problem may come down to the nitty gritty.

What version of Windows on the Windows Server running XPP (you connect to via Remote Desktop)? What version of Windows on your PC where you run Photoshop?

You said: XPP is accessed via a windows remote desktop connection to a Windows server using a mapped drive on a server in the cloud.
... but xz and sd_liz are referenced like this: XYV_EXECS=C:\XPP\xz

Do you mean that xz and sd_liz (C:\XPP) on that remote Windows Server are a mapped drive to even another machine "in the cloud", or were you talking about the images when you mentioned a mapped drive here?

You indicate that alljobz job data (XYV_JOB) is using an UNC path to access that data.

And you seemed to indicate that XPP is using a "mapped drive" to the images, but didn't give a specific example path. I just want to verify if XPP access to images is "mapped drive" or "UNC path" (like alljobz)? We've found in the past that sometimes it makes a difference (unfortunately).

Again, all these details can help us brainstorm and make sure anyone trying to reproduce the problem is not comparing apples to oranges.

It's interesting to me that you are running Photoshop on a completely different system (your PC) than where XPP is running (remote Windows Server). That "shouldn't" matter I would think, but the truth is that XPP on Windows runs on top of the NutCracker Operating Environment (including some services), and so it could be a factor.