I'm trying to get the PDFG service to work in CF2021 on windows, and not having much luck. My initial CF2021 install was via the zip installer, so the addon services were not part of the original install. I have installed the htmltopdf package via cfpm. I have downloaded and installed the add-on services I have started the add-on services service. I have configured and enabled the PDF service in the CF admin. When I click the verify button, it reports that the connection status is "OK" When I attempt to generate a simple PDF via the code below, I get an exception: "Error occurred while generating PDF. Reason: SERVER ERROR" There are no entries in the coldfusion-out, coldfusion-error, or exception log files, nor is there anything in the stderrout log for jetty. The jetty request log does show

127.0.0.1 - - [13/Sep/2024:14:35:41 +0000] "POST /PDFgServlet/ HTTP/1.1" 500 486 "-" "Apache-HttpClient/4.5.13 (Java/11.0.23)"

and I'm assuming that 500 is an http response. But I'm at a loss on where else to look to find out why.

<cfscript>
	cfhtmltopdf() {
		WriteOutput("<p>Test</p>");
	}
</cfscript>

I was just about to post - since installing update 15 on our staging server we have not been able to generate anything with cfhtmltopdf. we get the same error. I have been able to fix the issue post update 16 on a local environment, but am unable to replicate the fix on the staging environment yet

hmm.. I'm on update 16.

if you have time to try a rollback to 13 would give it a whirl. i just have not got arround to trying a rollback yet

I've mostly avoided it like the plague, but I have a client who is having issues with cfdocument causing their server to freeze up -- they have to reboot it several times a day. and I haven't had any luck in tracking that problem down, so i thought I'd try switching.

big PDF's can kill things - we had to update the java version the pdf service was using to get around that (didnt seem to blow anything else up)

There was some stuff I was reading yesterday that said that if you restarted the add on services while CF was still running, it wouldn't be able to connect to them anymore. So stopping CF, restarting the addon services, and then starting CF again is the required order for that. But I've done that, and it didn't help for me.