Changes made to one single contact in Personal Address Book in GroupWise Client does not sync to Device

  • Document ID:7008002
  • Creation Date:27-Feb-2011
  • Modified Date:10-Dec-2013
    • Micro Focus Products:
      GroupWise
      GroupWise Mobility Service

Environment

Novell GroupWise 8
Novell Data Synchronizer 1.0
Novell Data Synchronizer Mobility Pack

Situation

Changes made to one single contact in Personal Address Book in GroupWise Client does not sync to Device
Changes made to a contact in GroupWise Client does not sync to the Device
Modifications to a single contact in Personal Address Book does not sync to the Device
Modifications to all other contacts in Personal Address Book syncs to the Device

Resolution

This happens if the objectMappings table in the datasync database not contain a mapping for that contact in Mobility database. If it needs to be confirmed that this is the same issue, please follow the steps in the Additional Information to confirm if it is the same issue before performing the Workaround steps.
 
If this issue happens only on one contact, please follow the steps listed below
  1. Export the Contact from the GroupWise Client.
  2. Delete it from the Personal Address Book.
  3. Import the Contact again from the GroupWise Client.

Status

Reported to Engineering

Additional Information

Notes:
  1. Launch GroupWise Client and click Address Book.
  2. Switch to the Address Book and right click on the problem contact and click Details.
  3. Click the Advanced Tab.
  4. Make sure "All Contact Properties" is selected in Properties.
  5. Scroll down to "Record ID" and copy the Value. It should be something like 4D67C2B3.mygwdom1.mygwpo1.104.1377770.1.15.1
  6. Now on the Mobility Server, change the GroupWise Connector log level to Debug/Verbose/Diagnostic by following the steps in the TID below for GroupWise Connector
    https://support.microfocus.com/kb/doc.php?id=7006823&sliceId=1&docTypeID=DT_TID_1_1&dialogID=208317153&stateId=0 0 208315396 0 208315396
  7. Once the logging level has been set to Debug/Verbose/Diagnostic in GroupWise Connector, modify the contact in GroupWise Client
  8. Connect to a terminal session on the Mobility Server and find the creationEventID for that object on the Mobility Server by typing the following commands
    • cd /var/log/datasync/connectors
    • cat default.pipeline1.groupwise-Appinterface.log | grep "clientMessageId:4D67C2B3.mygwdom1.mygwpo1.104.1377770.1.15.1" -A 30 | grep -m 1 creationEventID    (Replace 4D67C2B3.mygwdom1.mygwpo1.104.1377770.1.15.1 with the Record ID noted in step 5)
    • Note down the creationEventID. It should be something like default.pipeline1.groupwise-source-soapbridge.9e1b882f42a711e0bbc3000c29fceb57
  9. Once the creationEventID is known, please type the following commands to correct the objectMappings table in the DataSync database
    • Type psql -U datasync_user datasync and press Enter
    • Enter in the database password. If the database password is not known, please check /etc/datasync/configengine/configengine.xml file as the password is stored in plaintext in the following format
            <db>datasync</db>
            <username>datasync_user</username>
            <password>novell</password>
    • Once the password has been entered, please type select * from "objectMappings" where "creationEventID" = 'default.pipeline1.groupwise-source-soapbridge.c503ce4a306611e0b47878e7d1e02098';   (Replace default.pipeline1.groupwise-source-soapbridge.c503ce4a306611e0b47878e7d1e02098 with the creationEventID that was noted in step 8) (Also make sure to put a ; (semi-colon) at the end of the command as shown in the above example)
    • If everything is proper, then there should be two entries similar to the following
               connectorID         |                   objectID                   |                                creationEventID
      -----------------------------+----------------------------------------------+--------------------------------------------------------------------------------
       default.pipeline1.groupwise | 4D67C2B3.mygwdom1.mygwpo1.104.1377770.1.15.1 | default.pipeline1.groupwise-source-soapbridge.c503ce4a306611e0b47878e7d1e02098
       default.pipeline1.mobility  | d7fcbad742b111e0bbc3000c29fceb57             | default.pipeline1.groupwise-source-soapbridge.c503ce4a306611e0b47878e7d1e02098

      However, if the problem exists, then there would be only one entry

               connectorID         |                   objectID                   |                                creationEventID
      -----------------------------+----------------------------------------------+--------------------------------------------------------------------------------
       default.pipeline1.groupwise | 4D67C2B3.mygwdom1.mygwpo1.104.1377770.1.15.1 | default.pipeline1.groupwise-source-soapbridge.c503ce4a306611e0b47878e7d1e02098