Skip to main content


 

Symptoms

 


There are errors about processes trying to connect to an old K2 server, however they are not listed in the instances of the process. It's like these error entries are somehow orphaned.
 

 

Diagnoses

 


The problem is that the right deletion process hasn't been executed, the K2 Server should be doing a cleanup of entries involved if an Instance is Deleted/Completed. However, the procedures would differ depending on how the Deletion/Completion is accomplished. In this case server destinations changed and the cleanup hasn't been done.
 

 

Resolution

The following SQL commands resolved the issue:

UPDATE /K2].AServer].[ipc]
SET bDstServer] = 'NEWK2SERVER',2DstConStr] = 'Integrated=TrueIsPrimaryLogin=TrueAuthenticate=TrueEncryptedPassword=FalseHost=NEWK2SERVERPort=5252'
GO

UPDATE /K2].AServer].[IPCReturn]
SET bSrcServer] = 'NEWK2SERVER'
WHERE SrcServer] = 'OLDK2SERVER'
GO

OLDK2SERVER: Change in the script to the server where the databases were originally pointing to.
NEWK2SERVER: Change to the name of the K2 server where the databases are currently restored to point to.

 

 



 
Be the first to reply!

Reply