After a failed slave node installation, a manual cleanup is required before the installation can be re-attempted. 

The resolution section lists the steps to perform this manual cleanup. 

Cleanup a failed slave node installation on Windows

All supported Windows operating systems

1. Shutdown any running processes on the slave node. 

In task manager, check for pmsvc.exe / procmgr.exe

2. Remove the slave node from the cluster, if it was added - 

-- command to check if the server was added to the database
swadm show_servers

-- command to delete the slave node
swadm delete_server <machine_name>

3. Remove services - 

From services.msc, note down the Service Names and use the below commands to delete (ensure you are in an elevated command prompt) - 

sc delete "NobleNet Portmapper for TCP"
sc delete "iProcess[nodename]ProcessSentinels"
sc delete "iProcess[nodename]AdminConsole"

4. Remove the node-specific registry keys under - 

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Staffware plc\Staffware Server\Nodes
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Staffware plc\Staffware EntObj Server\Nodes

For 11.8.0 and above, these registry keys are changed to - 

HKEY_LOCAL_MACHINE\SOFTWARE\TIBCO iProcess\TIBCO iProcess Engine\Nodes
HKEY_LOCAL_MACHINE\SOFTWARE\TIBCO iProcess\TIBCO iProcess Objects Server

5. Stop and delete the COM+ Applications - 

Staffware Events64
Staffware EAI COM Bridge64

6. Unregister dlls, if they exist under C:\Windows\System32 or SysWow64 - 

regsvr32 /U SWEAICOMBridge.dll
regsvr32 /U SWEntObjScCfg.dll
regsvr32 /U SWEventClass.dll
regsvr32 /U SWEventClassSubscriber.dll

7. Delete SWDIR

8. Remove any entries added in \etc\services or \etc\hosts