Error when moving working folder from C: to E:

Hi all, hope all is well.

As always, I’m looking for a nod in the right directions. I’m getting an error message on OL Connect Image after changing the working folders over from C: to E:

I am using a simple workflow on 2025.1.

Folder capture
Set variables (three)
Create MetaData
OL Connect Image output (email with attachment).

Previous builds I have used have accomplished this quickly. I have moved to a new cloud server and am running 2025.1. The speed of processing seems to have dropped drastically. The only difference I can see in build (as I am now running on a faster machine) is that all the working folders still point to C:

I have followed the online guide to move the folders by adding the reg. key.

When I restart and run the workflow, I get the following errors from Image:

REQST: PPImage Request - 1:53:45 PM

INFO: Processing file E:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Image\QueuedJobs\6D072.ps
DEBUG: Reading job options from input file E:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Image\QueuedJobs\6D072.ps
DEBUG: Watch Process Name : TEST_010P4A78XEHQ24D
INFO: Starting conversion…
INFO: Initializing PlanetPress Alambic…
INFO: Distilling file to Filename9000001.pdf…
DEBUG: %%[ Error: invalidfileaccess; OffendingCommand: file ]%%
DEBUG:
DEBUG: Stack:
DEBUG: (w)
DEBUG:
DEBUG: (E:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Image\Spool\6D072\Filename9000001.pdi)
DEBUG: /FO
DEBUG:
DEBUG:
DEBUG: %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
DEBUG: %%[ Warning: PostScript error. No PDF file produced. ] %%
ERROR: I1007 : Error while converting to PDF : Error converting file: invalidfileaccess
ERROR: I1005 : Error while processing job; moving file to error folder: 6D072.ps

REQST: End time: 1:53:56 PM (elapsed time: 00:00:10:721)

Is someone able to nudge me in the right direction please.

Thanks

Dav

The drive may have nothing to do with the issue at all. You mention moving to a cloud server. Is the performance radically different on drives C and E on the cloud server itself, or are you comparing a local drive with a new cloud setup?

So… Is E: a local drive? Is it the same type as C:? (i.e. SSD, NVMe…)

Regardless, one of the first things to check is whether the new folders and drive are in the list of exclusions from the antivirus on the system. Then, check whether the permissions are the same on both drives (group policies may also be involved, depending on your corporate setup).

Thanks for looking at this Phil.

Speed comparison is against last years output - VM ware on-prem vs this years cloud output.

C: is Premium SSD P30 - 5000 IOPS, 200 MB/s - OS disk latency is averaging round 0.5ms.

Have checked with our IT and AV exclusions have been made and no group policies are involved.