The last 3 days this has appeared in the Image logs and Planet Press Watch and Image has stopped working. The resolution was to reboot the Planet Press server and it will work fine for a while. Then back to the error and the issue.
any idea why? The file folder that it is distilling the PDF to is local, not networked. Not sure where the Temp File resides on the local machine.

DEBUG: Error creating temp file: (267) The directory name is invalid.
DEBUG:
ERROR: I1007 : Error while converting to PDF : Error converting file: Error getting a temporary file.
ERROR: I1005 : Error while processing job; moving file to error folder: 34D7428.ps

This is an issue when the Alambic.exe (PPAlambic) instance gets corrupted in memory. Once that happens, any other PDF process through that instance will give the same error. It needs to be killed (thus, working after a reboot).

The file that were sent in the error folder of PlanetPress Image (C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Image\error) can now be drop back in the In folder of PlanetPress Image (C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Image\In) and should process normally.

If that happens often, I suggest you open a technical support call at 1-866-348-5863 or through our website.

Thanks Jean. I reconfigured the network printer ports that feed into the PP processes and that seemed to have solved the issue. This happen after a Windows 10 update Dec 12. Not sure what went south with the ports, but all seems to be well currently.

@jean-Cedric
Jean, i have had 2 clients report this issue in the last 3 weeks. Both since a Windows 10 Update. Do you know of anything that is being experienced because of the latest update.???

We seem to see that error with customer who has migrate to a Windows 10 machine or done an upgrade on it.
We are still investigating.
We will keep you posted on this.

thank you

Afternoon
Has there been any progress regarding this issue? I am also getting the same error.

Error while converting to PDF : Error converting file: Error getting a temporary file

Martin, the latest i have been able to get out of OL support are these 2 things.

1) Limit the # of Alambics that are able to run (Preferences,Messenger). That helped a little, but not much.

2) Set a Dos Run Plugin right before any PDF Image creation objectin the process tree and have it run the following command.

taskkill /f /im ppalmbic.exe

That seems to have done the trick. Although it does generate(at least on my system) a few Recoverable errors. I get a few Alambic Crash errors, but they are flagged as recoverable and the Alambic restarts and completes the job.

You guys are funny. ;-)

The problem has been traced to the DiskCleanup scheduled task. It is supposed to clean up files and folders from the Temp folders (user and system) that are not in use and that are at least 7 days old (by default; the value is configurable).

For some reason, some installs of Windows 10 1709 (Fall Creators Update), but not all of them, delete everything immediately, causing ppalmbic.exe to lose its temp folder, which it (wrongly) assumes is always there.

The taskkill trick works because it triggers a restart of the ppalmbic.exe process, thus recreating its temp folder.

As of this writing, we don't know what introduced this new behavior in Windows 10 1709 or why it only happens on some systems and others not.

However, the problem is fixed in the coming release of Connect. A patch should also be made available shortly for both PlanetPress 7.6 and Connect 1.7/1.8.

We are getting this exact error suddenly. How do I determine if we have received this patch? We currently have version 7.6.2.9999. When I run update client, says no new updates.

The system is running Windows 10 1803 and started suddenly when running 1703 a week ago, so I updated to 1803 and its still an issue. Randomly our system stops sending emails and we get the same error in logs:
Error creating temp file: (267) The directory name is invalid.

A reboot will clear it up for a short time, maybe a day. I doubt its a permissions issue since a reboot resolved the problem temporarily. But the perms are correct regardless.

I tried disabling the task for DiskCleanup, still have the problem.

I appreciate any help,
Greg