test

Sun Java System Communications Express 6 2005Q4 Administration Guide

Troubleshooting Commonly Identified Problems

This section provides an overview of problems that can be encountered during installation, configuration, start-up, or while accessing Communications Express user interface client components.

Listed below are some commonly identified problems in Communications Express components and their possible causes.

Configuring Communications Express

Configuration changes are not reflected, even after restarting the web container.

Make sure the configuration changes have been applied to the files in the appropriate config path.

Once Communications Express configuration is completed, the following configuration directories are created in your system:

To ensure that the changes are reflected in your application, make configuration changes to uwc-deployed-path/WEB-INF/config

The other two directories such as uwc-deployed-path/ staging/WEB-INF/config and uwc-basedir /SUNWuwc/WEB-INF/config are temporary place holders created and used internally by the configurator during configuration. Changes made in them will not get reflected in the application.

Configuration tasks have failed.

To locate the problem, use the log file located at uwc-basedir /SUNWuwc/install/uwc-config _TIME-STAMP .log

Where, TIME-STAMP is the time stamp of the configuration in the form YYYYMMDDhhmmss.

Configuration program is not working properly.

To identify the problem, invoke the configuration program with debug options enabled, using the following debug modes:

-debug : Use this option to generate general debug information

-debugMessage : Use this option to generate a log of errors and warnings

-debugWarning : Use this option to generate a log of warning messages and error messages

-debugError : Use this option to generate a log of error messages. By defaut this option is enabled.

UWC applications startup failed and web container logs shows exceptions.

This error might have occurred due to an incomplete or incorrect configuration.

Work around.

The “chown” commands have failed during configuration.

Work around.

Run the configuration program and enter the correct web container user and group values in the “Web Container User and Group” panel of the configuration program.

The message, “An error occurred during this operation” appears when you access Communications Express with Access Manager enabled after authentication.

Work around.

Ensure that uwcauth.identity.binddn and uwcauth.identity.bindcred properties in uwc-deployed-path/WEB_INF/config/uwcauth.properties are set to that of the amAdmin DN that was provided when installing Access Manager SDK. Refer to the section on Configuring Access Manager Parameters in uwcauth.properties File

Although the directory manager credentials may be provided to uwcauth.identity.binddn and uwcauth.indentity.bindcred for Access Manager SSO, the directory manager does not have the ACLs required to obtain certain domain specific attributes that Communication Express depends on to function properly.

No support to modify web-container configuration for Access Manager SDK integration.

The configurator does not support modification of web-container configuration for Access Manager SDK integration.

Work around.

Manually invoke tools provided with Access Manager to modify web container configuration for Access Manager.

Messaging SSO is not supported in SSL.

Work around

To support Messaging SSO with SSL perform the following steps:

ProcedureHow to enable Messaging SSO with SSL

Steps

  1. Configure Web Server in SSL mode.

  2. Configure Communications Express for SSL port of Web Server.

  3. Set uwcauth.ssl.enabled=true.

  4. Set uwcauth.https.port to SSL port of Web Server.

  5. Enable Messaging Server in SSL mode.

  6. Set the webmail.port in uwcconfig.properties to SSL port of Messaging Server.

  7. Provide messagingsso.ims.url to Non SSL port of Messaging Server

  8. Install the Certificate Management Server root Certificate Authority (CMS root CA) on both Web Server and Messaging Server.

  9. Restart Web Server.

  10. Provide a value to local.webmail.sso.ims.verifyurl pointing to Non SSL port of Messaging Server.

  11. Restart Messaging Server.

Accessing Calendar

The message, “An error occurred during this operation” appears when you access Calendar from Communications Express.

This error can appear because of either one or more of the following reasons.

The message, “Calendar Not Available. Could Not Display View. The selected calendar(s) was either deleted, or does not exist, or you do not have permissions to view it. Select another calendar(s)” appears when you access Calendar from Communications Express.

This error can occur when users are provisioned using commcli, which is used for Schema 2, in a non-hosted domain setup scenario. The error message is displayed because commcli incorrectly appends @domain to the value of icsCalendar attribute in the user’s LDAP entry.

Work around

To provision users using commcli in a non-hosted domain environment, use the -k legacy option in the commadmin command. For a Hosted domain environment, use -k hosted option. If the -k option is not specified a hosted domain setup is assumed.

For example,

Example 5–1 Commcli provisioning


./commadmin user create -D admin -w password -X 
siroe .varrius .com -n siroe.varrius.com -p 85 -d 
siroe.varrius.com-F test -L user2 -l user2 
-Wuser2 -S mail,cal -k legacy
ok

or

If the entry corresponding to an already provisioned user cannot be removed, manually remove the '@domain ' part from icsCalendar, icsSubscribed and icsOwned attributes.

The messages, “Calendars across the domain cannot be searched,” “Calendars across the domain cannot be invited,” “Calendars across the domain cannot be subscribed,” or “Check Availability for Calendars across the domain cannot be done,” appears when you search, invite, subscribe, or check the availability of Calendars across domains from Communications Express.

Work around

To search, invite, subscribe, or check the availability of calendars, Cross Domain search needs to be enabled. Refer to the section on “Enabling Cross Domain Searches” in Chapter 13 of the Calendar Server 6 2005Q1 Administration Guide.

Issues with Default Event Status Filter.

The Default Event Status Filter in the Options Calendar window specifies the events to be displayed in the day, week, and month calendar views. The options available are: Accepted, Tentative, Declined, No Response.

When the “Accepted” option is selected as the event status, only those invitations you have accepted are displayed in the day, week or month calendar views. However, all events created by you are always displayed in day, week, or month calendar views.

In the Options Calendar Window, by default only “Accepted” and “Tentative” are selected, which means as a user, you will not see events you have declined or to which you have not responded as yet.

Work around

To view all the events in the Day, Week, Month, and Year views, you should select all the options, that is, Accepted, Tentative, Declined, No Response in the Options Calendar window.

Communications Express displays "Server Error" while uploading files greater than 2 MB.

This error occurs while importing events and tasks to a calendar or importing contacts to an address book when the uploaded file size is greater than 2 MB.

By default Communications Express allows import of upto 2 MB file data. However, upload file size limit is configurable.

Work around

Configure a greater upload file size limit.

To configure a greater upload file size limit configure the following init parameters for the filter, MultipartFormServletFilter in web.xml:

For example, to increase the upload file size to 10MB, follow the configuration steps mentioned below:

ProcedureIncreasing the upload file size

Steps

  1. Take a backup of the existing web.xml from uwc-deployed-path/WEB-INF/web.xml.

  2. Edit the web.xml file at uwc-deployed-path /WEB-INF/web.xml.

  3. Provide the configuration for MultipartFormServletFilter in web.xml as indicated in bold in code example 5-2.


    <web-app\>
..
..
  <filter\>
    <filter-name\>MultipartFormServletFilter</filter-name\>
    <filter-class\>com.sun.uwc.calclient.MultipartFormServletFilter</filter-class\>
    ..
    ..
    <init-param\>
      <param-name\>fileSizeHardLimit</param-name\>
      <param-value\>10485760</param-value\>
      <description\>Ten mega bytes</description\>
    </init-param\>
    <init-param\>
      <param-name\>requestSizeLimit</param-name\>
      <param-value\>10485760</param-value\>
      <description\>Ten mega bytes</description\>
    </init-param\>
    <init-param\>
      <param-name\>fileSizeLimit</param-name\>
      <param-value\>10485760</param-value\>
      <description\>Ten mega bytes</description\>
    </init-param\>
    <init-param\>
      <param-name\>failureRedirectURL</param-name\>
      <param-value\>put your url here</param-value\>
      <description\>Request is redirected to this url when 
uploaded file size crosses
fileSizeHardLimit value</description\>
    </init-param\>
    ..
    ..
  </filter\>
..
..
..
..
</web-app\>

  4. Restart web container to have the changes take effect.

ProcedureAccessing Address Book

A “Server Error” occurs when Address Book is accessed. The Web Server log records an exception “org.apache.xml.utils.WrappedRuntimeException: The output format must have a ’{http://xml.apache.org/xslt}content-handler’ property!”

This exception is thrown by Web Server when JDK Web Server points to a version lower than JDK 1.4.2. The Communications Express uses the latest version of xalan and xerces for XML/XSL parsing. This error can appear when:

Steps

  1. You are using Web Server 6.1 not deployed using JES installer. JDK 1.4.1 is usually bundled with Web Server 6.1.

  2. The version of the shared xalan and xerces components shipped with Java Enterprise System, are not the latest.

    Work around

    • If the error appears because you have not installed Web Server from the JES installer, manually upgrade the JDK version of the web container that is defined as java_home attribute of java tag in server.xml Web Server configuration file.

      or

      Re-install webserver from Java Enterprise System, and have the install process upgrade JDK automatically.

    Note –

    If this step is performed, all the other web-applications must be redeployed. As a precaution, take a backup of the server.xml file.

    • If the error appears because the version of the shared xalan and xerces components are not the latest, remove the symbolic links for xalan.jar and xerces.jar from uwc-deployed-path/WEB-INF/lib.

      For example:

      # cd /var/opt/SUNWuwc/WEB-INF/lib

      # rm xalan.jar xercesImpl.jar

      Then, restart the Web Server.

    The message “An error occurred during this operation” appears when Address Book is accessed from Communications Express.

    This error occurs when the LDAP configuration for Personal Address Book (PAB) is not correct. When the Address Book tab is accessed, Communications Express connects to the personal address book store, that is, the LDAP configured for PAB. If the personal address book store is unable to establish a connection, the error is displayed.

    Work around

  3. Check the LDAP configuration in WEB-INF/config/ldappstore/db_config.properties .

  4. Edit the incorrect configuration settings.

  5. Restart the Web Server where Communications Express is deployed.

    For more information, refer to the section Configuring Corporate Directory Parameters db_config.properties File

    Corporate Directory shows an inline error when search is performed.

    This could happen if LDAP configuration for Corporate Directory is not configured properly.

    Work around.

    Check the LDAP configuration in WEB-INF/config/corp-dir/db_config.properties for any misconfigurations, correct them and then restart Communications Express.

    For more information, refer to the section Configuring Corporate Directory Parameters db_config.properties File

    Viewing contacts of Corporate Directory shows error in View window

    This error is displayed when the key to access a contact entry in Corporate Directory is not “uid.”

    uid is the default value set by Communications Express.

    Work around

    To access the contacts from Corporate Directory the key value should be set to the desired value in db_config.properties and xlate-inetorgperson.xml configuration files in uwc-deployed-path/WEB-INF/config.

    Make the following changes in the files:

  6. Set the appropriate key value in uwc-deployed-path /WEB-INF/config/WEB-INF/config/corp-dir/db_config.properties.

  7. Set the appropriate key in place of “uid” in entry entryID="db:uid" in

    uwc-deployed-path/WEB-INF/config/WEB-INF/config/corp-dir/xlate-inetorgperson.xml .

  8. Restart the Web Server where Communications Express is deployed.

    For more information, refer to the section Configuring Corporate Directory Parameters db_config.properties File

    The value of psRoot cannot be set.

    The LDAP attribute psRoot in User Preferences is used for Addressbook Server Horizontal Scalability. For more details, see the section, Supporting Horizontal Scalability of Addressbook Server deployment does not require Addressbook Server Horizontal Scalability, you may ignore this error.

    When a user logs into Communications Express for the first time, the psRoot is attempted to be set automatically, but sometimes the value may not be automatically set. This typically happens when the Java Enterprise System Directory Server has not been installed and comm_dssetup.p1 for Java Enterprise System has not be run after installing Java Enterprise System Directory Server. This results in the LDAP Schema not being updated.

    Since the schema is not updated, the psRoot attribute cannot be manually set even when the attribute is required for a horizontally scalable Addressbook Server deployment.

    Work around

    To enable the setting of the psRoot attribute, update the Directory Server to include the psRoot attribute. To do this, include the attribute psRoot in the definition of ipUser object class in

    Directory ServerInstance/ config/schema/99user.ldif.

    Note –

    You need to update the Directory Server to include the psRoot attribute only if in the current deployment, the Java Enterprise System Directory Server has not been installed and you have not run comm_dssetup.p1 for Java Enterprise System after installing Java Enterprise System Directory Server.

Accessing Mail

Login page appears when Mail tab is clicked.

This problem is noticed when the configuration between Communications Express and Messaging Server is not done properly. For Messaging Server and Communications Express to work seemlessly, Messaging or Access Manager Single Sign-On should be enabled. Before starting Communications Express, follow the instructions outlined for Single Sign-on configuration in Chapter 1, Overview of Communications Express

The message “An error occurred during this operation” appears when Mail is accessed from Communications Express.

This error appears when the mail component of Communications Express is not deployed or enabled, but the user logging into Communications Express has set Mail to be the default application.

Work around

The Administrator needs to change the value of the attribute sunUCDefaultApplication in the user’s LDAP entry to “calendar” or “addressbook.”

The user remains logged in even after logging out of Communications Express.

This problem is encountered when Access Manager (formerly known as Identity Server) and Communications Express are installed on different machines and Access Manager Remote SDK is installed in the machine where Communications Express is installed.

Work around

In the machine on which Communications Express is installed, specify the following configuration parameter in AMConfig.properties file:

com.iplanet.am.notification.url=url-to-access-web-container-of-CommunicationsExpress /servlet/com.iplanet.services.comm.server.PLLRequestServlet

Note –

AMConfig.properties file can be found under IS-SDK-BASEDIR/SUNWam/lib

You may encounter the following problems when accessing Address book features from Mail:

It is mandatory to deploy Communications Express and Messenger Express (MEM) on the same host to enable them interoperate using Javascript in the browser.

Authenticating using Access Manager

Unable to authenticate after entering valid userid and password.

Authentication could fail for the following reasons: