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

After reconfiguration of K2 on a new server it was found that all running instances were raising an error and not completing.

Symptoms

After reconfiguration of K2 on a new server it was found that all running instances were raising an error and not completing. It seemed from the instances in error that connection to the old server was being initialized and could be established.

Resolution

After investigating to see what values the error instances had in the [Server].[IPCReturn], we found that these were still pointing to the old server under the SrcServer.

If this is the case, please log a support ticket. Database modification will be necessary and should only be done with the assistance of a support agent.

Do not modify any database definition or database content unless specifically instructed to do so by K2. No changes to the K2 Database definition or content are supported unless specifically instructed by K2. 
Direct read access or modification of the data in the K2 database is also not supported, unless specifically instructed by K2, except for the ServerLog table where direct read access is supported.  Please see: https://help.k2.com/onlinehelp/k2blackpearl/devref/current/default.htm#Database_Reference.html