Recovering from a fix pack installation that failed due to insufficient space on the file system
 Technote (FAQ)
 
Problem
If you use the UpdateInstaller to install a fix pack on a UNIX® system and run out of file space in the installation directory during the installation, you could see the following error:

An unhandled error occurred that has prevented wizard bean "PTFSelect" from displaying
 
Cause
After UpdateInstaller starts, at the Scanning for installable fixpacks screen, the following error occurs:

An unhandled error occurred that has prevented wizard bean "PTFSelect" from displaying:

java.lang.NullPointerException
at com.ibm.websphere.update.ismp.ptf.util.TableMap.setModel
(TableMap.java:61)
at com.ibm.websphere.update.ismp.ptf.panels.PTFSelectionPanel.
initializeTableListing(PTFSelectionPanel.java:176)
at com.ibm.websphere.update.ismp.ptf.panels.PTFSelectionPanel.
initialize(PTFSelectionPanel.java:116)
at com.installshield.wizardx.panels.ExtendedWizardPanel.createUI
(ExtendedWizardPanel.java:80)
at com.ibm.websphere.update.ismp.ptf.panels.PTFSelectionPanel.
createUI(PTFSelectionPanel.java:239)
at com.installshield.wizard.WizardPanel.initializeComponent
(WizardPanel.java:117)
at com.installshield.wizard.awt.AWTWizardUI.currentBeanChanged
(AWTWizardUI.java:1268)
at com.installshield.wizard.StandardWizardListener.
currentBeanChanged(StandardWizardListener.java:78)
at com.installshield.wizard.Wizard$RunThread.run(Wizard.java:1535)



When your file system fills to 100%, UpdateInstaller can no longer update any WebSphere® Application Server files or logs. Therefore, some WebSphere Application Server version files might be corrupt.

This error also occurs if installation is stopped by stopping the Java™ process.

 
Solution
Check the fix pack installation logs for the component that failed. Verify that the file of any failed component is complete in the following location:

Install_Root/properties/version directory.
  1. Check the event.history file located in:
    Install_Root
    /properties/version/history.

    There could be missing closing statements at the bottom of the file. For every opening statement, there is a closing statement. The following three lines might need to be added at the end of the file.

        </update-event>
     </update-event>
    </event-history>

    Also check the last event that occurred in the event.history file. It might be missing information entries.
  2. If the failed installation was updating the Base version, for example version 5.0 or 5.1, move the Install_Root/version/history directory and all files under that directory to a backup location, then try the fix pack installation again.
  3. If you are unable to determine what is missing from the version files, the best thing to do is manually uninstall WebSphere® Application Server. Then verify that your file system has sufficient free space, and perform a complete reinstallation.
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Install
Operating system(s): Solaris
Software version: 5.0.x
Software edition:
Reference #: 1175732
IBM Group: Software Group
Modified date: Aug 30, 2004