(Master TID) Mobility unable to communicate with GroupWise POA

  • 7014498
  • 03-Feb-2014
  • 06-May-2020

Environment

Novell GroupWise Mobility Service 2.0
Novell Data Synchronizer Mobility Pack
GroupWise Mobility Service 18

Situation

No mail, contacts, calendar syncing to Mobility server from GroupWise POA's or Post Offices.
Mobility unable to communicate with GroupWise POAs.
DataSync can't communicate with GroupWise.
Sync is not working.

Resolution

The Mobility server may be unable to communicate for several reasons:

  1. Double-check the POA server settings in WebAdmin. Try connecting in a terminal window:
    telnet <serverAddressofPOA> 7191
    Note: If the connection hangs or refuses to connect (not returning anything), see steps 2, 3).

    Here is an example of a successful connection:

    mobility:~ # telnet 151.155.215.91 7191
    Trying 151.155.215.91...
    Connected to tharris3.lab.novell.com.
    Escape character is '^]'.

    HTTP/1.0 500
    Date: Mon, 03 Feb 2014 08:24:24 GMT
    Server: Linux GroupWise POA 12.0.2
    Content-Type: text/html
    X-GWError-Code: 0x892B
    Pragma: no-cache

    Connection closed by foreign host.


  2. A firewall is blocking communication between Mobility and the POA server. See TID 7009520 for a list of ports.
    Note: Ports 7191 and 4500 should be open.

  3. The POA doesn't have SOAP enabled. See GroupWise Administration - Section 36.2.4, Supporting SOAP Clients.
    • From ConsoleOne, properties of POA, GroupWise | Agent Settings | SOAP protocol is enabled.

  4. (Conditional) If the GroupWise URL contains HTTPS, there might be a misconfiguration of SOAP over SSL.
    • Check properties of the POA, GroupWise | SSL Settings | provide certificate and SSL key files location and then restart the POA.
    • Check properties of the POA, GroupWise | Network Address | check SOAP protocol port and enable SSL.

  5. There is a problem with the GroupWise trusted application key file. 
    • Verify the TCP/IP Address is left blank, ConsoleOne | Tools | GroupWise System Operations | Trusted Applications. Edit the Trusted Application Key for Mobility.
      Note: This step might explain proper sync for a single POA, but no others.
    • See TID 7012632.

  6. If the Mobility server was recently updated or suspicion of database corruption:
    • From a terminal window, stop Mobility services: rcdatasync stop OR rcgms stop
    • Run /opt/novell/datasync/update.sh
      Note: This configures the mobility database and is required with any Mobility updates.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.