Typical errors when ports are not configured correctly

This topic is intended as a quick reference to the ports commonly used in a K2 implementation. If firewalls exist between the servers in a K2 environment, between K2 and the systems it integrates with, or between K2 servers and client machines that connect to K2, you may need to open ports in Firewalls to allow network traffic to flow between these machines. You can use the guide below as reference.

Problem Area Error Message Likely Causes
SmartObject deployment (including during process deployment) SmartObject Server Exception:
Could not publish SmartObject definition to server: Error refreshing Service Instance 'WorkflowReportingService'. Service returned : 'Workflow Reporting SO Service: Communication with the underlying transaction manager has failed.

Firewall or MSDTC configuration.
SmartObject Server Exception:
Could not publish SmartObject definition to server: Error refreshing Service Instance 'SmartBoxService'. Service returned : 'Unable to connect to the Database.Communication with the underlying transaction manager has failed.
Dependency could not be created:
System.Transactions.TransactionManagerCommunicationException: Communication with the underlying transaction manager has failed. ---> System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
Dependency could not be created:
System.Transactions.TransactionManagerCommunicationException: Communication with the underlying transaction manager has failed. ---> System.Runtime.InteropServices.COMException (0x8004D02B): The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. (Exception from HRESULT: 0x8004D02B)		 MSDTC was unreachable on the other machine. If consistent, probably NetBIOS resolution or firewall or MSDTC security settings.
SmartObject Server Exception:
Could not publish SmartObject definition to server: Error refreshing Service Instance "WorkflowReportingService". Service returned : "Workflow Reporting SO Service: The partner transaction manager has disabled its support for remote / network transactions. (Exception from HRESULT: 0x8004D025)		 Network DTC access not enabled on SQL server / cluster.
SmartObjects Services Tester VALIDATION A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Source: SourceCode.SmartObjects.Services.Management

 Firewall or SQL configuration.
Host Server Log K2Sql::UpdateLogUsers,1 Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

The statement has been terminated.
Central Administration / Activate Components A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.10:5555 Port 5555 and / or 5252 not open between SharePoint and K2.
No such host is known.
SharePoint web application, Central Administration, Workspace, etc. Unable to connect to K2SERVER on port 5252.

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

 Firewall, DNS, K2 service not running.
K2 Studio Object Browser The following errors occurred while connecting to the Environment library:
No connection could be made because the target machine actively refused it
No response from host. Make sure that:
  • the K2 server is running on the target machine,
  • the target machine is accessible from the network and
  • a firewall is not blocking the K2 server from communicating with the network.
K2 Setup Manager (any component except K2 server) Connection Failed. Firewall blocking connection to SQL, install account has read permissions on DB.
Management Console Other K2 servers not visible. Discovery service not running, on different port, or firewall blocking 45999/46000.

You may also want to refer to the following resources for further configuration information and troubleshooting resources: