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.

Issue

During a K2 Blackpearl deployment, an error occurs: 

"System.Reflection.TargetInvocationException: The "SourceCode.DeploymentTasks.ExportProcessTask" task failed unexpectedly. System.Net.Sockets.SocketException (0x80004005): 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 (IP ADDRESS: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__26.MoveNext() ---> System.Exception: C:\ProgramData\Temp\c897c680f86647f6a7b6446c87cd575b\Deployment\CR1.msbuild(98,5) : error MSB4018: The "SourceCode.DeploymentTasks.ExportProcessTask" task failed unexpectedly. "

Symptoms

This error occurred after a 4.6.11 database was moved to a new environment and upgraded to 4.7.
From the error message it was confirmed that the IP in the error was listing the old environment.

This seems to indicate that the old servers details are still cached or referenced somewhere.

Resolution

After investigating in K2 Management we confirmed that all the values of the old server (pre K2 4.7 upgrade) were utilized in the connection strings.

This is due to the K2 4.6.11 database being moved to a new server to ensure environment prerequisites were met for the K2 4.7 upgrade.

To resolve this, remove all the old connection strings and run a K2 reconfigure to update the values.

You will now be able to deploy successfully.