Environment
Novell GroupWise 7 Support Pack 2
Novell GroupWise Mobile Server 2
BlackBerry Enterprise Server
LightSpeed Systems Total Traffic Control Message Journaling
BlackBerry Enterprise Server
LightSpeed Systems Total Traffic Control Message Journaling
Situation
Web PIM not updating properly after initial creation and synchronization of user.
Newly created users may work temporarily and/or sporadically to receive updates to the PIM.
Mail not synching to PIM or device.
Newly created users may work temporarily and/or sporadically to receive updates to the PIM.
Mail not synching to PIM or device.
Resolution
The issue is fixed in GroupWise 7 Support Pack 3 or later
If the update to GroupWise 7 Support Pack 3 or later does not resolve the issue straightway, it may be necessary to remove duplicate event notifications. If this is the case, it is recommended that the GMS users are deleted and then recreated post-update. It is not recommended that a second Post Office Agent be created to work on a separate SOAP port from other SOAP-enabled applications that will be accessing the Post Office.
If the update to GroupWise 7 Support Pack 3 or later does not resolve the issue straightway, it may be necessary to remove duplicate event notifications. If this is the case, it is recommended that the GMS users are deleted and then recreated post-update. It is not recommended that a second Post Office Agent be created to work on a separate SOAP port from other SOAP-enabled applications that will be accessing the Post Office.
Additional Information
A problem was discovered that may impact applications that use GroupWise Events, such as GroupWise Mobile Server (GMS) or GW BES. Users may see erratic synchronization behavior. The problem is that one application could potentially read and delete events stored for another application.
Whereas, with some conflicting applications such as BES, the synchronization may be erratic. With other applications the synchronization may never work after the initial creation of the user. Some programs such as LightSpeed Journaling software use the same default SOAP port and will constantly poll the Post Office for updates to synchronize with its messaging archive. This will effectively cause GMS to stop all updates as it polls the Post Office and finds that no updates are available. GroupWise 7 Support Pack 3 or later prevents this issue, but may not fix latent problems that were created in the older code. If the resolution section of this document does not resolve the problem, please contact Novell Technical Support for assistance.
Whereas, with some conflicting applications such as BES, the synchronization may be erratic. With other applications the synchronization may never work after the initial creation of the user. Some programs such as LightSpeed Journaling software use the same default SOAP port and will constantly poll the Post Office for updates to synchronize with its messaging archive. This will effectively cause GMS to stop all updates as it polls the Post Office and finds that no updates are available. GroupWise 7 Support Pack 3 or later prevents this issue, but may not fix latent problems that were created in the older code. If the resolution section of this document does not resolve the problem, please contact Novell Technical Support for assistance.
