RSS Feed
Knowledgebase : NotifyLink Enterprise Server > Kerio
Kerio: This issue applies to meeting requests/invitations initiated from the device. Changes such as adding or removing attendees on an existing meeting invitation are not synchronized properly.   When an attendee is removed an email is sent saying th...
Kerio: This issue applies to non-recurring events that start within the user's synchronization range (Look Back, Look Ahead), but end outside of the range. An event that meets these criteria will not synchronize to the device until the end time is wit...
Problem: Kerio users see "Caught Unknown Error" in the PIM log when trying to process contacts. Solution: One possible solution that has worked for customers is to Export and then Import their contacts.  Kerio doesn't have an import/export ...
Kerio:This issue involves invalid start dates on a recurring event.  An invalid start date is defined as a start date that is not an instance of the series. The following are examples of invalid start dates:    For a yearly recurring event:  1st Monday ev...
Kerio: Problem: User has performed an OTA load of contacts on their device.  All contacts came down to the device successfully but some or all of them do not contain an email address. Explanation:  In NotifyLink Enterprise Server for Kerio version 4....
Kerio: The BaseDN field on the LDAP Servers page has a maximum size of 50 characters.  If you attempt to enter a BaseDN that is larger, the field will be truncated resulting in errors when you attempt to use the Remote Lookup feature on the device cli...
If you are receiving a User Authentication error and you know the credentials are correct, here is something you will want to have the Kerio admin check.  On Kerio Server got to Admin Console -> Kerio Firewall -> Traffic Policy.  Make sure our ...
All day events created in Kerio synchronize to the device, but are displayed one day earlier. NOTE: This issue no longer occurs after applying the nlpim.exe v4.1.0.8 hotfix. NOTE: This issue is resolved in the NotifyLink Enterprise Server release version...
This issue occurs only for users on a Kerio CalDAV pim protocol that have their time zone set to GMT+2. All Day Events created on the device will synchronize to the server and appear one day early in the calendar. ...
Kerio: When a contact is created on the device with a new category, the category is synchronized and created as an address book on the server.  The new address book is listed when viewed in the NotifyLink Administrative Web console, but is not selec...
Kerio:This issue applies to contacts that are not in the user's Default Address Book. The default address book is defined on the user's Contact Sync Settings > Choose Address Books page in the NotifyLink web. If a contact that is not part of the defaul...
Kerio: This issue applies to contacts that are not in the user's Default Address Book. The default address book is defined on the user's Contact Sync Settings > Choose Address Books page in the NotifyLink web. If a contact that is not part of the defa...
Kerio:This article identifies situations that can result in contacts being duplicated on the server. I. This situation involves existing contacts that reside in an Address Book (category) on the server that has not been selected for processing by NotifyL...
Daily or weekly recurring events created in the Kerio web client with a specific end date (as opposed to specifying number of occurrences) render one more instance on the device than on the server.  EX: A weekly recurring event starting on 7/7 with a s...
Kerio:When an address book is deleted on the Kerio server it still shows up on the Choose Address Book list.  If the address book was selected for processing, NotifyLink unselects the address book. What is displayed on the Choose Address Book page is a De...
Kerio:When a user account is removed from the Kerio server, the LDAP entry for that user is not removed.  If a new account with the same name is added to the server, two instances of the username appear in the LDAP available user list.  This can also caus...
ISSUE: When users interfacing with a Kerio mail server register to GO!Enterprise MDM, a 500 error is returned to the device and the registration does not complete. BACKGROUND: Kerio considers a command used for validating NotifyMDM traffic to be from an ...
Kerio: Issue:  Calendar events that fall outside the sync range (IT Policies-> Calendar Sync Settings) may not be deleted from the device for several cycles. Solution: This is an issue with the Kerio server not immediately sending a delete for the ...
Kerio:The Kerio server does not support exceptions to recurring events, therefore, NotifyLink Enterprise Server (NLES) for Kerio does not support/synchronize them. When making a change to a single instance of an event which is part of a series (an except...
Kerio:The following PIM properties can be synchronized from the Kerio server to device clients. Appointments: subject, start time, end time, text description, reminder offset, all day event flag, location, recurrency rules Tasks:  subject, due time, tex...
Kerio:In the following situations, an email that includes invitation information will be sent to the NotifyLink user's device. This email is in addition to the meeting invitation itself. The email cannot be used to respond to the invitation (Accept/Declin...
Kerio: This issue involves calendar events originating as the result of an accepted meeting invitation.  When the event is deleted on a device, the change is initially synchronized to the server as well.  However, the event shows up again on the serve...
This issue occurs for newly created NotifyLink (NL) user accounts when the user has meeting requests in the Kerio web client to which he/she has not yet responded.  Normally, historical web client email (those received prior to NL account creation) a...
Kerio:When a meeting invitation on which notes have been entered is sent to a Kerio account, Kerio adds a summary of the invitation to the note section along with the original notes. The event is later updated to remove the summary from the notes. NotifyL...
Kerio:A multi-day event, created on an Exchange or Kerio server, that starts within the calendar synchronization range and ends outside the range, does not synchronize to the device. Once the event comes into calendar synchronization range, however, it i...
nlpim.log error "Failed to create the new resource" may be a remnant of a resolved Kerio issue. Prior to the issue's resolution, a meeting invitation created on a device would not appear in the recipient's email. Although the issue is resolved, the erro...
Port Requirements for NotifyLink Installation can be found in the NotifyLink for Kerio Pre-Installation Guide  under Pre-Installation Tasks #8, Port Requirements Port numbers used for connections with NotifyLink Enterprise Server (NLES) components are we...
Kerio:Recurring events created on the sever with instances outside the set synchronization range (prior to the look-back date and after the look ahead date) are being synchronized to the device, thus ignoring the synchronization range parameters.
Kerio: This issue applies to meeting requests initiated from the device. When the NotifyLink user that created the invitation views it using Outlook, attendee responses are not displayed correctly and the Free/Busy status is not up to date on the 'S...
Kerio: This issue applies to tasks created on the server. The task will synchronize to the device with a reminder time set to one minute earlier than what was defined on the server. This issue is seen primarily when using the Outlook connector to cre...
Kerio: Creating/editing a task with a reminder time on a device results in the following:  On the server, the task's reminder date is correct, but the reminder time will be incorrectly set to midnight. NOTE: This issue is resolved in the NotifyLink En...
Kerio: Tasks created on the server with due dates one day past the set look-ahead date, synchronize to the device.  Calendar events do not exhibit this behavior - only events occurring within the synchronization range are synchronized to the device. ...
Information: In version 6.4.2 of the Kerio server, tentative and accepted responses are treated the same (they will both be seen as accepted). In version 6.5.0 this is no longer an issue.
Kerio:Replying to a meeting request from a device with the 'Tentative' response results in the meeting invitation being resent in a subsequent synchronization cycle.  The invitation will continue to resend each time the 'Tentative' response is used.
Kerio:In the NotifyLink Mail Servers settings, the Trash and Sent Items folders may be changed to a folder that does not exist in the users' Kerio accounts. If this is done, the folder will not be automatically created and so deletes and tracking messages...
Kerio:This issue applies to iPhone/iPod touch users operating on a Exchange or Kerio server.   A contact created on the device may contain fields not supported by the NotifyLink Enterprise Server. However, should the contact be moved on the server into a...