I encountered this error when installing a 64 bit version of K2Blackpearl and pointing to an existing set of databases the error would repeat every 30 seconds or so in console mode, this is what showed up in the host log:

"22200","2008-11-12 10:06:03","Error","General","28039","CouldNotConnect","K2ClusterServer.CheckRunning","28039 Could not connect to [OldServerName]","anonymous","0.0.0.0","[NewServerName]:C:Program Files (x86)K2 blackpearlHost ServerBin","22200","661efcc16669467c8dd1c5bb72ffcdac",""

 The solution was to go into the K2Server database, open up the _Server table and locate any reference made to the old BlackPearl server (in my case the 32 bit server)  Once that record was removed from the table the problem disappeared.

 

 

Hi,

We encounter it also, sometimes it also in different server setup, in my case, we have two k2 service server with only 1 database server, if the other k2 service is down then it will throw that error. so if you encounter this verify first if the other k2 service is running.

Error normally caused by the reference to old server which is no longer available (you saying that you restore/use existing K2 DB, so it contains references to some old server, right?). Please refer to the following community KB for details on how to fix this:

http://community.k2.com/t5/K2-blackpearl/Error-28039-quot-Could-not-connect-to-SERVERNAME-quot-in-K2-host/ta-p/79840