Name: PK30303 ============= Summary: The 5103 upgrade task fails if additional classloaders exist. Problem Description: The fixpack install will break with the following error, if you have specified two classloaders: [wsadmin] WASX7017E: Exception received while running file "C:\Program Files\WebSphere\PortalServer/config/was/LibraryRemove.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7080E: Invalid attributes specified for type "Classloader" -- "libraryName" Problem Solution: The config code breaks if two classloaders for the server WebSphere_Portal exist. The PK fixed this problem. Note: You need to install the PK between the install step of fixpack 5103 and the configuration task CONFIG-WP-PTF-5103. Failing Module(s): Configuration Affected Users: All Version Information: Portal Version(s): 6.0.0 Pre-Requisite(s): Co-Requisite(s): --- Platform Specific: This fix applies to all platforms. Installation: NOTE: YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Portal Update Installer can be downloaded from the following link: http://www.ibm.com/software/genservers/portal/support 1. Install 5103 fixpack till step 8 in the following description: http://publib.boulder.ibm.com/infocenter/wpdoc/v510/topic/com.ibm.wp.ent.doc/wpf/pui_install5101to5103.html#pui_install5101to5103__mpinst 2. After step 8 please install this PK30303: 3. Create temporary "fix" directory to store the jar file. 4. Copy jar file to this directory. 5. Shutdown WebSphere Portal. 4. Follow the fix installation instructions that are packaged with the Portal Update Installer on how to install the fix. 5. Restart WebSphere Portal. 6. The temporary directory may be removed. 7. Please continue the fixpack installation beginning with step 9. Un-Installation: NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. 1. Shutdown WebSphere Portal. 2. Follow the instructions that are packaged with the Portal Update Installer on how to uninstall the fix. 3. Restart WebSphere Portal.