Getting Node invocation timed out error when invoking JS file using Microsoft.AspNetCore.NodeServices #71

New Issue

fergalmoran · 2025-08-09T17:14:54Z

fergalmoran commented

2025-08-09 17:14:54 +00:00

Originally created by @kgrvr on 5/9/2018

Title

Getting Node invocation timed out error when invoking JS file using Microsoft.AspNetCore.NodeServices

Functional impact

I developed application which is using NodeServices and deployed it on Azure using following article:
https://code.msdn.microsoft.com/How-to-export-HTML-to-PDF-c5afd0ce

It's working locally, but not on deployed version.
Getting node time out error:

The Node invocation timed out after 60000ms.
You can change the timeout duration by setting the InvocationTimeoutMilliseconds property on NodeServicesOptions.
The first debugging step is to ensure that your Node.js function always invokes the supplied callback (or throws an exception synchronously), even if it encounters an error. Otherwise, the .NET code has no way to know that it is finished or has failed. | Source: Microsoft.AspNetCore.NodeServices

Expected result

PDF should be created.

Actual result

NodeService throwing timeout error

I also followed related issues on Github:
https://github.com/aspnet/JavaScriptServices/issues/1377
https://github.com/aspnet/JavaScriptServices/issues/1177

But still getting Timeout error on deployed version. Any help would be appreciated. Thanks.

*Originally created by @kgrvr on 5/9/2018* ### Title Getting Node invocation timed out error when invoking JS file using Microsoft.AspNetCore.NodeServices ### Functional impact I developed application which is using NodeServices and deployed it on Azure using following article: https://code.msdn.microsoft.com/How-to-export-HTML-to-PDF-c5afd0ce It's working locally, but not on deployed version. Getting node time out error: > The Node invocation timed out after 60000ms. > You can change the timeout duration by setting the InvocationTimeoutMilliseconds property on NodeServicesOptions. > The first debugging step is to ensure that your Node.js function always invokes the supplied callback (or throws an exception synchronously), even if it encounters an error. Otherwise, the .NET code has no way to know that it is finished or has failed. | Source: Microsoft.AspNetCore.NodeServices ### Expected result PDF should be created. ### Actual result NodeService throwing timeout error I also followed related issues on Github: https://github.com/aspnet/JavaScriptServices/issues/1377 https://github.com/aspnet/JavaScriptServices/issues/1177 But still getting Timeout error on deployed version. Any help would be appreciated. Thanks.

fergalmoran closed this issue

2025-08-09 17:14:54 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#71