Troubleshooting: WebSphere Commerce feature pack install or uninstall failed
Review this information if the installation or uninstallation of a WebSphere Commerce feature pack fails.
Problem
Attention: Installing Feature Pack 1 using Installation
Manager 1.4, requires an Interim Fix. For more information, see Interim Fix (iFix).
The install or uninstall of the WebSphere Commerce feature pack failed.
Solution
If the install or uninstall failed, the Summary page of the installation wizard displays the log file location.
The log file locations for the install: WC_installdir/logs/FEPX/install
The log file locations for the uninstall: WC_installdir/logs/FEPX/uninstall
Where X is the feature pack number that you have installed or uninstalled.
If
the log file indicated by the installer does not exist, or the installer
indicates the following log file location: null/logs/FEPX/install/log.txtyou
can find the logs in the following location:
Where X is the feature pack number that
you have installed or uninstalled and user is the
user profile of the user who is installing or uninstalling the WebSphere
Commerce feature pack. - /fepX_install_logs/log.txt
- /root/fepX_install_logs/log.txt
- /home/user/fepX_install_logs/log.txt
Fix the errors indicated in this log file
and run the installation or uninstallation again.
Note: When you install
or uninstall, ensure you have the appropriate privileges:
- Log on:
- As a root user
- Or as a non-root user that owns WC_installdir
- If you want
log on as a non-root user, ensure that the non-root user owns the appropriate
.profile file and consider the following installation limitations.
- Feature packs that are installed by a non-root user cannot be registered through native operating system mechanisms, such as the Red Hat Package Manager (RPM) on Linux. WebSphere software registers in the installation registry file and the vpd.properties file. All installed components are fully functional despite the lack of native registration.
- Feature packs installed by the root user must be uninstalled by the root user only.
- Log on as the
root
user. - If the directory /tmp/niflog/ exists, create a backup and then remove the directory.
- Change the ownership of /home/non-root_userdir/.profile
to
non-root
user and thenon-root
user group. For example, change ownership of /home/wasuser/.profile towasuser
andwasgroup
. - Set the non-root user's umask to 0027.
- Log on with a user profile
that has
*SECOFR
authority. - Log on to a user that has Windows Administrative user rights.