Pdfexport fails after after upgrading to Puppetter from Phantom; We have had several customer tickets with an exception trace "Error in Exporting Data" and serverout log traces with:

java.lang.Exception: {"error":{"message":"An `executablePath` or `channel` must be specified for `puppeteer-core`","stack":"Error: An `executablePath` or `channel` must be specified for `puppeteer-core`\n    at assert (C:\\snapshot\\node_fies\\node_modules\\puppeteer-core\\lib\\cjs\\puppeteer\\util\\assert.js:18:15)\n    at ChromeLauncher.computeLaunchArguments (C:\\snapshot\\node_fies\\node_modules\\puppeteer-core\\lib\\cjs\\puppeteer\\node\\ChromeLauncher.js:102:36)\n    at async ChromeLauncher.launch (C:\\snapshot\\node_fies\\node_modules\\puppeteer-core\\lib\\cjs\\puppeteer\\node\\ProductLauncher.js:69:28)\n    at async C:\\snapshot\\node_fies\\index.js:150:25","statuscode":200}}

1.Server doesn't have an Internet connection to download chromium.

2. Server blocks below two URLs:

 a. https://storage.googleapis.com/ 

 b. https://npmmirror.com/

Steps to Resolve:

Step 1 : Download the appropriate pdfexport executable files from this link and extract the file contents in /ServiceDesk/custom/pdffolder/. Make sure to replace all existing files.

Step 2 :  Navigate to the /ServiceDesk/custom/pdffolder directory and run the executable with the following commands:

For Windows

pdfexport-win.exe "{\"options\":{\"init\":true,\"revision\":\"1370400\"}}"

For builds after the version 15150 (Windows):

echo {"options":{"init":true,"manual":false,"revision":"1370400"}} | pdfexport-win.exe

For Linux

./pdfexport-linux   "{\"options\":{\"init\":true,\"revision\":\"1370449\"}}" 

For builds after the version 15150 (Linux):

echo '{"options":{"init":true,"manual":false,"revision":"1370449"}}' | ./pdfexport-linux 

You should receive a success message that includes the new Chromium executable path and a .pcr_stats.json file

Test PDF Export: After following the above steps, try exporting the reports again to see if the issue is resolved.

Note: 

Kindly check the alias URL in Admin> Advanced Portal Settings " Alias URL " this should be accessible from the server.