Symptoms

K2 blackpearl Setup Manager is stuck waiting on another node in the farm. K2 blackpearl Setup Manager is stuck waiting on another node in the farm. The 2nd node is stuck waiting on the first node and the first node isn't doing anything.
 

Diagnoses

When the configuration gets interrupted sometimes it sets the flag in the database and can't move on.
 

Resolution



1. Added a hostheader to the K2 Site in IIS.
2. Ran a Repair on Node 2 since it got stuck configuring it and some kind of flag was set on the database that wouldn't let us configure Node 1
3. input the Web Cluster host name for Workspace. Select the correct binding fro the K2 Site.
4. Finish the Installation on Node 2.
5. Add the host header to the IIS K2 Site on node 1.
6. Ran the Setup manager from the Installation package on Node 1 and select configure. This time the Distributed Installation error didn't showed up.
7. Select the correct Binding on the Workspace configuration screen.
8. Finish the Installation.
9. Edit the K2HostServer.exe.config and change the Autodiscover port to 49600 it was on 49559 (Single Install).

Got some issues on Node 2 trying to connect to Node 1 but it was due to an expired licensed. After updating the correct one everything worked as expected.