I'm on V12p23, and I'm trying to resolve 'econnreset' and 'X3Dispatch' errors. End-users get the errors launching basic functions, and we see 'econnreset' errors on the batch server tasks. On the runtime server these seem to correlate with KERNELBASE.dll errors in the event log. I have applied the registry settings in KB 105883 related to TCP/IP keepalive. I have two Syracuse servers, one of which resides with Mongo, and both are virtual machines. I have a support case open, and we're still working on it. The error itself seems to indicate an attempt to connect to an X3 resource that no longer exists, or that the connection is ruined in some way. This may have happened occasionally in V12p21, but it's been a frequent issue since upgrading to p23.

http://online-help.sageerpx3.com/erp/12/staticpost/configuration-file-nodelocal/

The online help article for configuring the nodelocal.js file has two settings under the 'server' section; keepAliveTimeout and headersTimeout. (In the actual Node.js documentation, the base 'server.timeout' value is also specified there.)

When Syracuse starts up the log indicates it's setting the server.timeout to 600 seconds, and the server.keepAliveTimeout and server headersTimeout are null. I am curious to know if anyone has set these in X3 and with what results.

Thanks.