Environment
Novell Data Synchronizer 1.1
Novell Data Synchronizer Connector for GroupWise
Novell Data Synchronizer Connector for GroupWise
Situation
Following is excerpt from GroupWise Connector AppInterface log:
INFO_VERBOSE [Thread-4] [gwconnectorlogic:997] [userID:<user_ID>] [eventID:] [objectID:] [ItemHandler] Engine rejected event: <information related to user, event, or Domain/PO>|<user_ID>
ERROR_VERBOSE [Thread-4] [gwconnectorlogic:998] [userID:] [eventID:] [objectID:] []
<result>
<status>
<code>11</code>
<desc>Add requested by pipeline</desc>
</status>
<event>
<metadata/>
</event>
</result>
INFO_VERBOSE [Thread-4] [gwconnectorlogic:997] [userID:<user_ID>] [eventID:] [objectID:] [ItemHandler] Engine rejected event: <information related to user, event, or Domain/PO>|<user_ID>
ERROR_VERBOSE [Thread-4] [gwconnectorlogic:998] [userID:] [eventID:] [objectID:] []
<result>
<status>
<code>11</code>
<desc>Add requested by pipeline</desc>
</status>
<event>
<metadata/>
</event>
</result>
Resolution
At the time this TID was written, build 428 (1.1.2) was available to the public.
The resolution may depend on upon the item(s) that this issue is failing on. Currently this issue is believed to be fixed relating to appointments in builds after June 28th, 2011. When this error is returned by the Sync Engine, we will now check the type of event that was being sent. If the event is a delete or a decline appointment, we'll just ignore the error and delete the event. All other events will continue to be put in the same error state. If running a DataSync build that is newer then June 28th 2011, and this error is seen, please contact Novell Technical Support for assistance, as Novell Development will need to examine the items that are triggering this error.
The resolution may depend on upon the item(s) that this issue is failing on. Currently this issue is believed to be fixed relating to appointments in builds after June 28th, 2011. When this error is returned by the Sync Engine, we will now check the type of event that was being sent. If the event is a delete or a decline appointment, we'll just ignore the error and delete the event. All other events will continue to be put in the same error state. If running a DataSync build that is newer then June 28th 2011, and this error is seen, please contact Novell Technical Support for assistance, as Novell Development will need to examine the items that are triggering this error.
Additional Information
The impact to end users is currently not known, but can happen any
any type of sync event. The impact may depend upon the type of sync events.
The error getting reported in this case ("Add requested by pipeline" with status code 11) indicates that the Sync Engine no longer knows about the object that the event is associated with. For example, this could happen when an email is deleted from the GroupWise Client and then some action is performed on that same email from the users device before the delete syncs through the system.
An example for one customer, what was seen were two types of events coming through ... MeetingResponse requests with a decline (this is a distributed appointment that the user is declining) and also deletes for calendar items. Since both of these event types lead to the appointment getting deleted anyway, there really wasn't a problem and did not impact the user. The delete action has already occurred in the SyncEngine and hence it had probably already been deleted in GroupWise. Novell Development is looking to drop the events and not keep them in the error state in the database for a future release on a case by case scenario.
The error getting reported in this case ("Add requested by pipeline" with status code 11) indicates that the Sync Engine no longer knows about the object that the event is associated with. For example, this could happen when an email is deleted from the GroupWise Client and then some action is performed on that same email from the users device before the delete syncs through the system.
An example for one customer, what was seen were two types of events coming through ... MeetingResponse requests with a decline (this is a distributed appointment that the user is declining) and also deletes for calendar items. Since both of these event types lead to the appointment getting deleted anyway, there really wasn't a problem and did not impact the user. The delete action has already occurred in the SyncEngine and hence it had probably already been deleted in GroupWise. Novell Development is looking to drop the events and not keep them in the error state in the database for a future release on a case by case scenario.