Error

[imranjalali]

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

[pofider]

seems like there is already a server running in port: 5488

There is another jsreport instance. Kill it from the taskmgr (node process).

You can also let .net kill all other jsreport node processes using

var rs = new LocalReporting()
     .UseBinary(JsReportBinary.GetBinary())
     .KillRunningJsReportProcesses()
     ...

[imranjalali]

Thank you for your prompt reply.

I am already doing it ... from the previous posts.

var rs = new LocalReporting() .UseBinary(JsReportBinary.GetBinary()) .KillRunningJsReportProcesses() .TempDirectory(Path.Combine((string)AppDomain.CurrentDomain.GetData("DataDirectory"), "jsreport-temp")) .AsUtility() .Create();

But that doesn't solve the problem....

[pofider]

Did you try to kill node processes in the taskmgr?

[imranjalali]

Did you try to kill node processes in the taskmgr?

Yes I did!

[imranjalali]

It works fine with sample source code you have provided. But when I deploy in IIS the above error is throwing.

[imranjalali]

Now when I kill the node manually following error is appearing?

Error rendering report: rendering has finished with errors:An error ocurred while trying to execute "render" command (3). A critical error occurred while trying to execute the render command (2). spawn EPERM (1). caused by error (3):-> stackError: at startCLI (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\startCommand.js:127:19) at processTicksAndRejections (node:internal/process/task_queues:96:5) 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 processTicksAndRejections (node:internal/process/task_queues:96:5) 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):-> stackError: at Client.render (C:\snapshot\jsreport\packages\nodejs-client\lib\client.js:92:17) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async startRender (C:\snapshot\jsreport\packages\jsreport-cli\lib\commands\render.js:321:24) at async C:\snapshot\jsreport\packages\jsreport-cli\lib\commands\render.js:228:22 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)Remote stack: Error: at ChildProcess.spawn (node:internal/child_process:412:11) at Object.spawn (node:child_process:698:9) at Object.spawn (pkg/prelude/bootstrap.js:1963:27) at BrowserRunner.start (C:\snapshot\jsreport\node_modules\puppeteer\lib\cjs\puppeteer\node\BrowserRunner.js:119:34) at ChromeLauncher.launch (C:\snapshot\jsreport\node_modules\puppeteer\lib\cjs\puppeteer\node\ChromeLauncher.js:76:16) at async createBrowser (C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\chromePoolStrategy.js:98:26) at async allocateBrowser (C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\chromePoolStrategy.js:113:5) at async getBrowser (C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\chromePoolStrategy.js:23:30) at async C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\conversion.js:11:19 at async execute (C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\chromePoolStrategy.js:20:22) 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\jsreportinstance has been daemonized and initialized successfully (pid: 7280)remote server options:{ "url": "http://localhost:5488/"}rendering with options:{

[imranjalali]

I found something strange when I kill Node JS there is different error with partial HTML Rendered.

Here is the output. Error rendering report: rendering has finished with errors:An error ocurred while trying to execute "render" command (3). A critical error occurred while trying to execute the render command (2). spawn EPERM (1). caused by error (3):-> stackError: at startCLI (C:\snapshot\jsreport\packages\jsreport-cli\lib\commander\startCommand.js:127:19) at processTicksAndRejections (node:internal/process/task_queues:96:5) 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 processTicksAndRejections (node:internal/process/task_queues:96:5) 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):-> stackError: at Client.render (C:\snapshot\jsreport\packages\nodejs-client\lib\client.js:92:17) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async startRender (C:\snapshot\jsreport\packages\jsreport-cli\lib\commands\render.js:321:24) at async C:\snapshot\jsreport\packages\jsreport-cli\lib\commands\render.js:228:22 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)Remote stack: Error: at ChildProcess.spawn (node:internal/child_process:412:11) at Object.spawn (node:child_process:698:9) at Object.spawn (pkg/prelude/bootstrap.js:1963:27) at BrowserRunner.start (C:\snapshot\jsreport\node_modules\puppeteer\lib\cjs\puppeteer\node\BrowserRunner.js:119:34) at ChromeLauncher.launch (C:\snapshot\jsreport\node_modules\puppeteer\lib\cjs\puppeteer\node\ChromeLauncher.js:76:16) at async createBrowser (C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\chromePoolStrategy.js:98:26) at async allocateBrowser (C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\chromePoolStrategy.js:113:5) at async getBrowser (C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\chromePoolStrategy.js:23:30) at async C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\conversion.js:11:19 at async execute (C:\snapshot\jsreport\packages\jsreport-chrome-pdf\lib\chromePoolStrategy.js:20:22) looking for previously daemonized instance in: C:\Users\DefaultAppPool\AppData\Local\Temp\jsreport\cli\wSock cwd: C:\inetpub\wwwroot\TanFile\bin\jsreportthere is no previously daemonized instance in: C:\Users\DefaultAppPool\AppData\Local\Temp\jsreport\cli\wSock cwd: C:\inetpub\wwwroot\TanFile\bin\jsreportinstance has been daemonized and initialized successfully (pid: 10144)remote server options:{ "url": "http://localhost:5488/"}rendering with options:{ "$id": "1", "template": { "$id": "2", "content": "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html dir=\"rtl\" lang=\"ar\">\r\n\r\n <meta charset=\"UTF-8\" />\r\n \r\n <link rel=\"stylesheet\" href=\"/test/Content/bootstrap.min.css\" />\r\n <link rel=\"stylesheet\" href=\"/test/Content/style.css\" />\r\n <link rel=\"preconnect\" href=\"https://fonts.googleapis.com\" />\r\n <link rel=\"preconnect\" href=\"https://fonts.gstatic.com\" crossorigin />\r\n <link href=\"https://fonts.googleapis.com/css2?family=Noto+Kufi+Arabic:wght@400;600;700&display=swap\" rel=\"stylesheet\" />\r\n <script src=\"/test/Scripts/jquery-3.3.1.min.js\">\r\n\r\n \r\n <div class=\"container pm-certificate-container\">\r\n <div class=\"outer-border\">

[pofider]

Don't you have IIS number of worker processes configured to higher than 1?"

[imranjalali]

It's configured as 1

Late yesterday, I mange to render by adding

` var rs = new LocalReporting() .UseBinary(JsReportBinary.GetBinary()) .KillRunningJsReportProcesses() .TempDirectory(Path.Combine((string)AppDomain.CurrentDomain.GetData("DataDirectory"), "jsreport-temp")) .Configure(cfg => cfg.AllowedLocalFilesAccess().BaseUrlAsWorkingDirectory()) .AsUtility().KeepAlive(false) .Create();

       filters.Add(new JsReportFilterAttribute(new ReportingService("http://10.112.8.21:5488/")));`

Now it is showing...

[pofider]

Hmm, I will need some instructions on how to replicate this.

I cloned and compiled this example https://github.com/jsreport/jsreport-dotnet-example-net-webapp

I created a new website in IIS without doing any extra configs. I open the app and things work for me.

Could you give me some steps on how to replicate your issue? The best is to start from scratch, create a new VM lets say in Azure, with windows server xxx, install IIS, and deploy an app...

[kajdzo]

I'm having the same issue here. Works awesome on my local machine but the minute I publish it to EC2 windows IIS same thing happens. Do you guys have any solution ? Here is also peace of my code.

[pofider]

@kajdzo I would love to replicate it and fix it. Would you please provide me with the exact steps on what to do to replicate this? What exact image do you use? Windows Server 2022 base? What do you do in VM, do you provide the user running the app the permissions to write to the app folder? Do you use the default website in IIS or do you create a new one? Do you configure IIS in any way? What .net version do you use?

[kajdzo]

First of all, thanks for quick response. I'm on Windows Server 2022. Using default IIS site. .NET 6. Pretty much everything is out of the box. While debugging this issue I have added user with Full access to everything. My code is pasted in previous post. And here is a list of my nugets. I also installed nodejs on the VM.

[pofider]

I've tried it and have had no issues. Please try the same and let me know if it works. We will need to find out what is different to isolate the problem.

The app

https://github.com/jsreport/jsreport-dotnet-example-webapp I used publish to file system

The server

I have a fresh EC2 Windows Server 2022 Base T2 medium I've installed IIS there using Server Manager and "Add roles and features" I've installed also .net ASP.NET Core Runtime 6.0.11 Windows Hosting Bundle from the link here https://dotnet.microsoft.com/en-us/download/dotnet/6.0 In IIS I used "Add Website.." with the new app pool and targetting the folder with the app deployment and explicit port 5000

Then I opened the app, and I see the pdf renders fine.

[kajdzo]

I won't be able to test it untill tomorrow but as soon as I do I'll post results. Thanks!