Unable to manage Kanaka after installing second Kanka engine

After installing Kanaka on a second server, Kanka administration is no longer possible on the first server.

To fix this, simply run the setup wizard again. On the server where you want the second incidence to run, stop the engine, go to /etc/opt/novell/kanaka/engine/config and rename the kanaka.conf file and restart the kanaka engine.  Then go to the kanaka admin page and it will start the setup wizard.  Keep all information the same, except for the proxy user. It must have a unique name.

The issue is caused by the proxy user for the second server overwriting the proxy user password for the first server. Each server instance must have it's own proxy object.

According to documentation:

IMPORTANT: You can have multiple Kanaka Engines in the same eDirectory tree. To do so, you
must select or create a separate Kanaka proxy object for each server instance in Step 2 of the Setup
Wizard.
This is important because each instance of a Kanaka Engine sets a different password for its Kanaka
proxy object. If you use the same Kanaka proxy object for each Kanaka Engine, upon completion of
the Setup Wizard, the new instance of the Kanaka Engine overwrites the current password for the
object in eDirectory. This results in failures to perform operations for the Kanaka Engine instance that
was initially configured for the proxy object.