If SharePoint is not setup in a particular way, processes deployed from the K2 Web Designer in SharePoint do not deploy as expected.  Specifically, in a SharePoint farm, the Web Designer deployment will appear to be successful, but in reality it will only have been deployed to a single server in the SharePoint form. 

Before explaining how to resolve this, it is useful to understand how the Web designer deployment works in a SharePoint farm:

• Deployment first executes on the machine to which the session has been established
• It then queries SharePoint for a list of Servers in the farm (e.g. http://IP:port/_vti_bin/K2SPsites.asmx)
• It then takes the first WFE server and gets a list of sites on that server (e.g. http://IP:port/_vti_bin/K2SPsites.asmx)
• After that it resolves the Server name to an IP address
• It then hits each site on http://IP:port and not on http://machinename:port and try to deploy to the K2 Features web service (e.g. http://IP:port/_vti_bin/K2SPfeatures.asmx). Basically looping through all sites on each server and tries to deploy the solution

So how to resolve the scenario where the process only gets deployed to a single node in the SharePoint farm?  This will mean that you need to have a site (web application) on each WFE server that can be accessed locally via http://IP:port.  After doing this and redeploying the process is should make it to all nodes.

Special thanks goes to Barry from K2 for providing the details here.