Use the form below to enter your search criteria. By default, all content is searched except for document comments. If you wish to search comments as well as everything else, click "Also Search Comments" below.
[829]
Comments: 0,
Last Modified: Apr 18, 2008 9:05 AM
- Find Similar
Expected behavior for calendar events synchronizing between FirstClass and NotifyLink. The following situations are expected behavior for calendar events synchronizing between FirstClass and NotifyLink. I. Calendar events created on the server without a subject synchronize to the device with "No Subject" in the subject field.II. Calendar events created on the device with the start
[830]
Comments: 0,
Last Modified: Apr 22, 2008 4:15 PM
- Find Similar
Port Requirements for NotifyLink Enterprise Server - FirstClass Installations Port Requirements for NotifyLink Installation can be found in the NotifyLink for FirstClass Pre-Installation Guide under Pre-Installation Tasks #8, Port Requirements Port numbers used for connections with NotifyLink Enterprise Server (NLES) components are well-known default TCP port numbers, but are subject
[794]
Comments: 0,
Last Modified: Apr 11, 2008 5:14 PM
- Find Similar
Email/PIM notifications to the device cannot be tracked for FirstClass user accounts. The folder necessary for tracking notifications cannot be created in FirstClass, thus email/PIM tracking notifications to the device cannot be tracked. "Track Notifications" enabled in the Server IT Policies > Control Options will not implement this feature.
[814]
Comments: 0,
Last Modified: Apr 17, 2008 10:18 AM
- Find Similar
List of PIM (calendar event, contact, task)fields that will not synchronize between FirstClass and NotifyLink. Some PIM fields will not be synchronized between FirstClass and NotifyLink. Calendar ... to FirstClass -Exceptions -Suffix -Prefix/Title ... addresses (1st Email syncs) FirstClass fields that do not sync
[790]
Comments: 0,
Last Modified: Apr 14, 2008 4:10 PM
- Find Similar
FirstClass ignores NotifyLink LookBack/LookAhead reanges and uses its own "Synchronize only after date" setting. LookBack/LookAhead ranges set in either the NotifyLink Administrative or Client web ... event and task synchronization ranges are governed by the FirstClass server. Work Around Set a LookBack in the FirstClass Client or Web under: Select Desktop > Preferences >
[791]
Comments: 0,
Last Modified: Apr 11, 2008 3:20 PM
- Find Similar
An option on contacts created on the server must be enabled in order to synchronize through NotifyLink Enter Server. Contacts created on the FirstClass server include an option to "Synchronize Entity with handheld device." If the option is disabled, the contact will not synchronize to the device via NotifyLink Enterprise Server.
[797]
Comments: 0,
Last Modified: Apr 11, 2008 5:45 PM
- Find Similar
User created Contact Databases (address books) cannot be selected for synchronization From the FirstClass server, users may create multiple address books (Contact Databases), however, these address books are not available for selection in the NotifyLink Contact Sync Settings and thus contacts from these address books cannot be synchronized to the device. In the NotifyLink Administrative
[1166]
Comments: 0,
Last Modified: Jun 25, 2009 4:58 PM
- Find Similar
Several 'slow sync' issues experienced with NotifyLink may be rectified by adjusting a configuration file setting on the FirstClass server. Several 'slow sync' issues experienced with NotifyLink may be rectified by adjusting a configuration file setting on the FirstClass server. Behavior: -PIM Slow Sync resulting in mass delete/add of PIM items -Errors in the FirstClass log, such as: PENDING
[799]
Comments: 0,
Last Modified: Apr 15, 2008 8:54 AM
- Find Similar
Not all patterns of recurring events created on the device are supported in FirstClass and therefore do not synchronize to the server. Recurring events, created on the device with a pattern not supported in FirstClass will only synchronize properly to the server. Only the first instance appears on the server. Examples of recurring event patterns that are not supported are events
[801]
Comments: 0,
Last Modified: Apr 15, 2008 8:54 AM
- Find Similar
Recurring events for every weekday or weekend day do not synchronize properly to the FirstClass server if created on a Windows Mobile device. This issue involves recurring events that are created on a Windows Mobile device and synchronized to the FirstClass server.Recurring events that are set to occur every weekday (M,T,W,TH,F) synchronize to the server with instances of the event for 5 weeks
[802]
Comments: 0,
Last Modified: Apr 15, 2008 8:55 AM
- Find Similar
An event created on the device before the "Synchronize only after date" does not appear on the server. An event created on the device before the "Synchronize only after date" does not appear on the server. This "Synchronize only after date" parameter is one set in FirstClass and it overrides any LookBack/LookAhead range set in the NotifyLink policies. See also KB
[811]
Comments: 0,
Last Modified: Apr 15, 2008 1:40 PM
- Find Similar
If you change the "Synchronize only after date" in the FirstClass Client, deletions and additions are not made for items that fall into or out of range. If you change the "Synchronize only after date" in the FirstClass Client, no deletes or adds are sent to the device for events or tasks that fall out of or enter the new range.
[818]
Comments: 0,
Last Modified: Apr 17, 2008 9:14 AM
- Find Similar
Contacts where the name or company fields are not filled in do not synchronize. Contacts created on either the device or the FirstClass server that do not have the name or company field filled in do not synchronize.
[803]
Comments: 0,
Last Modified: Apr 15, 2008 2:28 PM
- Find Similar
If the event was originally created on the server with a category, changing it on the device wipes out the category. An event originally created on the FirstClass server with a category will lose the category if the event is modified on the device.
A Leading Provider of Enterprise Mobility Solutions
Contact Support