-
Notifications
You must be signed in to change notification settings - Fork 10
Description
I am facing the following error, I am rendering HTML as PDF (Download). Can anyone help?
Error rendering report: An error ocurred while trying to execute "render" command (3). A critical error occurred while trying to execute the render command (2). An error occurred while trying to start daemonized process: An error has occurred when trying to initialize jsreport, seems like there is already a server running in port: 5488 (1). caused by error (3):-> stackError: at startCLI (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\startCommand.js:127:19) at async startCommand (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\startCommand.js:67:5) at async startProcessing (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\startProcessing.js:195:3)caused by error (2):-> stackError: at onCriticalError (C:\snapshot\jsreport\packages\jsreport-cli\lib\commands\render.js:304:19) at C:\snapshot\jsreport\packages\jsreport-cli\lib\commands\render.js:258:14 at async executeCommand (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\executeCommand.js:22:20) at async Object.handler (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\registerCommand.js:76:9) at async parseCLI (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\startCommand.js:156:3) at async startCLI (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\startCommand.js:121:20) at async startCommand (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\startCommand.js:67:5) at async startProcessing (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\startProcessing.js:195:3)caused by error (1):-> meta = {"code":"EADDRINUSE"}-> stackError: An error has occurred when trying to initialize jsreport, seems like there is already a server running in port: 5488 at Object. (C:\snapshot\jsreport\packages\jsreport-cli\lib\keepAliveProcess.js:157:27) at Object.listener (C:\snapshot\jsreport\node_modules\eventemitter2\lib\eventemitter2.js:251:10) at Object.emit (C:\snapshot\jsreport\node_modules\eventemitter2\lib\eventemitter2.js:339:22) at Object._onData (C:\snapshot\jsreport\node_modules\nssocket\lib\nssocket.js:454:8) at Lazy. (C:\snapshot\jsreport\node_modules\lazy\lazy.js:91:13) at Lazy. (C:\snapshot\jsreport\node_modules\lazy\lazy.js:73:19) at Lazy.emit (node:events:390:28) at Lazy. (C:\snapshot\jsreport\node_modules\lazy\lazy.js:74:22) at Lazy.emit (node:events:390:28) at yieldTo (C:\snapshot\jsreport\node_modules\lazy\lazy.js:181:18)Remote Instance Error: Error: at C:\snapshot\jsreport\packages\jsreport-cli\lib\instanceHandler.js:31:29 at processTicksAndRejections (node:internal/process/task_queues:96:5)Remote Instance Error: Error: at Server.setupListenHandle [as _listen2] (node:net:1334:16) at listenInCluster (node:net:1382:12) at Server.listen (node:net:1469:7) at C:\snapshot\jsreport\packages\jsreport-express\lib\main.js:22:12 at new Promise () at startAsync (C:\snapshot\jsreport\packages\jsreport-express\lib\main.js:16:10) at C:\snapshot\jsreport\packages\jsreport-express\lib\main.js:50:14 at Object.start (C:\snapshot\jsreport\packages\jsreport-express\lib\main.js:125:13) at Object. (C:\snapshot\jsreport\packages\jsreport-express\lib\main.js:327:30) at async ListenerCollection.fire (C:\snapshot\jsreport\packages\jsreport-core\lib\shared\listenerCollection.js:157:21)
looking for previously daemonized instance in: C:\inetpub\wwwroot\TanFile\App_Data\jsreport-temp\cli\wSock cwd: C:\inetpub\wwwroot\TanFile\bin\jsreportthere is no previously daemonized instance in: C:\inetpub\wwwroot\TanFile\App_Data\jsreport-temp\cli\wSock cwd: C:\inetpub\wwwroot\TanFile\bin\jsreport