Communication with the underlying transaction manager has failed
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
IssueYou are unable to deploy a workflow and this error appears:
"SmartObject Server Exception: Could not publish SmartObject Definition to server: Error refreshing Service Instance 'WorkflowReportService'. Service returned: 'Workflow Reporting SO Service': Communication with the underlying transaction manager has failed"
SymptomsThis error generally points to DTC. The troubleshooting steps below should help determine whether or not the error is due to a misconfiguration on this component.
- Check if the K2 server and SQL server hosting the K2 database has DTC configured as per the following documentation.
- Verify if DTC and its port is opened if the firewall is active. You may refer to this documentation on K2 and Firewalls.
- Use the DTCPing tool to test the connection between your servers outside the context of K2. You may download the tool here.