Conflict Resolution

If you see something similar to: -

(Sep 7, 2007 2:11:50 PM), PortalExpress.install,
com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
[wsadmin] WASX7017E: Exception received while running file "C:\Program
Files\IBM\PE\PortalServer/config/was/wmm_SecurityConfigWmmUR.jacl";
exception information: com.ibm.bsf.BSFException: error while eval'ing
Jacl expression:
(Sep 7, 2007 2:11:50 PM), PortalExpress.install,
com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
[wsadmin] invalid command name "checkUidPw"
(Sep 7, 2007 2:11:50 PM), PortalExpress.install,
com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
[wsadmin] while executing
(Sep 7, 2007 2:11:50 PM), PortalExpress.install,
com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
[wsadmin] "checkUidPw"

during an installation of WebSphere Portal Express 6.0, then the problem
MAY be due to a port conflict.

I saw this yesterday, where Symantec BackupExec was listening on port
10000, which the WebSphere Portal installer uses ( it's actually used by
the server1 instance which is started during the Enable Security phase ).

Once we temporarily suspended the BackupExec service and performed a
clean installation ( having uninstalled fully, removed VPD.PROPERTIES,
empty folders etc. ), the installation completely normally.

Being a typical techie, I also made two or three other changes prior to
the installation ( renamed the installation images to W-Setup, W-1 etc.
) and installed into C:\WebSphere rather than C:\Program Files. However,
my money (£££) is on the port conflict, knowing that WebSphere will try
and use it.

If in doubt, use NETSTAT -AN | FIND "LISTENING" to see what's going on
BEFORE you do the installation. Additionally, or alternatively, use the
TCPView utility from SysInternals at: -

http://www.microsoft.com/technet/sysinternals/default.mspx

Thanks to Chris for his patience and hospitality ( and copious amounts of coffee and water )

Have fun