K2 Blackpearl configuration problem

So we are taking advantage of the new year to ensure all of our servers are patched up. As we patched our SQL Servers (SQL Server 2005 SP3), we started getting the following error from our application servers (both SharePoint WFE and K2 Blackpearl app servers).

Unable to connect to SERVERNAME on port 5252. No connection could be made because the target machine actively refused it.

I immediately start looking at the SQL Server, and everything is working as it should be. Since I’m running into a wall, I drop down to the network level. Port 5252 isn’t open on my server. OK, I checked to see that the service is running, and it is. Why isn’t it listening?

I turn on logging by

  • opening C:\Program Files\K2 blackpearl\Host Server\Bin\HostServerLogging.config
  • Going to
     applicationlevellogsettings ... loglocation name="FileExtension"
  • Change the Active to “True” and LogLevel to”All”
  • Restart the K2 Service

A new log file is available in C:\Program Files\K2 blackpearl\Host Server\Bin\. I open it up and find the culprit.

1046 Expired K2 [blackpearl] - Partner Software License Key: KEYNUM

Ahhh, and I was thinking it was the patching we were doing. Sometimes you just have to look at the logs.

Leave a Reply

Name *
Email *