Symptoms
Second server in farm Workspace won't open. We are trying to add a second server to a farm and whenever we do so we no longer able to open Workspace. It will sit there and spin and does not load.
Diagnoses
Apply the recommended settings for K2 farm load balancing
Resolution
During our online meeting, we added a hosts file entry on the non-working K2 Workspace node (i.e. 127.0.0.1 k2.denallix.com) as well as change the binding for the K2 web application to use the load balanced FQDN and to match the working node workspace now successfully load from a client machine. Usually the following are recommended:
1. 'Disableloopbackcheck' registry key or its equivalent implemented on the K2 Workspace server and Sharepoint WFEs:
http://support.microsoft.com/kb/896861
2. Hosts file entries on the K2 Workspace servers and Sharepoint WFEs using the loopback address when using "All Unassigned" IP address bindings:
i.e. 127.0.0.1 k2.denallix.com
* the hosts file is usually located a "C:WindowsSystem32driversetc"
3. Regarding the Workspace rendering issues, please see the KB article belows:
http://help.k2.com/kb001578
