WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Troubleshoot WebSphere Portal Express installation

 

+

Search Tips   |   Advanced Search

 

  1. User wpdb2ins already exists
  2. Installation fails when logging in using NLS characters
  3. Wizard default language does not match language locale
  4. Insufficient credentials to stop the administrative server
  5. Installation directory path cannot contain National Language characters
  6. The WebSphere Portal Express Version 6.0 installation program dependency checker does not recognize any interim fix installation on WAS V6.0.2.9, 6.0.2.11 or 6.0.2.13
  7. Change to make if IBM HTTP Server and WAS plugin installed
  8. Receive EJPIC0034E: unexpected service exception message
  9. Information on WebSphere Portal Express Version information and History information
  10. Java processes continue to run
  11. Setup program fails to run
  12. General steps to perform if the installation fails
  13. Reinstall after a failed installation
  14. Installation fails after uninstalling a previous copy of WebSphere Portal
  15. Receive Permission denied error when attempting to install on Linux
  16. Search Collections are not removed during an uninstall
  17. ICM exceptions occurs during portal startup after 6.0.0.1 or 6.0.1 uninstall
  18. Installation fails due to path problem
  19. Non ISO-8859-1 characters not supported in installation path
  20. Console mode installation not available for bidirectional languages
  21. Installation fails due to insufficient disk space
  22. Desktop display width doubles when running installation program
  23. Some portlets failed to deploy
  24. Receiving errors when installing and uninstalling WebSphere Portal Express with different users
  25. WebSphere Portal Express configuration fails
  26. Errors related to XADatasources prevent restarting WAS
  27. WpsHostPort property value not updated during installation
  28. Errors are written to SystemOut.log during portal startup
  29. Turkish language does not work with WebSphere Portal Express install wizard

  30. Related to Windows

    1. Version 6.0.1 only Error starting servers when servers running as Windows services
    2. Installation fails with the message "Please make sure you have at least 100MB free space in %TEMP% directory."
    3. WAS silent installation fails on Windows
    4. Installation program incorrectly identifies Windows 2003 operating system
    5. WAS installation stalls on Windows 2003 when installing from a network drive
    6. Installation program displays a dialog for amqicsdn.exe file when installing on Windows 2003
    7. During uninstall, an exception is found in wpuninstalllog.txt

  31. Related to Linux

    1. (Linux and Linux only) Some Double Byte Character Sets (DBCS) fonts may be corrupted when installing from console or GUI interface
    2. (Linux and Linux only) Install fails if path contains space

  32. Related to

    1. WebSphere Portal Express installation message states that the libraries for Motif and LessTif are missing when they are installed on the target system

  33. Related to i5/OS

    1. IBM WAS Update Installer cannot install interim fixes on an System i5 system with WAS Version 6.0.2.13 (i5/OS only)
    2. i5/OS login prompt freezes when installing remotely from Windows 2000 (i5/OS only)
    3. Parallel Portlet Rendering gets pipe timed out error (i5/OS only)
    4. addNode fails with timeout exception (i5/OS only)
    5. Installation program does not start (i5/OS only)
    6. Deployment into a cluster fails with FTP errors (i5/OS only)
    7. User ID no longer works (i5/OS only)

  34. Related to ReleaseBuilder

    1. ReleaseBuilder ignores deletion of attributes
    2. Warning when transferring complete configuration

 

User wpdb2ins already exists

By default, the IBM WebSphere Portal Express installation program creates a DB2 user ID that has a predefined value (wpdb2ins). If the wpdb2ins user already exists on the system, the installation program cannot install DB2 Express in its default configuration. You can choose either to continue installing and specify a different DB2 user ID, or exit the installation wizard, perform the necessary cleanup, and then restart the installation wizard.

Solution: First manually uninstall any unused versions of DB2. Then use the instructions below to remove the wpdb2ins user from your system.

On Linux...

userdel -r wpdb2ins

On Windows...

  1. Select...

    Start menu | Settings | Control Panel | Administrative Tools | Computer Management | System Tools | Local Users and Groups | Users | wpdb2ins (right-click) | Delete

  2. Select...

    Start menu | Settings | Control Panel | System | Advanced tab | User Profiles | Settings | unknown_user profile (right-click) | Delete

 

Installation fails when logging in using NLS characters

DB2 does not allow you to install using any NLS characters or because it sends the current OS user and the database user to its subsystem which can only handle ASCII character sets. DB2 also does not support single quotes within the user ID.

Solution: This is a known DB2 limitation. Install WebSphere Portal Express in a path whose name does not contain NLS characters or single quotes.

 

Wizard default language does not match language locale

After you change the language locale for your operating system, the selected default language in the wizard does not match the language locale.

Solution: This is a known limitation.

 

Insufficient credentials to stop the administrative server

After installation is complete, an error occurs if you try to stop the WebSphere Application Server administrative server via the Windows menu command...

Start | Programs | IBM WebSphere Application Server Network Deployment v6 | Profiles | wp_profile | Stop the server

This problem occurs because the installation process enables security and the menu command that stops the administrative server does not have access to the required user ID and password for the WebSphere Portal Express and WebSphere Application Server administrator.

Solution: Edit...

was_profile_root/properties/soap.client.props

...as follows...

You may need to stop and restart the WebSphere Portal Express application server.

 

Installation directory path cannot contain National Language characters

You cannot install WebSphere Portal Express in a directory whose name contains National Language characters.

Solution: Install WebSphere Portal Express in a path whose name does not contain National Language characters.

 

The WebSphere Portal Express Version 6.0 installation program dependency checker does not recognize any interim fix installation on WAS V6.0.2.9, 6.0.2.11 or 6.0.2.13

The latest WAS group PTFs (SF99312 and SF99301) include Version 6.1 of WAS Update Installer. If this version of the Update Installer was used to install interim fixes, a history file NIFStack.xml is created instead of maintenanceStack.xml, which was created and maintained by the WAS Update Installer Version 6. The WebSphere Portal Express Version 6 installation program dependency checker retrieves the interim fix history from the maintenanceStack.xml file rather than NIFStack.xml.

Solution: From the ProdData directory copy the file...

app_server_root/properties/version/update/backup/NIFStack.xml

...and paste it into the same directory. Rename this copied file to...

maintenanceStack.xml

Rerun the installation program.

 

Change to make if IBM HTTP Server and WAS plugin installed

If you install IBM HTTP Server (IHS) and the associated WAS Plug-in from the disk labeled SO-2 and intend to enable SSL services using the https transport, then perform the following manual steps after installation.

Solution: As user root, change directory to {IHS_ROOT}/lib and create a symbolic link from libgsk7ssl.so to...

/opt/ibm/gsk7_64/lib64/libgsk7ssl_64.so

For example,

CD /opt/IBMIHS/lib ln -s /opt/ibm/gsk7_64/lib64/libgsk7ssl_64.so libgsk7ssl.so

 

Receive EJPIC0034E: unexpected service exception message

Installation on a mounted directory fails with a EJPIC0034E: unexpected service exception error.

Solution: If you receive this message, run df-k to see if there are problems with your file systems or you can validate using df-k before installing.

 

Information on WebSphere Portal Express Version information and History information

WebSphere Portal Express Version information: The WebSphere Portal Express Version information tool can be used to gather information about the WebSphere Portal Express product. This information may be useful when contacting customer support by providing a snapshot of your WebSphere Portal Express product specifics. The WebSphere Portal Express Version information tool is located in the following directory:

The tool can be invoked using the following:

You can also generate a report in html format by executing the genVersionReport tool

 

History information:

The History information tool can be used to gather installation history for the WebSphere Portal Express product.

The History information tool is located in the following directory:

The History information tool can be invoked using the following:

You can also generate a report in HTML format by executing the genHistoryReport tool:

 

Java processes continue to run

When canceling installation during one of the installation steps, there may be some extra Java processes left running in the background.

Solution: Stop any running Java processes before attempting another installation.

 

Setup program fails to run

Solution: If you are unable to run the Setup program, you can start installation by running the appropriate command from the PortalExpress directory:

 

General steps to perform if the installation fails

Solution: If the WebSphere Portal installation fails, follow these steps:

  1. If the WebSphere Portal installation fails, check the WebSphere Portal logs for relevant messages.

  2. Verify that WAS has been installed correctly.

    If you did not use WebSphere Portal Express installation program to install WAS, ensure that the correct WAS Fix Packs and interim fixes are installed.

  3. Before you use the installation program to install WebSphere Portal or any other component that requires WAS, verify that you can start and stop WAS.

  4. Change the time-out request for the SOAP client. The default, in seconds, is 180. Within the directory...

    was_profile_root/properties/

    ...edit the soap.client.props file. Change the line to:

    com.ibm.SOAP.requestTimeout=6000

 

Reinstall after a failed installation

Solution: If a product fails to install, do the following steps before you attempt to install again:

  1. If an uninstallation program is available, run it before reinstalling the product. If the installation failed before the uninstallation program was created or if the uninstallation program fails, manually delete the installation directory and all of its contents before reinstalling the product. See the uninstallation section for more information on manual uninstallation.

  2. When you run the installation program, any irregularities in the vpd.properties file pertaining to WebSphere Portal Express will be corrected automatically.

    It is not recommended that you edit this file manually or delete it.

 

Installation fails after uninstalling a previous copy of WebSphere Portal

If the WebSphere Portal installation fails after you have uninstalled a previous copy of WebSphere Portal, ensure that no components of the WebSphere Portal remain before you attempt to install WebSphere Portal again.

Solution:

  1. Open the Administrative Console for WAS.

    Verify that all of the WebSphere Portal components were removed by the previous uninstallation. Manually remove any of the components that remain. This includes the following elements:

    Enterprise application: WebSphere Portal Enterprise Application
    Application server: WebSphere Portal Express
    Data sources: wpsdbDS and wmmDS
    JDBC driver: wpsdbJDBC

  2. On the portal machine, delete the WebSphere Portal directory manually.

  3. Restart the installation.

 

Receive "Permission denied" error when attempting to install on Linux

You receive a "Permission denied" error message when attempting to install WebSphere Portal using a non-root user on a Linux system

Solution: Remove the following files and directories from your /tmp directory. Remove all files from your /var/tmp directory as well.

These files may exist from a previous installation and be owned such that the installing user cannot overwrite them.

 

Search Collections are not removed during an uninstall

Solution:

  1. Remove the Search Collections before uninstalling.

  2. Manually remove the Search Collections by deleting the app_server_root/searchcollectionname directories after an uninstall is complete.

    The Search Collections directory might not be located under app_server_root since the user can choose to locate Search Collection anywhere on the system

 

ICM exceptions occurs during portal startup after 6.0.0.1 or 6.0.1 uninstall

After you uninstall the version 6.0.0.1 Fix Pack or the 6.0.1 Fix Pack, you may see some ICM exceptions in SystemOut.log file during the portal startup. The detail exception is similar to the message below: 

==================================================================================
[11/3/06 6:48:08:133 EST] 00000032 WorkManagerFa I   
ASYN0067I: Resource wm/icmci is being looked up without using resource reference. 
[11/3/06 6:48:08:329 EST] 00000032 PortalCollect E 
com.ibm.hrl.portlets.WsPse.PortalCollectionsService getUnsecuredIndexCreationBean 
EJPJO0085E:  Failed to retrieve index creation bean for collection 
/opt/IBM/WebSphere/PortalServer/collections/Portal Content
com.ibm.hrl.juru.IndexWrongVersionException: Index data version:juru_5.0.3 
<> package data version:juru_5.0.1   
at com.ibm.hrl.juru.DoubleIndex.open(DoubleIndex.java:494)   
at com.ibm.hrl.juru.DoubleIndex.<init>(DoubleIndex.java:459)

Solution: Portal search collections created in version 6.0.0.1 or 6.0.1 will not be supported in version 6.0 and vice versa. If you want to use the collections in another portal version, you need to recreate them.

 

Installation fails due to path problem

Installation can sometimes fail if you download installation files to a local hard drive or a network drive and use long directory paths for the directories corresponding to the product CDs.

Solution: Where possible, you should specify short path names that do not contain special characters such as Double Byte Character Sets (DBCS).

 

Non ISO-8859-1 characters not supported in installation path

Solution: Installing to paths containing non ISO-8859-1 characters does not work and is not currently supported. Installing WebSphere Portal Express to use an existing WAS whose install path includes non ISO-8859-1 characters also might not work. For example, Chinese characters in the installation path are not supported.

 

Console mode installation not available for bidirectional languages

When installing WebSphere Portal Express in console mode on machines with bidirectional language support, an error is generated, and the installation exits.

Solution: Console mode installation is not supported for bidirectional languages, such as Hebrew and Arabic. When installing WebSphere Portal Express in a bidirectional language, you cannot use console mode. Instead, perform the installation using the graphical interface or using a response file.

 

Installation fails due to insufficient disk space

Solution: If you receive a message during installation informing you that there is insufficient disk space to install WebSphere Portal Express, you can complete one of the following steps:

 

Desktop display width doubles when running installation program

When running the WebSphere Portal Express installation program on a machine with the Windows 2000 operating system, you might encounter an error that causes the desktop to be displayed at twice its normal width, so that only half of the desktop can be viewed. This problem is due to an issue with Java 1.4 and the display settings of the monitor. This problem can occur for any of the ISMP-based wizards, such as the configuration wizard.

Solution 1: Reduce the refresh rate for the monitor.

  1. Exit the installation program (if still running).

  2. Click Start > Settings > Control Panel.

  3. Double-click Display.

  4. In the Display Properties window, click Settings > Advanced > Monitor.

  5. Change the refresh rate to a lower value. For example, if the refresh rate is set to 85 Hertz, you can change it to 60 Hertz.

  6. Click OK > OK >Yes to save your changes.

After you complete the WebSphere Portal Express installation, restore your display settings to their previous values.

Solution 2: Decrease screen resolution (This solution increases the pixel size on your screen to increase the size of the image.)

  1. Exit the installation program (if still running).

  2. Click Start > Settings > Control Panel.

  3. Double-click Display.

  4. Click Settings.

  5. In the Screen Area section, move the slider to the left (toward "Less").

    If your monitor resolution is at its lowest setting, refer to Solution 1 above.

  6. Click OK > OK > Yes to save your changes.

After you complete the WebSphere Portal Express installation, restore your display settings to their previous configuration.

 

Some portlets failed to deploy

If you encounter installation error EJPI0021W Some portlets failed to deploy, you might be able to recover the installation. This error can be caused by some portlets being left on WAS, or caused by WebSphere Portal Express not running.

Solution: The user must first verify that WebSphere Portal Express starts and that the user can log in as the WebSphere Portal Express administrator.

If this cannot be verified, something more severe than portlet deployment has gone wrong and manually installing portlets will not work. If WebSphere Portal Express login succeeds, you might be able to manually install portlets. To manually install portlets, run the following commands:

  1. Change directory to the WebSphere Portal Express configuration directory:

    • Windows:

      Open a command prompt, and change to the directory portal_server_root\config.

    • Linux:

      Open a command prompt, and change to the directory portal_server_root/config.

    • i5/OS:

      Start the Qshell interpreter on your i5/OS system by typing STRQSH on an OS/400 command line, and change to the directory portal_server_root_user/config.

  2. To drop all portlets, issue the following command:

    Windows portal_server_root\bin
    Linux portal_server_root/bin
    i5/OS portal_server_root/bin. 

    xmlaccess -in portal_server_root/package/removeallportlets.xml 
          -user portal_admin_id 	 
          -pwd portal_admin_password 
          -url localhost:port_number/wps/config

  3. To install all portlets, issue the appropriate command for your operating system:

    • Linux:

      ./WPSconfig.sh portlets -DPortalAdminPwd=password

    • Windows:

      WPSconfig.bat portlets -DPortalAdminPwd=password

    • i5/OS:

      WPSconfig.sh-profileName profile_root portlets -DPortalAdminPwd=password

      where profile_root is the name of the WAS profile where WebSphere Portal Express is installed; for example, wp_profile.

 

WebSphere Portal Express configuration fails

If the configuration of WebSphere Portal Express fails with an error similar to the one below, it might be that there is not enough swap space. 

BUILD FAILED
file:../config/actions/was_cfg.xml:592: Execute failed: java.io.IOException: Not enough space 
Total time: 44 minutes 10 seconds

Solution: Increase your swap space to a minimum of 2.5 GB. 3.0 GB is preferred.

 

Errors related to XADatasources prevent restarting WAS

If WAS is stopped improperly or unexpectedly, you might see errors similar to the one below when you try to restart: 

J2CA0061W: Error creating XA Connection and Resource com.ibm.ws.exception.WsException: 
DSRA8100E: Unable to get a XAConnection from the DataSource.

When this happens, you will be unable to restart WAS. This is because there are XA transactions still pending in the translog directory.

Solution: Delete the transaction logs in the was_profile_root tranlog/WebSphere_Portal directory, then restart WAS.

 

WpsHostPort property value not updated during installation

If the wpconfig.properties file is locked during installation, such as when it is open in a text editor, this can prevent the WpsHostPort property value from being updated properly. Although this is unlikely to occur during most installation scenarios, it could happen if you are installing on an existing WAS with security enabled, because this installation scenario requires you to perform the installation in a series of manual steps.

If the WpsHostPort property value is not set correctly, you will encounter problems if you perform a task that refers to the wpconfig.properties file for the WpsHostPort property, such using the xmlaccess command to deploy security credentials or portlets. Because the command will attempt to use the default value of 80 for WpsHostPort instead of the port number set at installation (which is what the xmlaccess command expects), the command will fail.

Solution: Edit the wpconfig.properties file with a text editor, and change the value of the WpsHostPort property to the value set during installation.

 

Receiving errors when installing and uninstalling WebSphere Portal Express with different users

Solution: You must install and uninstall WebSphere Portal Express with the same user.

 

Errors are written to SystemOut.log during portal startup

During portal startup, error(s) similar to the following might be written to the SystemOut.log: 

0000000a ArtifactLoade W com.ibm.ws.al.locator.TargetNamespaceSAXParser parseDocument(URL) 
CWLAG0450W:unableto parse document 
	file:/opt/IBM/WebSphere/PortalServer/shared/app/oiexport/SearchML.xsd;
Reason: org.xml.sax.SAXParseException: The element type "complexType" 
	must be terminated  by the matching 
end-tag.

Solution: The error does not indicate a problem with WebSphere Portal Express nor with XML conversion, and can be ignored.

 

Turkish language does not work with WebSphere Portal Express install wizard

Using Turkish as the install wizard language when installing WebSphere Portal Express causes errors.

Solution: When installing WebSphere Portal Express, use English as the install wizard language regardless of operating system locale.

 

Related to Windows

 

Error starting servers when servers running as Windows services

Version 6.0.1 only You receive an error such as ADMU7711E: Unexpected exception associated with WASService.exe: exitCode = -1 during processing of a server with the name: WebSphere_Portal. However, the server and associated Windows service start.

Solution: If you are running on a non-production server (for example, a system that meets the minimum hardware requirements but that does not have enough resources to start WebSphere Portal in less than five minutes), then ServicesPipeTimeout should be set to a value that is longer than the amount of time it takes to start the portal server according to the instructions entitled "How to debug Windows services" on the Microsoft support site .

 

Installation fails with the message "Please make sure you have at least 100MB free space in %TEMP% directory."

This message may be displayed even if your %TEMP% directory has more than 100MB of free space. If you have more than 100MB of free space, it is likely the install.bat (or install.sh) had problems copying some files to your %TEMP% directory. Refer to the %TEMP%\wplaunchlog.txt file.

There are several reasons this might happen:

Solutions:

 

WAS silent installation fails on Windows

On Windows, the silent installation fails if the user lacks permissions. In interactive mode, the install will catch the error and display a message. The GUI installer will not let the installation continue until the permissions are set by the System Administrator.

Solution: You must have the permissions set as stated in Preparing your Windows machine.

 

Installation program incorrectly identifies Windows 2003 operating system

When installing WebSphere Portal Express on Windows 2003, an error similar to the following error might be displayed in the installation log file: 

   EJPC1517I The Discovered specific Operating System type and version  
     Is winxp(5.0,2.0,0.0,0.0,0.0)

Solution: Due to how different levels of Java report Windows 2003, the installation program might identify the operating system incorrectly as either Windows 2000 or Windows XP. This error does not affect the WebSphere Portal Express installation and can be ignored.

 

WAS installation stalls on Windows 2003 when installing from a network drive

When installing WAS on a Windows 2003 machine, the installation can stall if you are attempting to perform the installation from a network file system.

Solution: Windows 2003 includes security policy settings that can prevent some programs from being run from a network file system without permission.

In this case, the WAS installation program is being denied access and is unable to complete. To allow such programs to run, update your security settings, as described in the following steps:

  1. Update the list of trusted sites on the Windows 2003 machine by adding the network file system containing the program you want to run.

    1. Open the Control Panel.

    2. Double-click Internet Options, and select the Security tab.

    3. Click Trusted sites, and then click Sites.

    4. Enter the network share, and click Add. The URL syntax is required for this information. For example, if you are connecting to share myshare on machine myhost, you would enter file://myhost/myshare.

    5. Click OK.

  2. Change the security level for the Trusted sites zone.

    1. On the Trusted sites page, click Custom Level.

    2. Locate Launching applications and unsafe files in the list of settings and click Enable.

    3. Click OK.

  3. Click OK to save the changes.

After completing these changes, you should be able to run the WAS installation program from a network file system.

 

Installation program displays a dialog for amqicsdn.exe file when installing on Windows 2003

When installing WebSphere Portal Express on a Windows 2003 machine from a network file system, the installation might display a dialog asking whether you want to open the amqicsdn.exe file.

Solution: Windows 2003 includes security policy settings that can prevent some programs from being run from a network file system without permission. In this case, the amqicsdn.exe file cannot run unless you perform one of the following steps:

 

During uninstall, an exception is found in wpuninstalllog.txt

On Windows, you may see the following exception in the wpuninstalllog.txt: 

ServiceException: (error code = -90001; message = "The configuration registry key is invalid.
(1010)"; severity = 0)

Solution: This exception can be ignored. Uninstall will still complete successfully.

 

Related to Linux

 

(Linux and Linux only) Some Double Byte Character Sets (DBCS) fonts may be corrupted when installing from console or GUI interface

On some versions of Linux and Linux, certain double-byte character sets can be corrupted during installation. When installing from the console, Korean, Traditional Chinese, and Simplified Chinese character sets are affected.

Using the GUI installation, Traditional Chinese and Simplified Chinese character sets are affected.

Solution:

Console Install Simplified Chinese Traditional Chinese Korean
HP-UX 11v zh_CN.hp15CN zh_TW.big5 ko_KR.eucKR
SuSE SLES 8 zh_CN.gb18030 zh_TW ko_KR.euckr
  zh_CN.gbk    
  zh_CN    
Red Hat AS 3 Update 1 zh_CN.gb18030 zh_TW ko_KR.euckr
  zh_CN.gbk    
  zh_CN    

GUI Install Simplified Chinese Traditional Chinese
HP-UX 11v zh_CN.hp15CN zh_TW.big5
    zh_TW.eucTW
SuSE SLES 8 zh_CN.gb18030 zh_TW
  zh_CN.utf8  
Red Hat AS 3 Update 1 zh_CN.gb18030 zh_TW
  zh_CN.utf8 zh_TW.euctw
    zh_TW.utf8

 

(Linux and Linux only) Install fails if path contains space

Linux and Linux do not support install paths that contain a space.

Solution: This is a known limitation. Remove the space from the install path.

 

Related to Linux

 

WebSphere Portal Express installation message states that the libraries for Motif and LessTif are missing when they are installed on the target system

Solution: Ignore this message and continue installation if you know the Motif or LessTif libraries are installed.

 

Related to i5/OS

 

IBM WAS Update Installer cannot install interim fixes on an System i5 system with WAS Version 6.0.2.13 (i5/OS only)

Interim fixes PK27024 and PK24014 are not included in WAS 6.0.2.13 Fix Pack.

 

Solution:

Download interim fixes PK29636 and PK27024 from Fix list for WAS Version 6.0.2, noting that interim fixes are dependent on the WAS version.

 

i5/OS login prompt freezes when installing remotely from Windows 2000 (i5/OS only)

When installing WebSphere Portal Express remotely from a Windows 2000 workstation, the i5/OS login prompt might freeze and not allow the user to enter anything in the fields.

Solution: Click on the Windows desktop, then click an input area in the login prompt. If the problem persists, cancel the installation and try again.

 

Parallel Portlet Rendering gets pipe timed out error (i5/OS only)

There is a timer value for the pipes reading the portlets content. Your i5/OS might require a higher rendering time frame. "PEEX0110E: The underlying pipe timed out while reading" is logged and "This portlet is temporarily disabled" is shown on the Portal page.

Solution: Run WPSconfig.sh -profileName profile_root action-update-portletcontainersevice -DparallelRenderingTimeOut=xxxxx, from a Qshell prompt, where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile, parallelRenderingTimeOut is the property that specifies the timeout value in milliseconds, and xxxxx is the new value. The default is 4000ms. The parallelRenderingTimeOut property is not specified in the wpconfig.properties file and must be specified on the command line to change the value.

 

addNode fails with timeout exception (i5/OS only)

On some machine configurations, WebSphere Portal Express components can cause a timeout exception when a node is being added to the Network Deployment in a cluster environment.

Solution: The problem can be avoided by increasing the Network Deployment's ConnectionIOTimeOut value before running the addNode command. However, if addNode has already been run, remove the node and uninstall the applications associated with that node from the Network Deployment profile using the Network Deployment administration console. For instructions on removing a node, refer to the Remove nodes from a Network Deployment instance topic of the System i5 information center.

Once you have removed the node, add a new node by following the instructions in the Clustering and WebSphere Portal Express topic, making sure to follow the directions for increasing the Network Deployment's ConnectionIOTimeOut value.

 

Installation program does not start (i5/OS only)

The WebSphere Portal Express installation program might not start if host servers are not running on the System i5 system.

Solution: Start host servers by entering the following on an OS/400 command line: 

STRHOSTSVR SERVER(*SIGNON *RMTCMD)

After host servers have been started, try running the WebSphere Portal Express installation program again.

 

Deployment into a cluster fails with FTP errors (i5/OS only)

Deployment of WebSphere Portal Express into a cluster might fail with a variety of FTP errors due to a problematic entry in the resources.xml file.

Solution: Open the resources.xml file located in the directory portal_server_root_user/config/cells/cellname/nodes/nodename/servers/servername, where cellname is the cell name, nodename is the node name, and servername is the application server name. Comment out the Samples URL Provider entry (last entry in the file). Save the file and attempt deployment again.

 

User ID no longer works (i5/OS only)

If you specify the wrong password for the user ID while running WPSconfig.sh i5/OS will render that user ID useless. See a system administrator in order to reactivate the user ID.

 

Related to ReleaseBuilder

 

ReleaseBuilder ignores deletion of attributes

 

If you delete values of fields in the portal administrative user interface, this might result in empty attributes in an XML export file. If you then use ReleaseBuilder to extract the changes between the configurations before and after the deletion of attributes, the difference file does not reflect the deletion of the attributes.

 

Cause: This is a known limitation. The ReleaseBuilder does not recognize the deletion of attributes. Refer also to You cannot delete attributes by using the XML configuration interface.

 

Solution: After you have completed the staging process with ReleaseBuilder, delete the attributes on the target portal system by using the same steps as you performed on your source system.

 

Sample scenario and files: An example scenario and sample scripts are given in the following.

  1. You create configuration status export1 of your source portal by using the XML configuration interface.

  2. You modify your source portal by deleting the contents of fields in the portal administrative user interface that lead to attributes without a value in an XML export file.

  3. You create configuration status export2 of your source portal by using the XML configuration interface.

  4. You use ReleaseBuilder to extract the changes between export1 and export2.

The resulting differential file does not contain the deleted attributes.

Sample XML script file snippet export1: 

<client action="update" domain="rel" manufacturer="dilbert" markup="html" markup-version="1.1" 
    name="puppy" objectid="M_CEENUPA000O7002A6CJO0Q1200" ordinal="250" version="1.0">
   <useragent-pattern>dogert</useragent-pattern>
   <client-capability update="set">dish</client-capability>
   <client-capability update="set">html</client-capability>
</client>

Sample XML script file snippet export2: 

<client action="update" domain="rel" manufacturer="dilbert" markup="html" markup-version="1.1" 
    name="" objectid="M_CEENUPA000O7002A6CJO0Q1200" ordinal="287" version="">
   <useragent-pattern>dogert</useragent-pattern>
   <client-capability update="set">dish</client-capability>
   <client-capability update="set">html</client-capability>
</client>

From the two exports above, ReleaseBuilder generates the following differential file: 

<?xml version="1.0" encoding="UTF-8"?>
<!-- IBM WebSphere Portal/6.0 build wp600_154 exported on Wed Apr 05 14:24:19 
   EDT 2006 from xyz -->
<request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" build="wp600_154" type="update" 
    version="6.0.0.0" xsi:noNamespaceSchemaLocation="PortalConfig_1.4.xsd">
   <portal action="locate">
    <client action="update" objectid="M_CEENUPA000O7002A6CJO0Q1200" ordinal="287"/>
   </portal>
</request>

If you use this ReleaseBuilder differential file to update your target portal, the name and version attributes of the client tag are not deleted on the target portal. To complete the update, you have to delete the attributes manually by using the same steps by which you deleted the attributes on the source portal.

 

Warning when transferring complete configuration

When attempting to import the entire portal configuration, the transfer will be successful with some warnings similar to, but not limited to, the following: 

<status element="[virtual-resource 0_000000000000G3RCDT7BG0C100 
    uniquename=wps.USER_GROUPS 
    name=USER_GROUPS]" 
    result="warning">

    <message id="EJPXA0060W">com.ibm.wps.command.xml.XmlCommandException: 
      EJPXA0060W: A user or group with ID cn=wpscontentadministrators,o=default 
      organization could not be retrieved from the portal datastore, possibly because it does not exist. 
      Related access-control configuration data will not be updated. 
      [virtual-resource 0_000000000000G3RCDT7BG0C100 uniquename=wps.USER_GROUPS name=USER_GROUPS]
     </message>
    </status>
    <status element="[virtual-resource 0_000000000000G3RCDT7BG0G100 uniquename=wps.USERS name=USERS]"
    result="warning">
    <message id="EJPXA0060W">com.ibm.wps.command.xml.XmlCommandException:
    EJPXA0060W: A user or group with ID cn=wpscontentadministrators,o=default  organization 
    could not be retrieved from the portal datastore, possibly because it does not exist. 
    Related access-control configuration data will not be updated. 
    [virtual-resource 0_000000000000G3RCDT7BG0G100 uniquename=wps.USERS name=USERS]
     </message>
    </status>

Solution: You can ignore these warnings or use the CleanupUsers.xml example file to identify users and groups in your database who have been removed from the user registry. Refer to Deregistering users and groups from WebSphere Portal Express for more information.

 

See also:

troubleshooting

 

Parent topic:

Search the product documentation for a solution