3. JSReport 2.7.2 all locked up

JSReport 2.7.2 all locked up


  • I've just had an instance where reports failed. I was receiving this error.
    I went into the location C:\Windows\TEMP\jsreport\compile and deleted the folder. restarted JSReport and it came back. Any ideas why this happened ?? It's on windows server.

    Error is

    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    The render log from the start up screen.

    Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14) at ChildProcess. (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64) at ChildProcess.emit (events.js:210:5) at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12) at onErrorNT (internal/child_process.js:456:16) at processTicksAndRejections (internal/process/task_queues.js:80:21)

    +0 Starting rendering request 885 (user: null)
    +6 Rendering template { name: V2-TPIC-Master-Template, recipe: chrome-pdf, engine: jsrender, preview: true }
    +10 Adding sample data HJlmk7ndwI
    +10 Resources not defined for this template.
    +14 Base url not specified, skipping its injection.
    +20 Rendering child template V2-TPIC-CoverPage
    +21 Rendering child template V2-TPIC-Preamble
    +20 Starting rendering request 886 (user: null)
    +28 Rendering template { name: V2-TPIC-CoverPage, recipe: html, engine: jsrender, preview: true }
    +31 Inline data specified.
    +32 Resources not defined for this template.
    +35 Base url not specified, skipping its injection.
    +48 Replaced assets ["TpicLogo.jpg","APILogo.jpeg"]
    +51 Rendering engine jsrender using in-process strategy
    +56 Taking compiled template from engine cache
    +75 Executing recipe html
    +76 Skipping storing report.
    +78 Rendering request 886 finished in 58 ms
    +22 Starting rendering request 887 (user: null)
    +28 Rendering template { name: V2-TPIC-Preamble, recipe: html, engine: jsrender, preview: true }
    +31 Inline data specified.
    +32 Resources not defined for this template.
    +35 Base url not specified, skipping its injection.
    +50 Replaced assets ["RPII.png","TpicLogo.jpg"]
    +59 Rendering engine jsrender using in-process strategy
    +64 Taking compiled template from engine cache
    +75 Executing recipe html
    +77 Skipping storing report.
    +78 Rendering request 887 finished in 56 ms
    +83 Rendering child template V2-TPIC-Preamble-Table
    +84 Rendering child template V2-Certificate-Page
    +83 Starting rendering request 888 (user: null)
    +91 Rendering template { name: V2-TPIC-Preamble-Table, recipe: html, engine: jsrender, preview: true }
    +94 Inline data specified.
    +95 Resources not defined for this template.
    +98 Base url not specified, skipping its injection.
    +151 Replaced assets ["RPII.png","TpicLogo.jpg","Tick.jpg","Cross.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Cross.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Cross.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Cross.jpg","Tick.jpg","Tick.jpg","Tick.jpg","Tick.jpg"]
    +153 Rendering engine jsrender using in-process strategy
    +162 Taking compiled template from engine cache
    +194 Executing recipe html
    +196 Skipping storing report.
    +197 Rendering request 888 finished in 114 ms
    +85 Starting rendering request 889 (user: null)
    +92 Rendering template { name: V2-Certificate-Page, recipe: html, engine: jsrender, preview: true }
    +94 Inline data specified.
    +95 Resources not defined for this template.
    +98 Base url not specified, skipping its injection.
    +152 Replaced assets ["APILogo.jpeg"]
    +169 Rendering engine jsrender using in-process strategy
    +175 Taking compiled template from engine cache
    +194 Executing recipe html
    +196 Skipping storing report.
    +198 Rendering request 889 finished in 113 ms
    +205 Rendering child template V2-Risk-Matrix
    +207 Rendering child template V2-TPIC-Site-information
    +206 Starting rendering request 890 (user: null)
    +211 Rendering template { name: V2-Risk-Matrix, recipe: html, engine: jsrender, preview: true }
    +214 Inline data specified.
    +215 Resources not defined for this template.
    +220 Base url not specified, skipping its injection.
    +230 Rendering engine jsrender using in-process strategy
    +236 Taking compiled template from engine cache
    +250 Executing recipe html
    +253 Skipping storing report.
    +254 Rendering request 890 finished in 48 ms
    +208 Starting rendering request 891 (user: null)
    +212 Rendering template { name: V2-TPIC-Site-information, recipe: html, engine: jsrender, preview: true }
    +214 Inline data specified.
    +216 Resources not defined for this template.
    +220 Base url not specified, skipping its injection.
    +241 Replaced assets ["blankNoImageToDisplay.png","Search.png","Check.png","Warning.png"]
    +243 Rendering engine jsrender using in-process strategy
    +248 Taking compiled template from engine cache
    +255 Executing recipe html
    +257 Skipping storing report.
    +261 Rendering request 891 finished in 53 ms
    +275 Replaced assets ["V2-TPIC-RPT.css","TPIC-RPT-V1ForV2Report.css","TpicLogo.jpg","Multiplay.png"]
    +276 Rendering engine jsrender using in-process strategy
    +282 Compiled template not found in the cache, compiling
    +329 Rendering child template V2-Finding-Score-Indicator
    +331 Rendering child template V2-Finding-Score-Indicator
    +329 Starting rendering request 892 (user: null)
    +334 Rendering template { name: V2-Finding-Score-Indicator, recipe: html, engine: jsrender, preview: true }
    +337 Inline data specified.
    +338 Resources not defined for this template.
    +341 Base url not specified, skipping its injection.
    +351 Replaced assets ["risk-label-down-arrow.png"]
    +352 Rendering engine jsrender using in-process strategy
    +358 Taking compiled template from engine cache
    +370 Executing recipe html
    +372 Skipping storing report.
    +373 Rendering request 892 finished in 44 ms
    +331 Starting rendering request 893 (user: null)
    +335 Rendering template { name: V2-Finding-Score-Indicator, recipe: html, engine: jsrender, preview: true }
    +338 Inline data specified.
    +339 Resources not defined for this template.
    +342 Base url not specified, skipping its injection.
    +351 Replaced assets ["risk-label-down-arrow.png"]
    +360 Rendering engine jsrender using in-process strategy
    +365 Taking compiled template from engine cache
    +371 Executing recipe html
    +372 Skipping storing report.
    +374 Rendering request 893 finished in 43 ms
    +378 Rendering child template V2-Finding-Score-Indicator
    +379 Rendering child template V2-Finding-Score-Indicator
    +378 Starting rendering request 894 (user: null)
    +383 Rendering template { name: V2-Finding-Score-Indicator, recipe: html, engine: jsrender, preview: true }
    +386 Inline data specified.
    +387 Resources not defined for this template.
    +390 Base url not specified, skipping its injection.
    +398 Replaced assets ["risk-label-down-arrow.png"]
    +399 Rendering engine jsrender using in-process strategy
    +404 Taking compiled template from engine cache
    +415 Executing recipe html
    +416 Skipping storing report.
    +418 Rendering request 894 finished in 40 ms
    +380 Starting rendering request 895 (user: null)
    +384 Rendering template { name: V2-Finding-Score-Indicator, recipe: html, engine: jsrender, preview: true }
    +386 Inline data specified.
    +388 Resources not defined for this template.
    +391 Base url not specified, skipping its injection.
    +398 Replaced assets ["risk-label-down-arrow.png"]
    +405 Rendering engine jsrender using in-process strategy
    +410 Taking compiled template from engine cache
    +415 Executing recipe html
    +417 Skipping storing report.
    +418 Rendering request 895 finished in 38 ms
    +423 Rendering child template V2-Finding-Score-Indicator
    +425 Rendering child template V2-Finding-Score-Indicator
    +423 Starting rendering request 896 (user: null)
    +429 Rendering template { name: V2-Finding-Score-Indicator, recipe: html, engine: jsrender, preview: true }
    +432 Inline data specified.
    +433 Resources not defined for this template.
    +436 Base url not specified, skipping its injection.
    +447 Replaced assets ["risk-label-down-arrow.png"]
    +451 Rendering engine jsrender using in-process strategy
    +456 Taking compiled template from engine cache
    +467 Executing recipe html
    +468 Skipping storing report.
    +470 Rendering request 896 finished in 47 ms
    +425 Starting rendering request 897 (user: null)
    +430 Rendering template { name: V2-Finding-Score-Indicator, recipe: html, engine: jsrender, preview: true }
    +432 Inline data specified.
    +433 Resources not defined for this template.
    +437 Base url not specified, skipping its injection.
    +448 Replaced assets ["risk-label-down-arrow.png"]
    +457 Rendering engine jsrender using in-process strategy
    +462 Taking compiled template from engine cache
    +467 Executing recipe html
    +469 Skipping storing report.
    +470 Rendering request 897 finished in 45 ms
    +473 Rendering child template V2-Finding-Score-Indicator
    +474 Starting rendering request 898 (user: null)
    +476 Rendering template { name: V2-Finding-Score-Indicator, recipe: html, engine: jsrender, preview: true }
    +478 Inline data specified.
    +478 Resources not defined for this template.
    +480 Base url not specified, skipping its injection.
    +484 Replaced assets ["risk-label-down-arrow.png"]
    +485 Rendering engine jsrender using in-process strategy
    +490 Taking compiled template from engine cache
    +493 Executing recipe html
    +494 Skipping storing report.
    +495 Rendering request 898 finished in 21 ms
    +501 Executing recipe chrome-pdf

    Information from the error log

    2020-04-15T10:46:26.529Z - error: Rendering request 133 finished with error in 180255 ms
    2020-04-15T10:46:26.532Z - error: Error when processing render request 133 Timeout Error: pdf generation not completed after 179243ms Error: Timeout Error: pdf generation not completed after 179243ms
    at Timeout.<anonymous> (D:\snapshot\jsreport\node_modules\jsreport-chrome-pdf\lib\conversion.js:202:19)
    at listOnTimeout (internal/timers.js:531:17)
    at processTimers (internal/timers.js:475:7)
    2020-04-15T10:46:26.537Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:02:24.942Z - error: Rendering request 698 finished with error in 640 ms
    2020-04-16T13:02:24.945Z - error: Error when processing render request 698 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:02:24.946Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:13:30.263Z - error: Rendering request 709 finished with error in 683 ms
    2020-04-16T13:13:30.264Z - error: Error when processing render request 709 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:13:30.265Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:14:48.960Z - error: Rendering request 720 finished with error in 614 ms
    2020-04-16T13:14:48.961Z - error: Error when processing render request 720 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:14:48.962Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:15:33.985Z - error: Rendering request 731 finished with error in 617 ms
    2020-04-16T13:15:33.986Z - error: Error when processing render request 731 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:15:33.987Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:22:22.439Z - error: Rendering request 742 finished with error in 651 ms
    2020-04-16T13:22:22.440Z - error: Error when processing render request 742 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:22:22.441Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:22:30.387Z - error: Rendering request 753 finished with error in 621 ms
    2020-04-16T13:22:30.389Z - error: Error when processing render request 753 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:22:30.390Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:23:49.304Z - error: Rendering request 764 finished with error in 601 ms
    2020-04-16T13:23:49.306Z - error: Error when processing render request 764 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:23:49.306Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:25:04.368Z - error: Rendering request 775 finished with error in 596 ms
    2020-04-16T13:25:04.369Z - error: Error when processing render request 775 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:25:04.369Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:25:34.564Z - error: Rendering request 786 finished with error in 691 ms
    2020-04-16T13:25:34.566Z - error: Error when processing render request 786 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:25:34.566Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T13:45:16.325Z - error: Rendering request 797 finished with error in 624 ms
    2020-04-16T13:45:16.326Z - error: Error when processing render request 797 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T13:45:16.326Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T14:11:17.234Z - error: Rendering request 808 finished with error in 587 ms
    2020-04-16T14:11:17.236Z - error: Error when processing render request 808 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T14:11:17.237Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T14:45:28.803Z - error: Rendering request 819 finished with error in 613 ms
    2020-04-16T14:45:28.805Z - error: Error when processing render request 819 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T14:45:28.805Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T14:45:56.991Z - error: Rendering request 830 finished with error in 624 ms
    2020-04-16T14:45:56.993Z - error: Error when processing render request 830 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T14:45:56.994Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T15:05:19.324Z - error: Rendering request 841 finished with error in 606 ms
    2020-04-16T15:05:19.326Z - error: Error when processing render request 841 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T15:05:19.326Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T15:05:23.534Z - error: Rendering request 852 finished with error in 586 ms
    2020-04-16T15:05:23.535Z - error: Error when processing render request 852 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T15:05:23.536Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T15:09:30.326Z - error: Rendering request 863 finished with error in 638 ms
    2020-04-16T15:09:30.327Z - error: Error when processing render request 863 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T15:09:30.328Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T15:13:56.060Z - error: Rendering request 874 finished with error in 669 ms
    2020-04-16T15:13:56.061Z - error: Error when processing render request 874 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T15:13:56.062Z - error: Error during processing request at http://localhost:5488/api/report
    2020-04-16T15:20:17.466Z - error: Rendering request 885 finished with error in 607 ms
    2020-04-16T15:20:17.468Z - error: Error when processing render request 885 Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
    Error: Failed to launch chrome! spawn C:\Windows\TEMP\jsreport\compile\jsreport-2.7.2-Bk9CenfI8\chrome\chrome.exe ENOENT

    TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:348:14)
at ChildProcess.<anonymous> (D:\snapshot\jsreport\node_modules\puppeteer\lib\Launcher.js:339:64)
at ChildProcess.emit (events.js:210:5)
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

    2020-04-16T15:20:17.469Z - error: Error during processing request at http://localhost:5488/api/report/V2-TPIC-Master-Template

    0

  • jsreport.exe binary during start extracts chrome binary into the temp directory. This binary is required for the chrome-pdf recipe.
    In your case, it looks like something deleted the chrome binary. I would recommend configuring jsreport tempDirectory somewhere next to you application where you can guarantee nothing else is meddling with files there.
    https://jsreport.net/learn/configuration#directories-configurations

    0

  • So it could be some kind of anti-virus software thinking JSReport.exe is bad and removing it? is that what you are saying?
    Back in Version 2.2.0 my AVG would always think jsreport.exe was malware and would try and remove it, I thought this problem had gone away?

    0

  • In this case, something has deleted chrome.exe, not the jsreport binary. But chrome.exe was extracted from the jsreport binary.
    As noted before, I would recommend configuring jsreport tempDirectory somewhere next to your application where you can guarantee nothing else is meddling with files there.

    0
Log in to reply
 

Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.