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.
[597]
Comments: 0,
Last Modified: Sep 5, 2007 11:46 AM
- Find Similar
Dismiss Scalix UALWSD popup message. Users have reported seeing the following Scalix UALWSD popup: "Scalix UALWSD encountered a problem and needed to close." In most instances, after dismissing the error, it did not reoccur. Dismiss the popup if you see it. Contact Scalix technical support if the problem becomes debilitating.
[173]
Comments: 0,
Last Modified: Apr 22, 2008 4:05 PM
- Find Similar
Port Requirements for NotifyLink Enterprise Server - Scalix Installation Port Requirements for NotifyLink Installation can be found in the NotifyLink for Scalix 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
[576]
Comments: 0,
Last Modified: Aug 30, 2007 1:22 PM
- Find Similar
Scalix Administrator login for IMAP is only supported when using Scalix Server v10 or higher. Scalix Administrator login for IMAP is only supported when using Scalix Server v10 or higher.
[573]
Comments: 0,
Last Modified: Mar 13, 2009 9:28 AM
- Find Similar
Scalix PreCheck status cannot be edited on a user account When adding a user to the NotifyLink Enterprise Server you can specify whether Scalix PreCheck should be enabled or disabled. The option, however, cannot be edited after the user is added. To change it, it must be edited in the database or the user must be deleted and added again with the correct status. This issue is resolved
[583]
Comments: 0,
Last Modified: Mar 13, 2009 9:29 AM
- Find Similar
If the "Scalix PreCheck" box is checked while adding a user, a screen refresh will remove the check. This issue occurs when adding a Scalix user to the NotifyLink Enterprise server. If the "Scalix PreCheck" box is checked, a subsequent screen refresh will uncheck the option. This issue is resolved in NotifyLink Enterprise Server version 4.6.0.
[556]
Comments: 0,
Last Modified: Oct 3, 2007 11:10 AM
- Find Similar
PIM servers (calendar, contact, and task servers) must be all Scalix or all GroupWise when using these two ... limitation in this scenario. GroupWise and Scalix PIM platforms cannot co-exist on the same ... Component server. Scalix systems require that Outlook and Scalix Connect for Wireless ... ; Below are examples of GroupWise/Scalix configurations that will work and some that won't. MAIL
[557]
Comments: 0,
Last Modified: Sep 5, 2007 11:41 AM
- Find Similar
If Scalix is used for PIM processing, the Multi-PIM (MaxThreads) feature must be set to 1. The MaxThreads registry key used for Multi-PIM processing must be set to 1 on systems that employ Scalix for any PIM processing. Using a registry editor, look for: HKEY_LOCAL_MACHINE\SOFTWARE\Notify Technology Corporation\NLES PIMService\MaxThreads Set the MaxThreads registry key to 1.
[898]
Comments: 0,
Last Modified: Jul 23, 2009 2:09 PM
- Find Similar
Meeting invitations for Scalix users appear twice in an ActiveSync device calendar - once as a calendar event, once as an invitation. Users operating on a Scalix or Scalix CalDAV PIM server will see duplicate meeting invitations on their ActiveSync device calendar - one for the Calendar Event and one for the invitation. iPhone users will see this as soon as the item is received. Windows Mobile
[571]
Comments: 0,
Last Modified: Mar 13, 2009 9:14 AM
- Find Similar
Task reminders are not synchronized when created on the server or device. Though you can create a task reminder through Scalix Outlook connector, reminders created on the server are ignored and not sent to the device. Likewise, task reminders created on the device are ignored by server. This issue is resolved in NotifyLink Enterprise Server version 4.6.0.
[86]
Comments: 0,
Last Modified: Aug 1, 2006 10:30 AM
- Find Similar
If you have set up a SCALIX ADMIN protcol for Notifylink and Notifylink is not logging into a user's account successfully, you will usually see Error code 4 being displayed inside User Statistics. You can test the login through Telnet and here is the syntax to do so: TELNET [IP or DNS of the mailserver] 143 (Press Enter) a login "mboxadmin:[adminUsername]:[userUsername]" "[adminPassword]" (Press Enter
[841]
Comments: 0,
Last Modified: Jun 4, 2008 12:31 PM
- Find Similar
Only calendar PIM items will be synchronized to the device. Users operating on Scalix CalDAV protocol can only synchronize calendar PIM items. The Scalix CalDAV protocol does not support synchronization of tasks or contacts at this time.A work-around for pulling down contacts from the server to the device is to use remote lookup. Additions of or changes to contacts or tasks 
[582]
Comments: 0,
Last Modified: Aug 30, 2007 1:25 PM
- Find Similar
If using Scalix 11, the notes field for exceptions to recurring events created on the server will be replaced with question marks. If using Scalix 11, the notes field for exceptions to recurring events created on the server will be replaced with question marks.
[577]
Comments: 0,
Last Modified: Aug 30, 2007 1:22 PM
- Find Similar
Scalix does not support SSL or TLS for IMAP. Scalix does not support SSL or TLS for IMAP. These options should not be selected in the NotifyLink web administration mail server / mail protocol settings.
[852]
Comments: 0,
Last Modified: Jun 18, 2008 3:57 PM
- Find Similar
Yearly, and sometimes daily, recurring events created in Outlook do not show up in the Scalix web client and thus do not sync to the device. Daily recurring events created in Outlook sometimes do not show up in Scalix Web Access. If this is the case, the event does not synchronize to the device either. Yearly recurring events created in Outlook never show up in Scalix Web 
[850]
Comments: 0,
Last Modified: Jun 18, 2008 3:57 PM
- Find Similar
Events added or changed on the Scalix CalDAV server get added, deleted, then added again to the device. Events added or changed on the Scalix CalDAV server send an add/delete to the device and then sends another add in a subsequent synchronization cycle. The subsequent addition shows a different UID number than the original in the PIM log.