Failed to install HCL Connections Docs due to incorrect cluster configuration

Troubleshoot the failure to install HCL Docs due to incorrect cluster configuration.

Problem

Installing HCL Docs components fails when creating the work manager:
2015-05-17 13:43:24,842 INFO -->IM:AddWorkManager 
2015-05-17 13:43:24,842 DEBUG >>>>entering docs.add_workmanager.AddWorkManager.readCfg 
2015-05-17 13:43:24,842 DEBUG <<<<exiting docs.add_workmanager.AddWorkManager.readCfg  
2015-05-17 13:43:24,842 DEBUG >>>>entering docs.add_workmanager.AddWorkManager.precheck 
2015-05-17 13:43:24,842 DEBUG <<<<exiting docs.add_workmanager.AddWorkManager.precheck
2015-05-17 13:43:24,842 DEBUG >>>>entering docs.add_workmanager.AddWorkManager.do 
2015-05-17 13:43:24,842 INFO Creating work manager: ConcordWorkManager 
2015-05-17 13:43:37,618 ERROR Exception thrown while executing WebSphere command:WASX7209I: 
Connected to process "dmgr" on node connectionsCellManager using SOAP connector;  The type of process is: DeploymentManager 
WASX7303I: The following options are passed to the scripting environment and are available as arguments 
that are stored in the argv variable: "[/ServerCluster:ClusterDocs/, ConcordWorkManager, com/ibm/concord/workmanager,
2, 5, 50, 5, workTimeout=150000,workReqQSize=70,workReqQFullAction=0,isGrowable=true]" 
[2015-0517-1343-3700] enableDebugMessages Verbose trace messages are now enabled; future debug messages will now be printed.    
---------------------------------------------------------------
AdminResources: Create a work manager at scope 
Scope: 
scope                        /ServerCluster:ClusterDocs/
Work manager:
name                         ConcordWorkManager 
JNDI name                    com/ibm/concord/workmanager 
number alarm threads         2 
min threads                  5 
max threads                  50 
thread priority              5 
WorkManagerProvider ID        
Optional attributes: 
otherAttributesList:  workTimeout=150000,workReqQSize=70,workReqQFullAction=0,isGrowable=true 
description  
category  
daemonTranClass  
defTranClass  
isDistributable  
isGrowable  
providerType  
serviceNames  
workReqQFullAction  
workReqQSize  
workTimeout  
referenceable (Referenceable config id)  
Usage: AdminResources.createWorkManagerAtScope
("/ServerCluster:ClusterDocs/", "ConcordWorkManager", "com/ibm/concord/workmanager", "2", "5", "50", "5", "", 
"workTimeout=150000,workReqQSize=70,workReqQFullAction=0,isGrowable=true") 
Return: The configuration ID of the created Work Manager in the respective scope 
--------------------------------------------------------------- 
Exception: exceptions.AttributeError WASL6041E: The following argument value is not valid: wmProviderID:.  
WASX7017E: Exception received while running file "./docs/tasks/add_workmanager.py"; 
exception information: com.ibm.bsf.BSFException: exception from Jython: 
Traceback (innermost last):
File "<string>", line 58, in ? 
File "<string>", line 33, in createWorkManager  
File "C:\WebSphere\AppServer\scriptLibraries\resources\Provider\V70\AdminResources.py", line 3568, in createWorkManagerAtScope
ScriptLibraryException: : 'exceptions.AttributeError WASL6041E: The following argument value is not valid: wmProviderID:.' 
2015-05-17 13:43:37,618 INFO Exception: Do failed for command: {'cfg': {'isGrowable': 'true', 'maxThreads': 
'50', 'name': 'ConcordWorkManager', 'threadPriority': '5', 
workReqQFullAction': '0', 'workReqQSize': '70', 'workTimeout': '150000', 'jndiName': 
'com/ibm/concord/workmanager', 'minThreads': '5', 'numAlarmThreads': '2'}, 
class': 'docs.add_workmanager.AddWorkManager'} 
2015-05-17 13:43:37,618 INFO -->IM:ERROR:Traceback (most recent call last): 
File "C:\temp\DocsApp\installer\common\commands\command.py", line 197, in exec_commands _do(cmd, cmd_instance) 
File "C:\temp\DocsApp\installer\common\commands\command.py", line 110, in _do raise Exception
("Do failed for command: " + str(cmd)) 
Exception: Do failed for command: {'cfg': {'isGrowable': 'true', 'maxThreads': '50', 
'name': 'ConcordWorkManager', 'threadPriority': '5', 'workReqQFullAction': '0',
'workReqQSize': '70', 'workTimeout': '150000', 'jndiName': 'com/ibm/concord/workmanager', 
'minThreads': '5', 'numAlarmThreads': '2'}, 'class': 
docs.add_workmanager.AddWorkManager'} 
2015-05-17 13:43:37,634 ERROR Error while executing command, now rollback previous changes...      

Cause

The configuration of the target cluster is not correct, for example, no server is configured in the cluster.

Resolving the problem

If you are installing using scripts, remove the old cluster and servers, and then create a new one. If the cluster name has changed, update cfg.properties accordingly. Then, rerun the script installer.

If you are using the installation program (wizard), remove the old cluster and servers, and rerun the wizard. Make sure that the server name used in the wizard is not the same as that of any existing cluster on the same node.