0

Please or Register to create posts and topics.

Execution Error

ceosjleong@ceosjleong
11 Posts
#1 · February 2, 2018, 4:55 pm

I encountered the following error message when try to execute the program.  Pls advise and guide.

Regards

 

An error occurred while starting the application.

AggregateException: One or more errors occurred. (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.)

System.Threading.Tasks.Task.GetResultCore(bool waitCompletionNotification)

NodeInvocationException: 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.

Microsoft.AspNetCore.NodeServices.HostingModels.OutOfProcessNodeInstance+<InvokeExportAsync>d__13.MoveNext()

  • AggregateException: One or more errors occurred. (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.)

    • System.Threading.Tasks.Task.GetResultCore(bool waitCompletionNotification)

    • Microsoft.AspNetCore.Builder.WebpackDevMiddleware.UseWebpackDevMiddleware(IApplicationBuilder appBuilder, WebpackDevMiddlewareOptions options)

    • QuickApp.Pro.Startup.Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory) in Startup.cs

      1. app.UseWebpackDevMiddleware(new WebpackDevMiddlewareOptions

    • System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

    • Microsoft.AspNetCore.Hosting.ConventionBasedStartup.Configure(IApplicationBuilder app)

    • Microsoft.ApplicationInsights.AspNetCore.ApplicationInsightsStartupFilter+<>c__DisplayClass0_0.<Configure>b__0(IApplicationBuilder app)

    • Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication()

  • NodeInvocationException: 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.

    • Microsoft.AspNetCore.NodeServices.HostingModels.OutOfProcessNodeInstance+<InvokeExportAsync>d__13.MoveNext()

    • System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

    • System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

    • Microsoft.AspNetCore.NodeServices.NodeServicesImpl+<InvokeExportWithPossibleRetryAsync>d__10.MoveNext()

    • System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

    • Microsoft.AspNetCore.NodeServices.NodeServicesImpl+<InvokeExportWithPossibleRetryAsync>d__10.MoveNext()

Click for thumbs down.0Click for thumbs up.0
Eben Monney@adentum
154 Posts
#2 · February 3, 2018, 12:54 am

Please perform the below steps to try to address this timeout issue:

  1. Does this timeout error happen on a vanilla installation? Please test with a fresh copy of QuickApp to ensure the error is not caused by an unknown package
  2. Have you enabled "Server Side Rendering / Prerendering" in the template? If so please disable this and test again
  3. What version of node do you have? Run "node -v" on the command line to see the version and also to ensure the environment path for nodejs is set properly. You can also download the latest LTS version of node from here and install it to be sure: https://nodejs.org/en/
  4. You might also try restarting your computer to ensure there's no competition for resources as with timeout errors
  5. Lastly delete the node_modules folder and manually run "npm install" to re-download all client packages. Please ensure the package download process completes with no errors.
Click for thumbs down.0Click for thumbs up.0