Symptoms

Workflow error throws error. Working on a practice workflow in our ?test? K2 environment the workflow is generating the following error: ?No connection could be made because the target machine actively refused it? No problems with getting into workspace.
 

Diagnoses

At first this issue seemed like the K2 Server was down. After checking the services the Server was up. Next thing to check was the Environment Library fields and make sure they were pointing to the correct server.
 

Resolution


The environment fields values were pointing to the wrong environment making the connection to drop. After changing them to be the correct ones, the workflow started with no issues.

There was an issue with the exchange AWS url having a / instead of the .asmx which was throwing the EWS web service error 404 not found each 15 seconds. After fixing the URL thru the ConnectionStringeditor Emails started to go thru.