2023 upgrade, can't access pdf service admin page

[impalerware]

Anyone know what's up with the pdf service page in 2023? I just upgraded one of our test servers and every time I go to the pdf service page to see the new pdf service settings, I get a the error page. Log has this in it: 

"Error","http-nio-8500-exec-6","06/01/23","08:59:37","cfadmin","Element ENGINE is undefined in THISPDFSERVICE. The specific sequence of files included or processed is: F:\ColdFusion2023\cfusion\wwwroot\CFIDE\administrator\document\pdfgservice.cfm, line: 602"

[Vikram Kumar M]

Hi @impalerware ,

Please reach out to our support team at cf.install@adobe.com.

Thanks,

Vikram

[BKBK]

Ticket created today: https://tracker.adobe.com/#/view/CF-4218060 

[Mohitha D S]

Hi @impalerware ,

Can you please reinstall the htmltopdf module and try again.

Thanks,

Mohitha

[BKBK]

 I tried doing the following as a workaround:

1.  Use CFPM to uninstall the htmltopdf package, then to reinstall it.
2.  Restart CF2023.
   
   

Alas, that hasn't helped. When I go to the PDF Service page in the Administrator, I still get the error "Element ENGINE is undefined in THISPDFSERVICE."

My setup: I did install CF2023 alongside CF2021 on the same Windows 10 Operating System.

[Charlie Arehart]

@impalerware, please see an elaborated comment I just offered in that tracker ticket BKBK offered (he's the AB listed there, if you didn't know/surmise). 

[pichardov]

I did migrate settings and that seemed to have been the issue at least for us. I went through a bunch of troubleshooting steps with support which did include removing and re installing the htmltopdf package to no avail. What we ended up doing was a full uninstall and reinstall of 2023 and this time not migrating from 2021. That worked.

[zipform · Accepted solution]

I had the same issue and the solution I found was to add the engine variable to neo-document.xml after isenabled.  Stopping and starting the CF service to do so.

<var name='engine'>
<string>pdfReactor</string>
</var>

[Charlie Arehart]

Zipform, thanks for sharing. But to help folks, are you saying you did the post-install migration step like pichardov confirmed? (I'd asked that of the op but they never replied.)

If so, this would seem to reflect a problem with that migration tool (offered on first launch of the cf admin after installation of cf). That would be helpful to know here, for Adobe and others.

Or did you do any OTHER form of migration of admin settings from your old to new cf?

• CAR (ColdFusion ARchive) file import 
• Cfsetup json import (new since cf2021)
• Copy of neo-xml files (highly discouraged from one cf version to a different one)
• Or another approach? 

[zipform]

Hi Charlie,

I was a bit cack-handed and did the migration by creating the migration settings folder after I'd already run the post-install process so I could install the packages first and then run the migration by editing adminconfig.xml

[Charlie Arehart]

Interesting. Thanks. 

[Tim2842955474bi]

Thanks, I'm having the same issue with a migration, and this resolved the issue. Clunky to have to hand-edit, but glad it worked. 

[paulg68955146]

You're a lifesaver!   I didn't have this issue when upgrading from 2018 to 2023 but did when upgrading a second server from 2016 to 2023.  Your solution worked perfectly! 

[FBod-1]

you, sir, are a genius. F

[grayforge]

I tried zipform's solution and it worked for me. 🙂

[Dmitriy Zaslavskiy]

Had the same issue and can confirm that zipform's solution worked.

[BKBK]

This PDF-generation issue goes way back. The solution that Zipform mentions,

<var name='engine'>
<string>pdfReactor</string>
</var

appears among the comments of the bug report  I created in June 2023: https://tracker.adobe.com/#/view/CF-4218060 

Adobe's ColdFusion engineer, Mohitha D., added an important remark in the comments:

"this [the fix to the bug] is already available in the release build (2023.0.0.330468). You have got this error due to some issue while migrating from CF2021 to CF2023 so, the neo-document.xml was not updated."

[Dmitriy Zaslavskiy]

I forgot to mention that it was a migration from 2016. So yes, the neo-document.xml was not updated.