Topics created by ryangreay

It looks like some stdio piping issue, however, I'm not sure what is wrong exactly.

Observing the stack trace, it looks like you communicate with jsreport v2 server but you mention you have the latest jsreport package versions. Are you sure you have jsreport.Binary@3.11.0?
If you open http://localhost:5488, don't you see an old jsreport?
You can check in taskmgr the node.exe processes a kill them to be sure there is no old jsreport running.

We aren't planning to release today. Probably Monday.

However, I am afraid Boris was a bit misleading. He fixed the error handling, not the actual error which will need more investigation.
Not sure at this moment, maybe it is a race condition on our side and maybe the process is just failing because of not enough resources.
In that case, you should limit the parallelization on your side.

In case the problem is persistent and you need to recover please use KillRunningJsReportProcesses and restart.

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

I also recommend trying using the "AsWebServer" strategy.
So far it looks like we have never-ending problems with "AsUtility" and maybe the "AsWebServer" will work better for you.
https://jsreport.net/learn/dotnet-local#utility-or-web-server

I had to instantiate a TemplatingEngineConfiguration and then set the timeout property but that seems to have done it. Much appreciated Jan!

@jan_blaha are there any examples of how to actually use this with .netcore pacakge?

Calling pdf utils from .net client can look like this
https://jsreport.net/learn/dotnet-client#pdf-utils

You now need to call both views, get the string from it and pass it as Content.
I believe you can use controller extension method RenderViewToString.
Check its source here