Slow sync of Emails or Appointments to mobile devices

  • 7007064
  • 18-Oct-2010
  • 22-May-2014


Novell GroupWise 8
Novell GroupWise 2012
Novell Data Synchronizer Mobility Pack


Emails or Appointments reach mobile devices after a long time
Slow sync of mails or appointments to mobile devices
New mails on device only after 60 min (3600 seconds).
Error: "Error with GWEvent notification [8906]:" in POA log file
Error: "Error with GWEvent notification [8906]: http://IPAddress:4500" in POA log file
Delayed Messages


  1. Verify the GroupWise connector is configured properly:
    • Launch WebAdmin by going to https://DatasyncMobilityServerIPAddress:8120
    • Login to WebAdmin.
    • Click GroupWise Connector. By default it is named groupwise.
    • Make sure that the "GroupWise Connector Server IP Address" is set to the Mobility Server IP address.
    • If a change is made click on Save Custom Settings.
    • Click on Home and restart the groupwise connector.
  2. Make sure port 4500 is open between POA and the Mobility server:
    • An easy way to confirm this is by typing "telnet x.x.x.x 4500" on the POA server where x.x.x.x is the IP Address of Mobility Server. If the Telnet succeeds, then the port is open, however if it fails then there is something between the POA and mobility server blocking the port.

      Note: If the POA is running on cluster and the secondary IP Address is bound exclusively to the POA, please make sure that the port 4500 is open between the secondary IP Address and the Mobility Server. An easy way to confirm this is by typing "telnet -b y.y.y.y x.x.x.x 4500"
      where y.y.y.y is IP Address in the POA Properties with "Bind Exclusively to TCP/IP Address" selected 
      and  x.x.x.x is the IP Address of Mobility Server
      If the "Bind Exclusively to TCP/IP Address" is selected then POA uses the secondary IP Address to connect to mobility server on port 4500. If the "Bind Exclusively to TCP/IP Address" is not selected, then the POA uses the node's IP Address to connect to mobility server on port 4500.

Additional Information

If a new email, appointment, etc. is received by the user, the POA SLAPs/notifies the GroupWise connector on port 4500. Once the notification is received by the connector, it goes ahead and requests for new the email, appointments, etc.
If POA is unable to SLAP/notify the GroupWise connector because of the communication issue, the GroupWise connector will automatically poll the POA for changes made to the user database after every 30 mins.
There are times when POA tries to SLAP mobility server and it fails. Follow the steps listed below to check if the slap has failed
  1. Login to the POA WebConsole (It is important that the POA WebConsole is protected with user and password for these steps to work. If the POA WebConsole does not have user and password, then the following options cannot be seen. Please click on the following link and click on "Using the POA Web Console" and setting the HTTP user and password
  2. Once logged in, please click on Configuration | SOAP Notification List
  3. Search for the user account in question and make sure the IP Address points to the mobility server and check the time stamp. If the time stamp does not have an asterisk besides it, then the slap failed. If the time stamp has an asterisk  besides it, then the last slap was successful at that time
    Force a slap by restarting mobility services
    • Click Configuration | Event Configuration List
    • Search for the user in question
    • Click on the user account
    • Select "Add to Notification List"
    • Click Submit