I have upgraded jsReport to v4.12, and Node version is v24.11, but I still see the promisify warning. I’ll review the beforeRender and afterRender scripts to see if any updates are needed.

Recently, our jsReport application has been generating a large number of the following DeprecationWarning messages. We are currently using jsReport version 4.3.1.

(node:3268) [DEP0174] DeprecationWarning: Calling promisify on a function that returns a Promise is likely a mistake.
    at node:internal/util:496:17
    at new Promise (<anonymous>)
    at beforeRender (node:internal/util:481:12)
    at executionFn (E:\app-reporting\node_modules\@jsreport\jsreport-scripts\lib\executeScript.js:73:58)
    at sandbox.js:50:18
    at async run (E:\app-reporting\node_modules\@jsreport\jsreport-core\lib\worker\sandbox\createSandbox.js:137:16)
    at async WorkerReporter.runInSandbox [as _runInSandbox] (E:\app-reporting\node_modules\@jsreport\jsreport-core\lib\worker\sandbox\runInSandbox.js:211:14)
    at async executeScript (E:\app-reporting\node_modules\@jsreport\jsreport-scripts\lib\executeScript.js:129:12)
    at async Scripts._runScript (E:\app-reporting\node_modules\@jsreport\jsreport-scripts\lib\worker.js:140:30)
    at async Scripts.handleBeforeRender (E:\app-reporting\node_modules\@jsreport\jsreport-scripts\lib\worker.js:64:7)

I am wondering whether upgrading to the next minor version might resolve this issue. Although these are only warnings, the high volume is significantly cluttering our error logs.

Yes, here is the config:

Thank you!

Hello,

I deployed a jsReport to our production environment and noticed that the header section is overlapping with the report body. However, when I tested this report in our test environment, it displayed correctly. See the following screenshots:

In test environment:

On production:

Do you have any suggestions on how I can troubleshoot this issue? Both production and testing servers are on Windows 2019.

Thank you!

Thank you for your suggestions, Jan. I discovered that the server might restrict external program's access to localhost. I will do more investigations.

Hello,

I deployed my jsReport application on Windows Server 2019, but its API endpoints are not functioning properly.

Here is the error:

Here is my sample request:

The jsReport studio is working:

Pinging API endpoint also returns correct response:

I successfully deployed the same jsReport application on both Windows 10 and Windows Server 2012, and it is operational on both OS platforms.

Any advice is greatly appreciated.

Thank you!

Thank you so much, @jan_blaha! Removing data/setting resolved the issue.

All our projects are about Angular + Express. I integrate jsreport with my Express app following https://jsreport.net/learn/adapting-jsreport#attach-to-existing-express-app . Our Angular programs just call jsreport API (https://jsreport.net/learn/api) to retrieve the reports directly.

In other words, we construct reports using jsreport studio - but our users only access Angular UI and the Angular UI will handle the communications with jsreport through API calls.

Hope it helps.

@jan_blaha , I shared the zipped data folder in Dropbox with you. Let me know if you received the share link.

Thank you,
Genhan

Thank you, @jan_blaha. I emailed you the v2 data zip. Let me know if you received it.

Best,
Genhan