Failure to read socket: process-execution2https://community.appian.com/discussions/f/administration/10211/failure-to-read-socket-process-execution2Hi All, We recently updated to Appian 16.3. We are facimng multiple issues on the environment. to find out the root cause for one of the issue, When I checked the logs: I saw the following error: 04:05:01,749 INFO [stdout] (Appian Engine Worken-USTelligent Community 12RE: Failure to read socket: process-execution2https://community.appian.com/thread/45102?ContentTypeID=1Thu, 27 Apr 2017 18:47:29 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:96fc6a0c-8610-4c26-b1a8-63540359ee74Eliot GersonThe error indicates that the app server is unable to communicate with the engines (in this case, process-execution02). In the vast majority of cases, this is because the engine is not running. However, in rare cases, this may be due to other problems, such as network issues. If checkengine is not showing any problems, I would recommend creating a Support Case.<div style="clear:both;"></div>RE: Failure to read socket: process-execution2https://community.appian.com/thread/45098?ContentTypeID=1Thu, 27 Apr 2017 16:44:16 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:acf00e52-8f4f-4401-9f0b-181d84b83efbrishubEliot, we did check the engines &amp; those running fine.<div style="clear:both;"></div>RE: Failure to read socket: process-execution2https://community.appian.com/thread/45095?ContentTypeID=1Thu, 27 Apr 2017 16:08:53 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:62f4c04b-4a3b-42a4-a8ad-c725d15d5916Eliot GersonThis most likely indicates that one of your Appian Engines is not running. Please run the checkengine script <a href="https://docs.appian.com/suite/help/17.1/Troubleshooting_with_Diagnostic_Scripts.html">docs.appian.com/.../Troubleshooting_with_Diagnostic_Scripts.html</a><div style="clear:both;"></div>