Riva Delays Syncing Items between GroupWise 2012

Several customers reported an issue with Riva not syncing calendar items for several hours after the user saved the create of a calendar item.  The customer was hosting GroupWise 2012 on OES Linux servers and the Riva 2.4.34.

Error in the Log

Examination of the crmgw log file revealed:

Cause

This customer was located in Eastern US in "Eastern Time Zone" and the time zone offset between UTC and Eastern was 4 hours.  It appears that Riva was not picking up the correct time offset for GroupWise.

Internal lab testing confirmed that this issue only affects GroupWise 2012.  Earlier versions of GroupWise do not suffer from the same errors.

Resolution

The following procedure has resolved this issue for several customers:

1. Upgrade Riva to 2.4.35+.

2. On the server hosting GroupWise, set the local clock to use UTC.

3. On the server hosting GroupWise, ensured that ntp is using local time (e.g. Central)

4. On the server hosting GroupWise, the OS time is set to local time (e.g. Central)

5. Add or modify the Omni.Riva.CrmAgent.exe.config file to include only highlighted line from this example:

   <?xml version="1.0" encoding="utf-8"?>
   <configuration>
     <appSettings>
       <add key="GwSoap.GetServerTime.UseServerLocal" value="True" />
     </appSettings>
   </configuration>


6. In the CRM Monitor application, RESTART the sync service.

7. After a sync cycle for a user completes, check the newest crmgw-log file and confirm that there are no "large time difference" errors.

Applies to

• Riva On Premise for GroupWise 2012 and Salesforce