Explanation | The cell name is a required value. |
Action | You must specify a cell name. |
Explanation | Both the server name and the node name are required for single-server plug-in generation. |
Action | If you specify a server name, you must specify a node name. |
Explanation | An unknown parameter was encountered. |
Action | Review the usage information of the GenPluginCfg utility for valid parameters. |
Explanation | An error occurred while the utility was running. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates the name of the plug-in configuration file. |
Action | No user action is required. |
Explanation | An error occured while generating the plug-in configuration file. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while generating the plug-in configuration file. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates that the configuration file for the cell is generating. |
Action | No user action is required. |
Explanation | None |
Action | No user action is required. |
Explanation | A cell name is required. |
Action | Specify a cell name. Make sure that configuration data is saved in the repository. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | None. |
Action | No user action is required. |
Explanation | None. |
Action | No user action is required. |
Explanation | No nodes or clusters are defined in the present configuration. No servers are available for which to generate a plug-in configuration. |
Action | Create nodes and clusters that have servers in them using either the administrative console, or the wsadmin.sh tool. |
Explanation | No servers are defined in the given cell. No servers are available for which to generate a plug-in configuration. |
Action | Create servers within the nodes and clusters before running the tool, by using either the administrative console or the wsadmin.sh tool. |
Explanation | One or more of the cluster members do not have server names. |
Action | Use the administrative console or the wsadmin tool to fix this problem. |
Explanation | This error occurred because of a corrupt cluster configuration file. |
Action | Use the administrative console to cluster your servers again. If that action fails, delete any cluster configuration that might be present and try again. Make sure that configuration data is saved in the repository. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This error occured because of a corrupt cluster configuration file. |
Action | Use the administrative console or the wsadmin.sh tool to cluster your servers again. If that action fails, delete any cluster configuration that might already be present and try again. |
Explanation | No cells are found in your existing configuration. |
Action | Use the administrative console or the wsadmin.sh tool to create the cells. |
Explanation | No servers are found in the specified cluster. |
Action | Use either the administrative console or the wsadmin tool to configure the servers within the cluster. |
Explanation | No servers are found. No servers are available for which to generate the plug-in configuration. |
Action | Use either the administrative console or the wsadmin tool to configure the servers within the cluster. |
Explanation | No configuration data is found for one or more of the servers that you specified. |
Action | Use either the administrative console or the wsadmin tool to configure your servers. |
Explanation | No configuration data is found for one or more of the servers that you specified. |
Action | Use either the administrative console or the wsadmin tool to configure your servers. |
Explanation | No configuration data is available for the Web container component of one or more of the specified servers. |
Action | Use either the administrative console or the wsadmin tool to configure the Web containers again. |
Explanation | No configuration data for the Web container component is available for one or more of the specified servers. |
Action | Use either the administrative console or the wsadmin tool to configure the Web containers again. |
Explanation | The present configuration did not contain a server index file. This missing file can result from a corrupt configuration. |
Action | Verify that the server index file exists or create one. |
Explanation | One or more of the applications that deployed on the specified servers cannot be read. |
Action | Examine the exception information. Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. If the problem persists, redeploy the application. Verify that the enterprise archive (EAR) file and the Web archive (WAR) file are valid. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | One or more of the applications that are deployed on the specified servers cannot be read. |
Action | Examine the exception. Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. Make sure that configuration data is saved in the repository. If the problem persists, redeploy the application. Verify that the enterprise archive (EAR) file and the Web archive (WAR) file are valid. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | No nodes are defined in the present configuration. This problem can result from a corrupt configuration. |
Action | Make sure that configuration data is saved in the repository. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Make sure that configuration data is saved in the repository. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A problem resulted from generating the plug-in configuration file. |
Action | Examine the exception for nested exceptions and error codes. Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A problem resulted from generating the configuration file. |
Action | Examine the exception for nested exceptions and error codes. Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates a root exception. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Rerun the GenPluginCfg script with the -debug option set to yes (GenPluginCfg -debug yes), to see trace details. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The webservices.jar file might not be in the class path. |
Action | Check the class path and include the JAR file, if necessary. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | None. |
Action | No user action is required. |
Explanation | Only one node can be specified when multiple servers are passed as parameters. |
Action | Specify one node only using either the administrative console or the wsadmin tool. |
Explanation | The Lotus workplace server helper class is not loaded. |
Action | No user action is required, if Lotus workplace servers are not defined. If you define Lotus workplace servers, verify that the class path includes the cfplugin.jar file. |
Explanation | None. |
Action | No user action is required. |
Explanation | None. |
Action | No user action is required. |
Explanation | None. |
Action | No user action is required. |
Explanation | None. |
Action | No user action is required. |
Explanation | Node sync is used to move the plug-in configuration file to the managed node. |
Action | No user action is required. |
Explanation | None. |
Action | No user action is required. |
Explanation | Exception has occured when transferring the plug-in configuration file. |
Action | Check if the IHS administration server is configured correctly. |
Explanation | Propagation of the plug-in configuration file to the remote webserver is supported only for the IHS Web server. |
Action | No user action is required. |
Explanation | None. |
Action | No user action is required. |
Explanation | None. |
Action | No user action is required. |
Explanation | Exception occured when generating the plug-in configuration file. |
Action | Enable trace for the classes "com.ibm.websphere.plugincfg.generator.*". If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Exception occured when getting the server type for the server |
Action | Enable trace for the classes "com.ibm.websphere.plugincfg.generator.*". If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Exception occured when getting the list of Web servers. |
Action | Enable trace for the classes "com.ibm.websphere.plugincfg.generator.*". If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Exception occured when getting plug-in properties |
Action | Enable trace for the classes "com.ibm.websphere.plugincfg.generator.*". If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | None. |
Action | No user action is required. |
Explanation | Exception occured when starting the plug-in configuration service. |
Action | Enable trace for the classes "com.ibm.websphere.plugincfg.generator.*". If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Plug-in configuration service is started only when it is enabled, and is run on dMgr server or the stand alone WebSphere application server. |
Action | No user action is required. |
Explanation | Plug-in configuration file for the Web server is generated based on the applications that are mapped to it. No applications are mapped to the Web server. |
Action | Application install wizard can be used to map modules to the Web server. |
Explanation | This informational message indicates name of the debug log file. |
Action | No user action is required. |
Explanation | None. |
Action | No user action is required. |
Explanation | Exception has occured when transferring the plug-in configuration file. |
Action | Check if the IHS administration server is configured correctly. |