RSS Feed
Knowledgebase : NotifyLink Enterprise Server > Meeting Maker
An all day event created on the device will appear as two days on Meeting Maker. NOTE: This issue is fixed in NotifyLink Enterprise Server version 4.5.0
In Meeting Maker version 8.6 there was a new feature added that required every user created to have a foreign email address that is set up by the email administrator. Since Meeting Maker does not have email, this feature was added for email contacts. Fo...
In the Meeting Maker client, reminders are set as specific times/dates.  On devices, reminders are created in the form of minutes prior to the event.  However, reminders created on the device that are longer than 24 hours and not evenly divisible by ho...
Passwords in Meeting Maker can contain upper ASCII characters. NotifyLink does not handle these correctly.
Meeting Maker allows for creating a monthly or yearly recurring event with the option to move any weekend occurrences to Monday, to Friday, or to Closest (default setting is don't move). None of the moved occurrences are reflected on the device.
Meeting Maker: This issue applies to users that have a wired device. If Synchronize Message Changes is not being used, a message may be deleted from the server, but still exist on the device.  If a user, from his/her device, attempts to respond to the...
Meeting Maker: The following issues exist with contact synchronization of the phone number field: Phone number fields created in Meeting Maker with leading or trailing space, the spaces will be removed when the contact is sent to the device.If a contac...
Meeting Maker: This issue involves contacts created on the device with the title and job title filled in. When the contact is synchronized to the server the title does not display and job title appears in the title field.
Meeting Maker: Creating a weekly recurring event from a device with a start date that does not correspond to its first instance results in the last instance occurring one week before it should on the server. The last instance is correct, however, on th...
The grave accent ("`") is ignored within pim fields, it will not be sent to the device. This no longer occurs after applying Meeting Maker Sync Servlet v8.6.1. This issue is resolved in NotifyLink Enterprise Server version 4.6.0. ...
Meeting Maker: This issue occurs only for users that have their time zone set to a GMT+ zone. All Day Events (Banners) created on the device will synchronize to the server and appear one day early in the calendar.  
This issue involves contacts created on a device and associated with a category or a contact category that is changed on a device. When the contact is synchronized to the server the category is set to ‘None', even if the specified category exists in Me...
If you create a contact on a Meeting Maker server and change the category from a Windows Mobile ActiveSync device, the change will not synchronize to the server correctly.  The contact will be listed with a ctegory of "None" in the Meeting Maker...
Once a task is marked as completed on a Meeting Maker server, changes to task status or to other task information made on a Windows Mobile ActiveSync device do not synchronize to the server.    This issue was reported using a WM ActiveSync device, but lik...
Meeting Maker: The device's Contacts (Address Book) application may have fields for Home Address and Web Page; these fields are not supported in the Meeting Maker Client. If a contact is created on the device with these fields, the contact is synchron...
  Contact Fields Synchronized MeetingMaker Palm BlackBerry Windows Mobile First First name First First Last Last name Last Last Title Title Job Title Job title Dept Department Company Company Company Company Address Work Address Work Address Work Street...
Meeting Maker: This issue involves calendar events created or modified on the device. After NotifyLink processes the add/change, an update will be sent back to the device for the same event. If the device user has PIM Change Summary enabled on the dev...
This issue involves contacts created in Meeting Maker that have a Custom 3 and/or Custom 4 value set. If the contact is edited on the device, the Custom 3 field will be cleared and the Custom 4 field will be set to the previous value of Custom 3. This...
Meeting Maker: This issue involves users in which one lives in a time zone that operates on Daylight Saving Time (DST) and the other does not. A recurring meeting scheduled prior to, but having occurrences after a time change will not shift the hour...
Meeting Maker:In Meeting Maker version 8.6 there was a new feature added that required every user created to have a foreign email address that is set up by the email administrator. Since Meeting Maker does not have email, this feature was added for email ...
The Euro character is not synchronized correctly within pim fields. If the Euro is used when adding or editing from the device, the character is sent to Meeting Maker but not displayed correctly. If the Euro is used when adding or editing in Meeting Ma...
Meeting Maker: Events created on the device with duration greater than 23 hours, 59 minutes are not supported.
Features Not Supported For Meeting Maker:  1.)     Notice of a meeting cancellation is not synchronized to a user's device. 2.)     The Label/category of a banner/activity/meeting is not synchronized to a user's device. 3.)     Flexible banners/a...
On iPhone OS based devices, when viewing the meeting invitation in the calendar or the mail application, the sender may display as "unknown." This typically happens when using GroupWise or Meeting Maker as the mail/pim server. In addition, if a dev...
Guests of meeting do not have permission to modify the meeting. This cannot be prevented on device, so if a user edits the meeting on the device, the change will not be stored in Meeting Maker. However, the user will not be notified that the update fai...
PROBLEM: One or more users are not able to sync PIM on their device to and or from Meeting Maker. The NL PIM log shows the following error: GetEventVCard: GetPimRequest failed, Http status = 539 Or GetEventVCard: GetPimRequest failed, Http s...
Meeting Maker: A weekly recurring meeting that is scheduled for a time early in the day (5:00 a.m. or earlier EST - Eastern Standard Time) or in the GMT shadow results in the date of the meeting being incorrect. The date will be one day earlier for th...
Meeting Maker:This issue involves invitations/proposals for recurring meetings. When a user receives an invitation on the device, only the first instance of the recurring meeting is noted making the invitation look as if it were for a single meeting.
Due to the following issues, it is recommended that all exceptions be created in the Meeting Maker client rather than on the device. For BlackBerry Phone or Windows Mobile 5 device users there exists a possibility of an issue involving a recurring app...
Meeting Maker: Some folders that display in the Folders list via the web may not be actual mail folders and should not be selected for processing. The names of these folders will be different depending on the mail system that is being used.
Meeting Maker:It is important to understand that the Meeting Maker servlet stores PIM dates/times in GMT.  In certain situations this can alter dates/times associated with calendar events or tasks and in turn the way those events or tasks are processed. ...
It is important to understand that the Meeting Maker servlet stores PIM dates/times in GMT.  In certain situations this can alter dates/times associated with calendar events or tasks and in turn the way those events or tasks are processed. One such sc...
Username and passwords in Meeting Maker can contain special characters that are not handled correctly by NotifyLink. For example, the ampersand ("&") and double quotation characters.
If Meeting Maker is set up to use LDAP Authentication, the user's LDAP password should be used when adding the user to NotifyLink Enterprise Server (NLES). If the LDAP password for a user changes, the password must be updated on the Edit User page of t...
The Meeting Maker Client supports creating monthly recurring events with the option "x days from month's end". NotifyLink does not support this type of recurrence pattern. If an event is created with the value set to one day before month's en...
Meeting Maker:If using a Palm device, multi-day banners created in Meeting Maker will only appear on the first day on the device. This is because Palm devices do not support multi-day untimed events.
If proposals are received in Meeting Maker, a calendar event will not be added to the device until the proposal is accepted.
This issue involves tasks created in Meeting Maker that have a Percent Done value set. If the task is edited on the device, the Percent Done will be set to 100 (for completed tasks) or 0 (for incomplete tasks).
Meeting Maker: Server and device application PIM fields do not always match.  This issue involves PIM items, created on a device, containing data in fields not supported by the server.  Such an item will synchronize to the server.  However, if a chan...
Problem:  A calendar event created on the device is not being synced to Meeting Maker and the following error appears in the NotifyLink PIM log for the user. [Jun 29, 2009 10:55:49][0]ProcessVCalendar - start [Jun 29, 2009 10:55:49][0]Parsing Calendar...
Meeting Maker: Issue: Pim login failure showing in the Admin Console under User Statistics. Description: Open the Pim log (nlpim.log) and look for the following errors: 2/28/2007 10:31:27 AM[0][LogonMBox: Login failed, Http status=2009261398] 2/28/2...
Meeting Maker: Issue: Pim login failure showing in the Admin Console under User Statistics. Description: Open the Pim log (nlpim.log) and look for the following error: 2/28/2007 10:15:24 AM[0][LogonMbox: processing user: johndoe, deviceSAKey = 135253...
Port Requirements for NotifyLink Installation can be found in the NotifyLink for Meeting Maker Pre-Installation Guide  under Pre-Installation Tasks #8, Port Requirements Port numbers used for connections with NotifyLink Enterprise Server (NLES) component...
Port Requirements for NotifyLink Installation can be found in the NotifyLink for Meeting Maker Pre-Installation Guide  under Pre-Installation Tasks #8, Port Requirements Port numbers used for connections with NotifyLink Enterprise Server (NLES) compone...
The following recurrence patterns are not supported in Meeting Maker.  If one of these patterns is created on the device an error message will appear in the NLPim.log file, however, the message is NOT passed to the device.  Check this log file if an event...
Meeting Maker: Information: If you have a recurring event that has instances prior to the look back date and after the look ahead date (specified in IT Policies -> Calendar Sync Settings) the event will still be sent to the device even though there ar...
A recurring event created on the device with a start date that is not an instance of the series may results in the series being incorrect on the Meeting Maker server. The series will occur on the wrong day. This applies to monthly by position, monthly...
Meeting Maker: This issue involves changing the synchronization range for calendar events or tasks. When a change is made reducing the length of the synchronization range (Look Ahead is reduced), events or tasks falling outside the original range are...
Meeting Maker: Tab character in the notes field of a calendar item is not synchronized correctly. There is different behavior depending on the direction of synchronization:      Server to device  - The first tab between characters is not shown but any...
Task priorities from Meeting Maker will be synchronized to the device as follows: Urgent, Important, High = HighMedium, Normal, None = NormalLow = LowTask priorities from the device will be synchronized to Meeting Maker as follows:High = HighNormal = Norm...
Issue: If you create a reminder for a task using the 'on date' option in Meeting Maker and set the local time so that it equates to midnight GMT (i.e. 7pm EST), the reminder will come down to the device as midnight instead of the specified time. Soluti...
Meeting Maker: This issue involves creating a task from a device with a reminder date prior to the task's due date. When the new task is synchronized to the server the new task is created, but without the reminder. If the task is created from the serv...
Meeting Maker: This issue involves tasks created on the server and subsequently marked as completed on the device. Further changes made on the server to the completed task result in the task being deleted from the device. (Example: Removing the "...
Meeting Maker: If using a Windows Mobile device with encryption on, some upper ASCII characters in Calendar, Contact, or Task fields will cause an error in NLPIM.log, and the item will not be added/updated.