+44(0)1908 545 770
YOUR EXPERT RPA PARTNER

Team up with our RPA strategy and tech specialists for maximum automation impact

Find out more
Harness the power of UiPath in your business.
WATCH NOW

Save money and spend more time on priority work.

Book consultation
READY, SET, AUTOMATE

Let's choose, design and deploy a process automation solution for your business.

Find out more
TRANSFORM YOUR BUSINESS

Let's analyse your business to discover opportunities for innovation and automation.

Find out more

Begin your business transformation journey

Book consultation
AUTOMATE EVERY FUNCTION

Automate where it matters most. Scale to solve challenges in every area

Find out more
GIVE EVERY TEAM THE TOOLS FOR SUCCESS

Equip people with user-friendly solutions that save time and make work easier

Find out more

Which business problem
can we solve first?

Book consultation
31 January 2016

K2 Server stuck in Starting state

When you open your K2 designer in the web browser you often get confronted with an error indicating that no connection could be made because the target machine actively refused it.

k2 server stuck - K2 Server not running

K2 Automated Testing Software

BenchQA allows full test automation of K2, including fully automated K2 SmartForms and K2 Workflow testing. It promotes test driven development for K2 and ensures continued quality assurance for K2 solutions. Easily apply changes to test cases to accommodate changes to K2 apps and ensure all apps are regression tested to avoid defects and assure continuous quality.

 

Free K2 Five Upgrade Review

This is usually because you have not started the K2 Server, but occasionally that is not the case. It could also be that you have started the server, but that it is stuck in a starting status, as you would be able to see by opening services.msc.

k2 server stuck - K2 Server Starting state

The most likely cause for this is that your SQL Server has not been started.

k2 server stuck - SQL Server not started

To solve the issue in this scenario, first start your SQL Server (and SQL Server Agent).

k2 server stuck - SQL Server Running

Once these service are running, you need to kill the K2 blackpearl Server service. To accomplish this you first need the process id (pid) of the service, which you can retrieve from the Service Tab in Task Manager.

k2 server stuck - Identify K2 hostser process

Once you have noted this id (1176 in this case), open command prompt as an administrator, and execute the following command:

k2 server stuck - K2 process Taskkill

Now return to services.msc, and start the K2 blackpearl Server again. Given that everything else is functioning as it should you should now once again be able to connect to the server.

Need further technical advice or support?