"Error 503: Failed to load target servlet [portal]" in Workplace or Portal

Problem

You login to Lotus Workplace or WebSphere Portal server and receive the following error: Error 503: Failed to load target servlet [portal]

Solution

The problem is due to general connectivity issues with the database server. The following is a list of known causes of this issue: Cause #1 Loss of connectivity to the DB2 server from the Lotus Workplace/Portal server can result in this error displaying to users. In the Systemerr.log, you see the message: com.ibm.websphere.ce.cm.StaleConnectionException: [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001 The number for the Protocol specific error code can be a different value. Restart the DB2, HTTP, WebSphere Administration, Websphere Portal , and Lotus Workplace servers. Cause #2 This error will also occur if the OS locale for the Lotus Workplace server changes. Refer to the technote titled "Workplace: Reinstall Required to Change OS Locale of Server" (#1159592) for more information. If an install of Lotus Workplace is not successful, the following error can display: Error 503 : Failed to load target servlet [portal], files missing Review install log files and SystemOut.log or SystemErr.log to find further information on the issue. Cause #3 One particular customer discovered an error in the system.out file which indicated that the data source name was incorrect. J2CA0036E: An exception occurred while invoking method setDataSourceProperties on com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jdbc/wmmDS : java.lang.reflect.InvocationTargetException: com.ibm.ws.exception.WsException: DSRA0023E: The DataSource implementation class "com.ibm.db2.jdbc.DB2XADataSource" could not be found. Changing the name and case of Implementation Classname in the WebSphere Application Server (WAS) administrator (under Resources JDBC providers) to the correct name solved the issue. Cause #4 The DB2 databases are not cataloged by the DB2 client on the Lotus Workplace server. To catalog a database, use the following commands: catalog tcpip node nodename remote fullyqualifiedDB2servernameserver port catalog db wps50 as wps50 at node nodename List of databases: wps50 wpcp50 fdbk50 LWPCOM LWPLMS LWPLDS NAGANO LWPARC LWPSQL** ** If you decide to use one database for all Lotus Workplace components then that is the database you need to catalog, in addition to the Portal databases. Cause #5 The Windows DB2 user accounts are locked out of the DB2 client (on Portal) and/or the db2server server. Cause #6 Failing to source the db2profile in the login profile of the IBM WebSphere® Application Server V5 instance owner. Directions on how to do this are described in the topic, "Configuring WebSphere Application Server for DB2 access," in the WebSphere Application Server Enterprise information center: http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp