This topic describes known problems and issues associated with the Update Installer for WebSphere Software program.
The update installer program displays its version information in the title bar of the graphical interface. Version information is stored in the version.txt file in the updateinstaller directory.
A new version might ship to correspond to any new fix. Information in the version.txt file is displayed prominently in the title bar of the wizard and is also recorded in the updatelog.txt file.
Always download and use the latest version of the Update installer wizard when installing an interim fix.
Description of problem | Workaround | Version with resolution |
---|---|---|
Product uninstall does not remove the updated product correctly. | Product uninstall | Current problem |
Relaunch action for SDK updates does not relaunch the
update installer.
|
Relaunch fails | Current problem |
Problem: The product uninstaller for Version 6.0.x.x cannot delete all files and directories that exist after installing a refresh pack or a fix pack.
Description: If you apply a refresh pack or a fix pack using the update installer program and then uninstall the whole product using the Version 6.0.0.0 product uninstaller program, many files are left on the system.
Cause: The product uninstaller program will be fixed in a later release.
Problem: The update installer program cannot launch a second ISMP process that uses the cloned copy of the SDK in the install_root/updateinstaller/java directory.
install_root /updateinstaller /java
After copying the SDK, the update installer program stops the first ISMP process and launches a second process that uses the SDK in the install_root/updateinstaller/java directory.
Cause: The update installer program will be fixed in a later release.
Customer action: If this problem occurs, launch the update installer program again. The update installer program uses the cloned copy of the SDK in the install_root/updateinstaller/java directory if the copy is present.
Related tasks
Applying service