Troubleshooting installation, configuration, and uninstall problems

Before running commands

Several problems can cause a build failure when you run ConfigEngine.sh tasks.

Check the following before you run a command to install, configure, or uninstall.

Is the environment configured correctly?

Make sure that the WebSphere® environment and CLASSPATH environment variable are set correctly by running the following command:

. wp_profile_root/bin/setupCmdLine.sh

Note: There is a space between the period (.) and the rest of the command.

wp_profile_root\bin\setupCmdLine

Are the application servers started or stopped?

Ensure that the application servers are started or stopped as required by the particular procedure.

Are the parameters specified correctly?

Parameters for ConfigEngine.sh are case-sensitive. Some of the input commands are long. Double-check commands before starting them.

Can you connect to the database?

Verify that you can connect to the database. Be sure to provide correct database information during installation.

Is the DB2® applet ("net") driver started? (DB2 only)

On the DB2 server, ensure that the JDBC applet ("net") driver is started. To check whether the driver is started, run the following command:

netstat -na | grep port_number

where port_number is the port number used by the driver. Normally port 50000 is used for the supported DB2 versions, unless another application (including another database instance) is already using that port.

For example, if you are using DB2 version 9.1 (with fix pack 5), you could start the "net" driver using the following command:

db2jstrt 50000

For instructions on starting the "net" driver in your environment, refer to the DB2 information center.

Note: If you configured Multi-Channel Server to use a data source after installation is complete, the DB2 net driver will no longer be used.

Are the Multi-Channel Server (MCS) database parameters specified correctly?

If the MCS database parameters or the McsProject parameter are specified incorrectly during MCS installation, the procedure to import devices and policies fails. Incorrect parameters also prevent Mobile Portal Accelerator from working properly after installation.

You must make the following updates to correct such problems:

1. Modify the file ImportPolicies script (or batch file) in the wp_root/wp.mobile/wp.mobile.mcs/repository/bin directory. Correct database parameters, such as -vendor, -host, -port, -source, -user, or -password in the DEFAULT_ARGS line. Also ensure that the database driver files are added to the CLASSPATH line. See the Installing Multi-Channel Server topics for details on how to add the database driver files to the CLASSPATH line.
2. Modify the file wp_profile_root/PortalServer/wp.mobile/wp.mobile.mcs/mcs-config.xml. Correct database information in the <anonymous-data-source> and <mcs-database> elements. If the McsProject parameter was specified incorrectly, correct the jdbc-repository project value in the <standard> element and the jdbc-policies name attribute value in the <default> element.
3. Rerun any installation tasks that import policies and that failed because database parameters were specified incorrectly.
4. If you modified the wp_profile_root/PortalServer/wp.mobile/wp.mobile.mcs/mcs-config.xml file, run the MCS configuration update procedure in the Configuring Multi-Channel Server topic after the installation of Mobile Portal Accelerator is complete.

If problems occur, check these files

The following files contain troubleshooting information.

• wp_profile_root/ConfigEngine/log/ConfigTrace.log

  Contains output from ConfigEngine tasks

• wp_profile_root/logs/WebSphere_Portal/SystemOut.log

  Contains the WebSphere Portal server standard output

• wp_profile_root/logs/WebSphere_Portal/SystemErr.log

  Contains the WebSphere Portal server standard error output

Mobile Portal Accelerator installation failed in cluster

The following error message displays:

./ConfigEngine.sh mwp-config-cluster-primary-node - failed

[wsadmin] WASX7017E: Exception received while running file "/opt/IBM/WebSphere/wp_profile/ConfigEngine/config/was/exportEar.jacl"; exception information: com.ibm.websphere.management.exception.AdminException
[wsadmin] com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.websphere.management.application.client.AppDeploymentException: [Root exception is org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0037E Could not open /opt/IBM/WebSphere/wp_profile/wstemp/Script129fe1b40ec/workspace/cells/mdsintel93Cell01/applications/MPAInfo.ear/MPAInfo.ear]
[wsadmin] org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0037E Could not open /opt/IBM/WebSphere/wp_profile/wstemp/Script129fe1b40ec/workspace/cells/mdsintel93Cell01/applications/MPAInfo.ear/MPAInfo.ear


BUILD FAILED

To resolve this issue, run a Full synchronization on the nodes and then restart the cluster. Next, reinstall the Mobile Portal Accelerator for the cluster.

Mobile Portal Accelerator installation fails with stand-alone LDAP

The following error message displays:

./ConfigEngine.sh mwp-config-all is failing with the folowing error 
wp.theme.modules.webapp.app_name=Theme_Modules
wp.theme.modules.webapp.context_root=/wps/themeModules
wp.webdav.ear.2.5.name=WebDAV_for_WebSphere_Portal
wp.wmm.vmm.db.migration.file.name=WmmVmmDBMigration_ascii.properties
wp.wmm.vmm.db.migration.file.name.original=WmmVmmDBMigration.properties
wps.classes.dir=/usr/IBM/WebSphere/PortalServer/bin
wps.product.version=7.0
wps.userdir=PortalServer
ws.ext.dirs=/usr/IBM/WebSphere/AppServer/java/lib:/usr/IBM/WebSphere/AppServer/classes:/usr/IBM/WebSphere/AppServer/lib:/usr/IBM/WebSphere/AppServer/installedChannels:/usr/IBM/WebSphere/AppServer/lib/ext:/usr/IBM/WebSphere/AppServer/web/help:/usr/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime:/usr/IBM/WebSphere/wp_profile/ConfigEngine/lib:/usr/IBM/WebSphere/wp_profile/ConfigEngine/shared/app:/usr/IBM/WebSphere/AppServer/plugins
wsadminConnType=SOAP
zipfiledir=/usr/IBM/WebSphere/wp_profile/filesForAutoPD
zipfilename=/usr/IBM/WebSphere/wp_profile/filesForAutoPD/wp.mustgather.zip
zipfilename.without.path=wp.mustgather.zip
---- End dump of properties ----
isIseries currently set to: null
uploading registry
Target started: update-registry-sync-property

update-registry-sync-property:
[echo] updated RegistrySynchronized in file wkplc.properties with value: true
Target finished: update-registry-sync-property

BUILD FAILED
/usr/IBM/WebSphere/PortalServer/wp.mobile/wp.mobile.mwp/config/includes/wp.mobile.mwp_cfg.xml:109: The following error occurred while executing this line:
/usr/IBM/WebSphere/PortalServer/wp.mobile/wp.mobile.mwp/config/includes/wp.mobile.mwp_cfg.xml:216: The following error occurred while executing this line:
/usr/IBM/WebSphere/PortalServer/wp.mobile/wp.mobile.mwp/config/includes/wp.mobile.mwp_cfg.xml:267: The following error occurred while executing this line:
/usr/IBM/WebSphere/PortalServer/wp.mobile/wp.mobile.mwp/config/includes/wp.mobile.mwp_cfg.xml:1275: The following error occurred while executing this line:
/usr/IBM/WebSphere/PortalServer/wp.mobile/wp.mobile.mwp/config/includes/wp.mobile.mwp_cfg.xml:1059: The following error occurred while executing this line:
/usr/IBM/WebSphere/PortalServer/wp.mobile/wp.mobile.mwp/config/includes/wp.mobile.mwp_cfg.xml:1159: EJPXB0015E: Server response indicates an error.

Total time: 47 minutes 34 seconds

And the following error is seen when starting the WebSphere Portal server in the system out log.

DYNA1071I: The cache provider "default" is being used.
[2/9/12 16:57:23:748 GMT+05:30] 00000012 ServerCache I DYNA1001I: WebSphere Dynamic Cache instance named ws/ldapusr1/SearchResultsCache initialized successfully.
[2/9/12 16:57:23:758 GMT+05:30] 00000012 ServerCache I DYNA1071I: The cache provider "default" is being used.
[2/9/12 16:57:25:802 GMT+05:30] 00000012 XACMLPolicyPa E XACMLPolicyParser$XACMLErrorHandler error() CWRGS4054E A error was issued while parsing the XML document at line 44, column 32. cvc-complex-type.2.4.a: Invalid content was found starting with element 'PolicySetIdReference'. One of '{"urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicySet, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":Policy, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicySetIdReference, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicyIdReference, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":CombinerParameters, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicyCombinerParameters, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicySetCombinerParameters, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":Obligations}' is expected. 
[2/9/12 16:57:25:818 GMT+05:30] 00000012 XACMLPolicyPa E XACMLPolicyParser parseDocument( InputStream ) CWRGS4038E An error occured while parsing an InputStream. CWRGS4054E A error was issued while parsing the XML document at line 44, column 32. cvc-complex-type.2.4.a: Invalid content was found starting with element 'PolicySetIdReference'. One of '{"urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicySet, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":Policy, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicySetIdReference, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicyIdReference, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":CombinerParameters, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicyCombinerParameters, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicySetCombinerParameters, "urn:oasis:names:tc:xacml:2.0:policy:schema:os":Obligations}' is expected. .

To resolve this issue, use a federated repository instead of a stand-alone LDAP.

Or, if you must use a stand-alone approach, use a WebSphere Application Server shared variable. Consider the following steps:

1. Navigate to wp_root/wp.mobile/wp.mobile.mcs/shared. In that folder, find and move org.apache.xalan-unbundled-2.7.1.vol5.jar and net.sourceforge.saxon-9.3.0.5.jar to a new directory, for example, wp_root/wp.mobile/wp.mobile.mcs/shared_conflict.
2. In the WebSphere Application Server admin console clickEnvironment > Shared libraries. Create a new shared variable under the server scope, for example, MCSLibConflict.
   1. In a clustered environment, create the variable in each scope. If you have a primary and a secondary node, create the shared variable for each WebSphere Portal server under each node. Use this example: If myhost is the cluster, then choose the following scope for creating the shared variable.

      Cell=myhost01Cell01, Node=myhost01, Server=WebSphere_Portal
      Cell=myhost01Cell01, Node=myhost02, Server=WebSphere_Portal

   2. In a stand-alone WebSphere Portal server, create the variable in the server scope. For example,

      Cell=myhostCell01, Node=myhost, Server=WebSphere_Portal

      Where myhost is a stand-alone server.

3. Set the class path for the shared variable. Use the new directory you defined in step 1.
4. Click Applications > Application Types > WebSphere Enterprise Applications. Choose the MCS application.
5. Click the Shared Library references link and select the check box for MCS.
6. Click the Referenced Shared Variables button. The Shared Library Mapping window appears.
7. Choose the shared library MCSLibConflict you created.
8. Click the arrow to add it.
9. Click OK to save the variable.
10. Select the second check box in the Shared Library References screen to add the shared library created earlier at both application and war level. Clicking this check box adds the references for the module.
11. Restart the WebSphere Portal server.
12. Run the command that failed earlier and follow the remaining installation steps in the information center to complete the installation.

Node synchronization problem

The following error message displays:

[6/7/10 7:30:03:620 PDT] 0000005d MBeanHelper E Could not invoke an operation on object: WebSphere:name=nodeSync,process=nodeagent,platform=common,node=wpmintel02,diagnosticProvider=true,version=7.0.0.9,type=NodeSync,mbeanIdentifier=nodeSync,cell=wpmintel01Cell01,spec=1.0 because of exception: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the isNodeSynchronized operation on NodeSync MBean because of insufficient or empty credentials.
[6/7/10 7:30:03:745 PDT] 0000005d DistributedMB E DistributedMBeanHelper isNodeSynchronized Failed to obtain Node Synch Status: {0}
javax.management.MBeanException
at com.ibm.ws.console.core.mbean.MBeanHelper.invoke(MBeanHelper.java:216)
at com.ibm.ws.console.core.mbean.DistributedMBeanHelper.isNodeSynchronized(DistributedMBeanHelper.java:840)
at com.ibm.ws.console.core.utils.StatusUtils.getNodeStatus(StatusUtils.java:173)
at com.ibm.ws.console.environment.topology.NodeDetailForm.getStatus(NodeDetailForm.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.apache.commons.beanutils.PropertyUtils.getSimpleProperty(Unknown Source)
at org.apache.commons.beanutils.PropertyUtils.getNestedProperty(Unknown Source)
at org.apache.commons.beanutils.PropertyUtils.getProperty(Unknown Source)
at org.apache.struts.util.RequestUtils.lookup(Unknown Source)

To resolve this issue, check the time in the servers. There is a 5-minute difference between the Deployment Manager, Primary node, and Secondary node (in a cluster environment). Or, between the Deployment Manager and WebSphere Portal server (in a stand-alone environment). If there is not a 5-minute difference, then refer to the technote 1405907, Managed node fails to synchronize, for detailed information for resolving the issue.

Primary node post federation fails

The following error message displays:

com.ibm.websphere.management.exception.InvalidConfigDataTypeException: ADMG0007E
: The configuration data type CellCompRegistryCollection is not valid.
at com.ibm.ws.management.configservice.TypeRegistry.getMetaObject(TypeRe
gistry.java:166)
at com.ibm.ws.management.configservice.ConfigServiceImpl.parseContainmen
tPath(ConfigServiceImpl.java:2724)
at com.ibm.ws.management.configservice.ConfigServiceImpl.resolve(ConfigS
erviceImpl.java:983)
at com.ibm.ws.management.configservice.ConfigServiceImpl.resolve(ConfigS
erviceImpl.java:956)

This particular exception implies that there is the AppServer/lib/wkplc.comp.registry.jar file is corrupted. This file exists on both the node and the Deployment manager. If it does not, this exception error message appears. In a cluster environment, make sure that you completed the step to copy files to the Deployment manager.

ConfigEngine.bat collect-files-for-dmgr

MCS deployment or Mobile Portal Accelerator prerequisite check fails

This Operating System is not supported. Please check the product documentation 
for a list of supported Operating Systems. Check the logs for more details