Workflow failed to deploy with error:The "SourceCode.DeploymentTasks.ExportProcessTask" task failed unexpectedly" appearing
kbt137432
PRODUCTK2 blackpearl 4.7
BASED ONK2 blackpearl 4.7
TAGSDeployment
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.
LEGACY/ARCHIVED CONTENT
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.
Issue
After deploying a K2 Workflow package, the following error appears:
"The "SourceCode.DeploymentTasks.ExportProcessTask" task failed unexpectedly. System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 10.200.254.253:5555 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at System.Net.Sockets.Socket.Connect(IPAddress address, Int32 port) at SourceCode.Hosting.Client.BaseAPI.SocketBaseAPIConnection.OnOpen(SCConnectionStringBuilder connectionStringBuilder) at SourceCode.Hosting.Client.BaseAPI.BaseAPIConnectionBroker.OnOpen(SCConnectionStringBuilder connectionStringBuilder) at SourceCode.Hosting.Client.BaseAPI.BaseAPIConnection.Open(String connectionString) at SourceCode.DeploymentTasks.ExportProcessTask.CheckServerFrameworkSupport(Version targetFramework) at SourceCode.DeploymentTasks.ExportProcessTask.Execute() at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.d__20.MoveNext()"
Symptoms
This issue could be caused by the Environment library fields pointing to the wrong server.Troubleshooting Steps
Check the 'Workflow Server' and 'SmartObject Server' fields in K2 Management, and ensure that the Host value is pointing to the correct server.