We have had issues with Image creating a PDF when going through the Watch process. We are using PlanetPress Image, output type is PDF file, and we have the Send Email checked.
The error we see in the Service Console when Distilling the file is:
Error saving to C:\DOCUME~1\Planet\LOCALS~\Temp\tmp3016-0\pdfB1.tmp: This file is too big for the current operation.
I1007: Error while converting to PDF ...

We are currently running on version 7.3.1.6377

We have a few servers running this same version. The process will work on one of the servers but fails on the others.

Is there a known issue or would upgrading to version 7.6 fix the issue?

We are not sure what to do to correct the issue. Any ideas or suggestions would be greatly appreciated.

Thanks.

Hi jkollman,

I can think of a few things here:
- The file may indeed have gotten too big. How large were those temp files? If they were above 2 Gb, this could be an issue, with PlanetPress being a 32 bits application.
- It could have run out of ressources(cpu/memory). Perhaps too much processing was going on, it got too heavy, and it just ended up crashing.
- Older versions may have had memory leaks and similar problems that could have caused issues. Upgrading to 7.6 would certainly help, though I can't guarantee that it will fix the issue, since we don't know for sure what it is.

Also, you say one server works fine. What's different about it? Is it more powerful? Does it has a different version of Windows? A different version of PlanetPress? Finding out what's different compared to the other servers could help us figuring out the problem.

In any case, it may be a good idea to contact Technical Support, and have them connect to your system, and investigate the issue. You may call 1-866-348-5863 to open a support ticket.

Regards,
Raphaël Lalonde Lefebvre

Did you isolate the cause of this? It began happening with our Watch today. I've just opened a ticket.

Regards,

I updated our servers to version 7.6 from version 7.3 and that seemed to take care of the issue. The servers that were having the issue did have 4 gig of ram less than the servers that were working.

Thanks.