My team encountered this issue. (and my colleague Julius Soestrisno manage to find the solution). If you encounter this issue, make sure that you disable the symantec backupexec if it's running on the portal server
PortalExpress.install,com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:[wsadmin] WASX7017E: Exception received while running file "D:\IBM\PortalExpress\PortalServer/config/was/wmm_SecurityConfigWmmUR.jacl";exception information: com.ibm.bsf.BSFException: error while eval'ingJacl expression:
PortalExpress.install,com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:[wsadmin] invalid command name "checkUidPw"
PortalExpress.install,com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:[wsadmin] while executing
PortalExpress.install,com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:[wsadmin] "checkUidPw"
This is due to port conflict with Port 10000 used by BackupExec and by Portal during Security Enablement. Portal 10000 is used by Portal Installer during Security Enablement. Not sure why, but when you encounter this, make sure that you check if BackupExec is enabled.
Subscribe to:
Post Comments (Atom)
-
So we have an EC2 instance on AWS. But we need to terminate it as the project has to give way to something urgent and therefore not on for... -
When updating MacOS High Sierra, you may experience this issue, where a couple of hours, you will be presented with an error Disk Management...
No comments:
Post a Comment