Scenario

The following scenario is an example of where a deployment error in K2 Studio occurred:

K2 Server is running in domain A, K2 Studio is in domain B with a logged on user from domain A
Processes that don’t use InfoPath deploys successfully
Processes integrated into InfoPath fails on deploy

If you are experiencing problems when trying to deploy a process in K2 Studio after an installation, use the following checklist to identify issues:

Check the MSMQ configuration on the K2 Server
Launch the K2 Configuration Analysis tool and check if any errors are reported
Check the permissions of the K2 Service Account on the K2 Server
Check to see if authenticated users and local administrators have rights on c:\windows\temp and on the %SharePoint%\template directories
Check if the user (used to deploy the Workflow) has access to the K2 installation folder
Check if the K2 Service account has FULL access to the K2 installation folder
When using more than one domain, check the trust between the domains
Check if the deployment user has permissions in SharePoint

Checks specific to the scenario which can be performed:

Deploy the InfoPath process using a deployment package on the K2 Server (which is in domain A) whilst logged on as a user in domain A in other words eliminating domain B factor
Remove all SmartObject methods from your InfoPath form, or try to deploy a simple "test” process with a simple InfoPath Form that don’t use SmartObjects
Try to disable the creation of Reporting SmartObjects in the MSBuild file