K2ClusterServer::CheckRunning: Could not connect to EPIC05

  • 24 October 2008
  • 3 replies
  • 1 view

Badge +1

Hi Everyone,


I am running K2 2003 SP2 on 2003 Standard Edition.


I have opened up the service manager and attempted to view the properties on my server in the list and I recieved the message ""


I then opened up the k2error.log file and this is what is in there:


24-10-08 08:12:38    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:12:54    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:13:10    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:13:26    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:13:42    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:13:58    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:14:14    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:14:30    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:14:46    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:15:02    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:15:19    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:15:34    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:15:51    K2ClusterServer::CheckRunning: Could not connect to EPIC05
24-10-08 08:16:07    K2ClusterServer::CheckRunning: Could not connect to EPIC05


I have searched all I could on this site and have found nothing. Can anyone help?


 


Thanks,


 


Xavier.


3 replies

Badge +1
Sorry... The message I recieve in the K2 Service Manager is "Authentication with server failed"
Badge +1
I have discovered that setting the k2 server registration properties to NTLM that it no longer causes this error, however I need it to run under kerberos
Badge +11

Possibly K2 DB has references to old/decomissioned server. See details here: http://community.k2.com/t5/K2-blackpearl/Error-28039-quot-Could-not-connect-to-SERVERNAME-quot-in-K2-host/ta-p/79840

Reply