CDC Software has published a Service Pack for Pivotal Sync Stream 5.9.
Service Pack adds number of functionalities to Outlook Synchronization Manager tool, as well as corrects several reported mistakes.
Service Pack’s installation is necessary for a proper functioning of
LinkPoint for Pivotal CRM, which enables an integration of e-mail with Lotus Notes server and Novell GroupWise.
Below you can find a detailed list of changes introduced by the Service Pack.
Additional Features Added in Service Pack 3
64270
The Outlook Synchronization Manager (OSM) now sends an e-mail notification if it shuts down due to a database connection failure.
The recipient address is specified by the following registry key:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Pivotal\SyncStream\OSM
Name: NotificationAddress
String Value: <Email address of user to be alerted>
64208
The OSM now archives old logs. By default, the OSM starts a new log once the current log is either 1 day old or 10 MB in size. The OSM archives old logs by renaming them to OSMLog YYYY-MM-DD hh.mm.ss.txt. By default, archived logs are deleted after 90 days.
64368
Improved the speed of the OSM startup scan.
64395
Added log statistics for the Outlook scan about the number of the items deleted, modified or not synchronizing.
64474
The OSM now attempts to restart if it loses connection to the Active Notification Manager (ANM).
Issues Addressed in Service Pack 3
64207
Resolved issue where the OSM did not restart if the computer restarted while OSM was running.
64273
Resolved issue where OSM Log reported issues of certain activity records that did not pass the filter.
64274
Resolved issue where the OSM did not restart after an Upgrade From Offline System (UFO) process was completed.
64282
Resolved issue where accented characters were not converted correctly during a System Restore on Oracle.
64283
Resolved issue where the OSM did not attempt to reconnect to the system if the database connection was lost.
64303
Resolved issue where, if a Resync Databases operation was running under a user other than the DSM user, the DSM would not restart after the Resync completed.
64243
Resolved issue where the This is the mailing address check box on the Contact form was not set properly.
64290
Resolved issue where the contact synchronization record was not updated with the Outlook timestamp.
64367
Resolved issue where the OSM did not delete a synchronization record after the corresponding task or appointment was deleted.
64393
Resolved issue where the OSM shut down after deleting contacts in Outlook.
64413
Resolved issue where the OSM did not process additions from Lifecycle Server. The OSM now retries three times if the record is not found.
64426
Resolved issue where the satellite DSM shut down during the UFO.
64212
Resolved issue where the OSM repeatedly updated the same record.
64445
Resolved issue where on a mobile configuration, in case of any error at the startup of the transport (by HttpSyncstat), the number of the transport worker threads would grow indefinitely.
64440
Resolved issue where, on mobile configurations, in some cases, the shutdown process took a very long time because of the DSM.
64449
Resolved issue where the PivotalTraceClient did not have a recycling mechanism for the generated logs
64453
Resolved issue where the Sender section of the transport failed to recover transitory chunks.
64484
Resolved issue where the results of an Audit Synchronization were displayed in the wrong instance of eRelationship Enterprise Manager if more than one eRelationship Enterprise Manager instances were open and connected to the same system.
