DSXchange

Hello All,

IS Version : Information Server 11.5.0.1.
Microsoft Windows OS for the IS Client: Window XP, Windows Server 2003 and windows7
Operating System version : Red Hat Enterprise Linux Server release 6.6

Below is the summary of the issue and please let us know if any additional information required.

Problem: Information Server services tier install on WebSphere Application cluster server failed with an error: CDIIN5123E: ExecuteScriptAction failed: the process returned error code 4.:

Description : We are trying to install Information server on existing WAS Cluster Application server. While doing the installation we are getting the errors below:

SEVERE: com.ibm.is.install.engine.runtime.InstallEngine
com.ibm.is.install.exception.ActionException: CDIIN5123E: ExecuteScriptAction failed: the process returned error code 4.:

CDIIN5106I: Details:
InstallAction (_id = update.client.cert, _installUnitModelId = ISFServer)
at com.ibm.is.install.engine.action.builtin.AbstractExecuteAction.execute(AbstractExecuteAction.java:335)
at com.ibm.is.install.engine.runtime.InstallEngine.executeAction(InstallEngine.java:1598)
at com.ibm.is.install.engine.runtime.InstallEngine.processInstallActionStep(InstallEngine.java:1538)
at com.ibm.is.install.engine.runtime.InstallEngine.processActionStep(InstallEngine.java:1422)
at com.ibm.is.install.engine.runtime.InstallEngine.processInstallStep(InstallEngine.java:587)
at com.ibm.is.install.engine.runtime.InstallEngine.processAllSteps(InstallEngine.java:567)
at com.ibm.is.install.engine.runtime.InstallEngine.run(InstallEngine.java:245)
at com.ibm.is.install.engine.runtime.InstallEngine.execute(InstallEngine.java:883)
at com.ibm.is.install.atlasinstaller.ui.control.InstallEngineMonitor.execute(InstallEngineMonitor.java:368)
at com.ibm.is.install.atlasinstaller.ui.control.InstallEngineMonitor.beginInstall(InstallEngineMonitor.java:252)
at com.ibm.is.install.atlasinstaller.ui.control.InstallEngineMonitor.access$100(InstallEngineMonitor.java:40)
at com.ibm.is.install.atlasinstaller.ui.control.InstallEngineMonitor$1.run(InstallEngineMonitor.java:119)
at java.lang.Thread.run(Thread.java:809)

Can you please let me know how to deal with this error?

Regards
Venkat

Sorry, but you'll have to contact IBM Support. There isn't any documentation that tells us what an "Error Code 4" is and how to rectify it.

However, in general, I will state that the IIS installation instructions need to be followed very carefully to setup the cluster and then install the Services Tier. Twice I've worked with WebSphere admins that decided that to setup the cluster "their way" and ignored the IIS setup instructions. In both cases the installation failed and they had to rip out the cluster and create it with IBM's instructions. After that it worked.

Thanks Andy,

Yes, We contacted IBM support team and they suggested us to start all WebSphere application server services as root id. We changed ownership of the WAS services from wasadm ID (dmgr,nodeagents) to root ID and re-installed it.
IIS was installed successfully in services tier without any issues.

Many thanks, Venkat.

Yes - I always install as root, then use the published procedures to switch to a non-root id afterwards. That works like a champ if you want to switch back to wasadm at this point.

Configuring WebSphere Application Server for non-root administration (Linux, UNIX)
http://www.ibm.com/support/knowledgecen ... admin.html