A.0 GroupWise Mobility Service Installation Troubleshooting

See also the following sections in the GroupWise Mobility Service 2.1 Administration Guide:

The GroupWise Mobility Service Installation program does not behave as documented

Possible Cause: You are trying to install the GroupWise Mobility Service on 32-bit hardware.
Action: Install the GroupWise Mobility Service on 64-bit hardware that meets the system requirements described in Section 2.1, Mobility Server Requirements.

The GroupWise Mobility Service Installation program cannot communicate with the LDAP server

Possible Cause: A firewall is blocking communication between the Installation program and the LDAP server.
Action: Ensure that communication through the firewall is allowed on port 636 for a secure LDAP connection or port 389 for a non-secure LDAP connection.
Possible Cause: The LDAP server is not functioning correctly.
Action: Restart the LDAP server.
Possible Cause: You specified the LDAP server settings incorrectly.
Action: Double-check the LDAP server settings you entered in the Installation program.

The GroupWise Mobility Service Installation program cannot communicate with the GroupWise POA

Possible Cause: A firewall is blocking communication between the Installation program and the POA server.
Action: Ensure that communication through the firewall is allowed on port 4500.
Possible Cause: The POA is not running.
Action: Start the POA.
Possible Cause: You specified the POA server settings incorrectly.
Action: Double-check the POA server settings you entered in the Installation program.
Possible Cause: There is a problem with the GroupWise trusted application key file.
Action: Re-create the GroupWise trusted application key file. You need to fill in only these three fields in the New Trusted App Key dialog box in the GroupWise Admin console (or in the Create Trusted Application dialog box in ConsoleOne in older GroupWise systems): Name, Location for Key File, and Name of Key File. Do not fill in any other fields.

The GroupWise Mobility Service Installation program cannot communicate with any required application

Possible Cause: The required port number is not open.
Action: Review the list of required port numbers in Section 3.2.2, Opening Required Ports.
Action: Use telnet to test whether ports are open.

  1. Enter the following command in a terminal window:

    telnet application_host port_number

    Replace application_host with the IP address or DNS hostname of the server where the application is running.

    Replace port_number with the port number on which the Installation program is attempting to communicate with the application.

  2. (Conditional) If the terminal windows goes blank, with the cursor in the upper-left corner, enter quit to exit the telnet session.

    The port is open. The Installation program should be able to communicate with the application.

  3. (Conditional) If a Connection failed message displays, open the port through the firewall to enable the Installation program to communicate with the application.

The Mobility Service does not start

Possible Cause: PostgreSQL is not running on the Mobility server.
Action: Check the status of PostgreSQL on the Mobility server, and start it manually if necessary. 
rcpostgresql status
rcpostgresql start

You cannot access the Mobility Admin console after installation

Possible Cause: The date and time on the Mobility server does not match the date and time on the GroupWise server.
Action: Reset the time on the Mobility server to match the time on the GroupWise server. This Mobility system requirement is listed in Section 2.1, Mobility Server Requirements.

A reinstallation of the Mobility Service software does not proceed normally

Possible Cause: The previous installation of the Mobility Service software was not completely uninstalled.
Action: The standard uninstallation procedure provided in Section 3.3.5, Uninstalling the Mobility Service occasionally fails to completely uninstall the GroupWise Mobility Service because of various server-specific issues. When the Mobility Service software is not completely uninstalled, the next installation does not proceed normally. For example, you might encounter problems configuring LDAP access during installation.

  1. To ensure that the Mobility Service software has been completely uninstalled, perform the following checks:

    • In YaST, click Software > Add-On Products.

      The GroupWise Mobility Service should not be listed. If it is still listed, select it, then click Delete.

    • In YaST, click Software > Software Repositories.

      The GroupWise Mobility Service repository should not be listed. If it is still listed, select it, then click Delete.

    • In YaST, click Software > Software Management. In the Filters drop-down list, select Patterns.

      Under the Primary Functions heading, the GroupWise Mobility Service should not be listed. If it is still listed, select it. Review the Packages list for any packages that were not successfully uninstalled and uninstall them.

    • In YaST, click Software > Software Management. In the Search field, specify datasync, then click Search.

      The Packages list should be empty. If any Mobility Service packages are still listed, uninstall them.

    • Log in as root in a terminal window, then check for Mobility Service RPMs:

      rpm -qa | grep datasync

      If any Mobility Service RPMs are still installed, uninstall them:

      rpm -e rpm_name.rpm

    • Ensure that none of the following directories still exist on your server:

      /opt/novell/datasync
/etc/datasync
/var/lib/datasync
/var/log/datasync
/var/run/datasync
/var/lib/pgsql

      If any of these directories still exist, delete them.

  2. After your performing these checks and making changes as needed, restart the Mobility server.

  3. Remove the Mobility certificate from any workstations where you have run the Mobility Admin console.

    For example, in Firefox, click Tools > Options > Advanced > Encryption > View Certificates. Select the certificate named DataSync Web Admin, then click Delete.