Could not find Chrome (ver. 116.0.5845.96). - puppeteer

neghev

In the new versions of jsreport, if I enable jsreport as a Windows service, I encounter the following issue when trying to generate my PDF report:

Could not find Chrome (ver. 116.0.5845.96). This can occur if either

you did not perform an installation before running the script (e.g. npm install) or
your cache path is incorrectly configured (which is: C:\WINDOWS\system32\config\systemprofile.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
Error: Could not find Chrome (ver. 116.0.5845.96). This can occur if either
you did not perform an installation before running the script (e.g. npm install) or
your cache path is incorrectly configured (which is: C:\WINDOWS\system32\config\systemprofile.cache\puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
at ChromeLauncher.resolveExecutablePath (C:\jsreportapp\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ProductLauncher.js:300:27)
at ChromeLauncher.executablePath (C:\jsreportapp\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ChromeLauncher.js:180:25)
at ChromeLauncher.computeLaunchArguments (C:\jsreportapp\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ChromeLauncher.js:97:37)
at async ChromeLauncher.launch (C:\jsreportapp\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ProductLauncher.js:79:28)
at async createBrowser (C:\jsreportapp\node_modules@jsreport\jsreport-chrome-pdf\lib\chromePoolStrategy.js:98:26)
at async allocateBrowser (C:\jsreportapp\node_modules@jsreport\jsreport-chrome-pdf\lib\chromePoolStrategy.js:113:5)
at async getBrowser (C:\jsreportapp\node_modules@jsreport\jsreport-chrome-pdf\lib\chromePoolStrategy.js:23:30)
at async module.exports (C:\jsreportapp\node_modules@jsreport\jsreport-chrome-pdf\lib\conversion.js:11:19)
at async execute (C:\jsreportapp\node_modules@jsreport\jsreport-chrome-pdf\lib\chromePoolStrategy.js:20:22)
at async C:\jsreportapp\node_modules@jsreport\jsreport-chrome-pdf\lib\lazyRecipe.js:73:20
at async invokeRender (C:\jsreportapp\node_modules@jsreport\jsreport-core\lib\worker\render\render.js:95:5)
at async WorkerReporter._render (C:\jsreportapp\node_modules@jsreport\jsreport-core\lib\worker\render\render.js:147:7)
at async C:\jsreportapp\node_modules@jsreport\jsreport-core\lib\worker\reporter.js:224:19
at async processAndResponse (C:\jsreportapp\node_modules@jsreport\advanced-workers\lib\workerHandler.js:41:17)

How can I fix this issue? Thanks.

admin

The problem is that puppeteer now installs chrome binary to the user folder which runs the install. You run the install with a different user than you run the windowse service with so the windows service can't find the chrome binary.

The solution is to run the windows service and install jsreport with the same user.

Or copy folder from c:\[user installing]\.cache\puppeteer\ to the [windows service user home]\.cache\puppeteer

We will think it through if this could be easier somehow.

neghev

Ok thank you, it working fine!