 |
|
 |
Knowledgebase Categories |
|
|
| Knowledgebase articles are categorized. Please select which category you would like to browse. You can also search the knowledgebase using the search field beside this text. |
|
| |
 | Articles |  |
|
 | Changing regional settings results in PIM processing halting for a period of time |  |
| NotifyLink Enterprise Server:Information: If you change the regional settings on the NLES messaging box, PIM will not process for a period of time until the current time exceeds the last processed times |
|
|
| Fowarded messages from device may appear with attachment in some clients | |
| NotifyLink Enterprise Server:Issue: When you forward a message from a device, the message received by the recipient(s) may contain an attachment with the email history instead of the history showing up |
|
|
| "Notify All" page is accessible even when there are no users to notify | |
| NotifyLink Enterprise Server:On the Administrative Web home page, the "Notify All" option is disabled (grayed out) if there are no users or all users are disabled on the server. However, a user may still access the fe |
|
|
| 10180 error using TLS | |
| NotifyLink Enterprise Server:Some IMAP servers specify that TLS is supported, but the implementation actually uses SSL. In this situation, the NotifyLink email login will fail with error 10180 (TLS handshake error). |
|
|
| Adding a new license to NLES v4.6.0 server |  |
| This article applies to NLES v4.6.0 servers that are running Update 5.Update 5 included a change for the behavior of license validation. When running this version, after a new license is added via the NLES Administrative Web Console, the fo |
|
|
| Administrator password change on the Notifylink server, Notifylink not working now | |
| NotifyLink Enterprise Server:When changing the Administrator password on the Notifylink server, the new password will have to also be changed for the Notifylin |
|
|
| Attachments not processing | |
| NotifyLink Enterprise Server:Problem: I have not been able to retrieve any attachments on my device. I have verified that my settings are correct in the admin console and then went to check the atta |
|
|
| Attendee list is not sent to device with meeting invitation | |
| NotifyLink Enterprise Server:Synchronization of meeting attendees to the device is not supported. When the user is invited to a meeting, the attendees (recipients) are not sent in either the meeting invitation or the associated |
|
|
| BlackBerry Attachment Conversions (NLES v4.0) | |
| NotifyLink Enterprise Server:On some NLES systems, the Attachment Service processing for BlackBerry attachment |
|
|
| Calendar event changes do not sync when processed with a PIM load | |
| NotifyLink Enterprise Server:This issue involves changes made to an event on the device. Should the event cha |
|
|
| Clean up the Logs directory files when a user is removed | |
| NotifyLink Enterprise Server:When a user is removed from the NotifyLink Enterprise Server, their log files are not removed. Administrators should go to the logs directory under NotifyLink Enterprise Server and manually clean up |
|
|
| Collaboration Suite Versions Supported by NotifyLink Production Releases | |
| Use this chart to determine what versions of your collaboration suite are supported by the latest production releases of the NotifyLink Enterprise Server (NLES). Document last updated: August 5 |
|
|
| ComboBox1 Error during NotifyLink Enterprise Server Installation | |
| NotifyLink Enterprise Server:Issue: During the installation of the NotifyLink Enterprise Server software you may encounter an error pop-up stating:"Internal Error 2878. Start_Installation_Dialog, ComboBox |
|
|
| Configuring LDAP for Remote Lookup | |
| NotifyLink Enterprise Server:LDAP Servers are used for the Remote Lookup feature, which allows users to search the System Address Book from their device. Once LDAP Servers are defined, an LDAP server can be specified for each u |
|
|
| Consecutive Notify Off commands can cause email to be unsent | |
| NotifyLink Enterprise Server:Issue: If you issue consecutive 'Notify Off' commands before issuing a 'Catchup' you will not receive any emails that where sent prior to the most recent 'Notify Off'. A tim |
|
|
| Contact Groups are not synchronized to the device | |
| NotifyLink Enterprise Server:Contact Groups (personal distribution lists) created on the server are not synchr |
|
|
| Delete Invitations From Device behavior | |
| NotifyLink Enterprise Server:Information: There are variations of the behavior of the 'Delete Invitations From Device' setting (User Policy -> Calendar Sync Setting). The following is a list |
|
|
| Device Management web page missing some information for iPhone devices | |
| NotifyLink Enterprise Server:iPhone/iPod touch devices do not synchronize all device management information to |
|
|
| Device Manual Registration does not work | |
| NotifyLink Enterprise Server:If you are trying to |
|
|
| Duress notification may not be sent if password is one repeated character | |
| NotifyLink Enterprise Server:A password entered in the Password Settings (Rules) such as, "aaaaaaaa" would render the same duress password. This may prevent the duress notification from being sent, a |
|
|
| Email deleted on device is not deleted on Cyrus server | |
| NotifyLink Enterprise Server:Issue: If you delete a message on the device, the message will not be removed from the Cyrus mail server. This is because there is no 'Trash' folder in Cyrus. |
|
|
| Email is not deleting from the device right away | |
| NotifyLink Enterprise Server:When accessing email from IMAP servers using certain email clients, such as some Outlook connectors, the mail is not deleted from the account at the time the user marks it for deletion. At that time |
|
|
| Email result displaying 382 error |  |
| Problem:Error code 382 displays in the Email Statistics field on the User Statistics page.Solution:Error code 382 indicates that there has been a change to the us |
|
|
| Emails that are encrypted or signed with SMIME or PGP will not be processed correctly | |
| NotifyLink Enterprise Server:Emails that are encrypted or signed with SMIME or PGP will not be processed correctly by NotifyLink; if there is an attachment on the message it will not be found. |
|
|
| Error 1722 when installing NLES Components | |
| NotifyLink Enterprise Server:Issue #1This error can occur if, when installing the NotifyLink Messaging Component, you have selected one or both of the monitoring routines (SQL Report or Disk Space Check) AND entered an inc |
|
|
| Error Code 303 in Gleaner Controller log | |
| NotifyLink Enterprise Server:If you look through |
|
|
| Fetch the Internal Date of an email message via the Command Line | |
| When Date and Time are selected in the Notification Format Rules of a user's IT policies (User Administration > select a user > Edit User Policy > Notification Format Rules), the inte |
|
|
| Filter Issues with NLES 4.6 | |
| NotifyLink Enterprise Server:There are some issues with the behavior of filters in NLES 4.6 that should be noted. They are listed below:Base64 Encoded BodyIssu |
|
|
| Fowarded messages from device may appear with attachment in some clients | |
| NotifyLink Enterprise Server:Issue: When you forward a message from a device, the message received by the recipient(s) may contain an attachment with the email history instead of the history showing up |
|
|
| Global IT Polices in the NotifyLink admin console for 4.5.2 and older | |
| NotifyLink Enterprise Server:When setting a Global Filter, in the Administrative Web Console under Global I |
|
|
| IIS Admin shows duplicate filters after upgrading from NLES 4.5.1 to 4.5.2 | |
| NotifyLink Enterprise Server:Two NLAirSyncRedirect filters appear in the IIS admin after upgrading from NLES 4.5.1 to NLES 4.5.2.Open the IIS admin, right click on Default Website, click Properties, |
|
|
| IMAP telnet test | |
| To test connectivity between your NotifyLink Server and your Mail Server, complete the following telnet test, pressing "enter" after each command: 1. Pull up a command prompt on the NotifyLink Server 2. Type "telnet xxx.xx |
|
|
| Implementing SSL on the NotifyLink server after users are set up | |
| NotifyLink Enterprise Server:Problem: I want to implement an SSL certificate on the NotifyLink server but I already have users set up and running with their devices connecting over HTTP. Solution: After imple |
|
|
| Incorrect warning message on Edit User Device page | |
| The Administrative Web console's Edit User Device page may display a warning message that does not accurately describe the status of the user device. For BlackBerry device users, the Edit User Device page may display a 'Register PDF Reader" |
|
|
| Increasing the number of ResponseHandler threads | |
| This information applies to NLES v4.6.0 servers that are running Update 5.Update 5 included a change that allows the maximum number of ResponseHandler threads to be configured in the registry. The default of 50 threads will perform well for |
|
|
| Install patch to prevent "SideBySide" errors after install or upgrade to NLES 4.6.0 | |
| Users are advised to install this Microsoft patch prior to or after an installation/upgrade to NotifyLink Enterprise Server (NLES) version 4.6.0. |
|
|
| Installing the SQL Report and Disk Space Check jobs after the NotifyLink server is already configured | |
| Problem:The NotifyLink server has already been installed without the SQL Report and Disk Space Check jobs that are optional to install during the Messaging Component setup. The server was installed without these jobs and now you would like for thes |
|
|
| Keeping Email and PIM Accounts Clean for Maximum Functionality | |
| NotifyLink Enterprise Server:The number of items in Email and PIM (Calendar, Tasks, Contacts) accounts should be kept under the required limitations to maintain functionality of NotifyLink. In addition to taxing a device's memo |
|
|
| LDAP Remote Lookup Mapping | |
|
NotifyLink Enterprise Server:See the link below for an Excel Spreadsheet of the default mappings of the a |
|
|
| License Validation Failure | |
| NotifyLink Enterprise Server:Issue: I see validation failures in the validate lease log fileSolution: En |
|
|
| Load balancing with NLES | |
| NotifyLink Enterprise Server:Network Load Balancing with NLES Install Windows 2003 Enterprise server. During install of the network components, select Network Load Balancing to install |
|
|
| Location of NotifyLink registry values | |
| On a NotifyLink Enterprise Server set up on a 32-bit Windows Server, the registry values can be found under:HKEY_LOCAL_MACHINE\SOFTWARE\Notify Technology CorporationOn a NotifyLink Enterprise Server set up on a 62-bit Windows Server, the |
|
|
| Log data can be restricted for security purposes | |
| NotifyLink Enterprise Server:NotifyLink Enterprise Server error logging is intended to be used as a diagnostic tool by Technical Support staff. Files may be set to log varying degrees of detail as needed or logging may |
|
|
| Logs for each service can be in either plaintext or HTML | |
|
NotifyLink Enterprise Server:Information: As of NLES 4.6 you can change the log name for each service. If you use .html as the extension for the filename, that service w |
|
|
| Messaging Component Port Requirements | |
| Messaging Component to Email/PIM Servers Port RequirementsReference the NotifyLink Enterprise Server Installation Guide for a listing of port requirements for the NotifyLink Messaging Component to Email and PIM server |
|
|
| Moving an exception to a recurring event prior to lookback does not remove it from device | |
| NotifyLink Enterprise Server:Issue: If you have created an exception to a recurring event and that exception is within the sync range (IT Policies -> Calendar Sync Settings) and you then mov |
|
|
| Multiple servers results in multiple logs for each service | |
| NotifyLink Enterprise Server:Information: If you have multiple servers running NLES services, you will have logs for each service on each machine, each containing only the cycles it was responsible for |
|
|
| NotifyLink Administrative/Client Web Console Lock Out | |
| Issue:After too many unsuccessful attempts to log into the NotifyLink Administrative Web Console or the Client Web Console, the login credential dialog box will gray out and prevent you from making further attempts. |
|
|
| NotifyLink Email Flow from Device to Server | |
| NotifyLink Enterprise Server:The Response Handler service is responsible for handling all device commands from the device. Older data devices will send commands via SMTP back into the gateway mailbo |
|
|
| Notifylink Email Flow from Server to Device | |
| NotifyLink Enterprise Server:Mail Server to Device: 1. Email (or PIM) is received in Mail User's account. 2. Gleaner takes the message and places |
|
|
| NotifyLink functionality may depend on Collaboration Suite software | |
| NotifyLink Enterprise Server:The level of functionality of the NotifyLink product may sometimes be limited by the features included (or not included) in the Collaboration Suite software you are using. Check the product release |
|
|
| NotifyLink Web Server Address Change | |
| NotifyLink Enterprise Server:If you change the IP or DNS address of your NotifyLink web component server, the following updates will need to be made.First, |
|
|
| OTA Load limited to 10MB maximum | |
| NotifyLink Enterprise Server:Information: NLES 4.6 has a 10 megabyte limit on an OTA load for any PIM type (calendar, contacts or tas |
|
|
| Recipient list is not received on device | |
| NotifyLink Enterprise Server:This issue applies when the 'List of Recipients' option is selected in Notification Format. If the total size of the recipient addresses is greater than 2000 characters, the list is truncated in the |
|
|
| Reminders for recurring events that start prior to the current day. | |
| NotifyLink Enterprise Server:Issue: NotifyLink handles recurring events by sending them to the device as a single event with a recurrence pattern. As such, if you create a recurring event on the server |
|
|
| Remote look up LDAP Configuration | |
| Remote Lookup allows a user, from a registered device to do a ‘global' lookup for Contacts from an existing LDAP server. In order to be able to perform this Lookup, you will need to have NotifyLink configured for access into the LDAP Server. In order |
|
|
| Remote Lookup for ActiveSync devices versus NotifyLink devices | |
| The LDAP Remote Lookup feature will return a different set of fields for contacts that are found depending on if the device is using the ActiveSync protocol or the NotifyLink device client. The ActiveSync protocol does not support all f |
|
|
| Reply or Forward text not viewable on an HTML message | |
| NotifyLink Enterprise Server:This issue applies to replies and forwards sent from the device when the original message is HTML. NotifyLink processes all messages on the device in plain text. When a message is replied to or forw |
|
|
| Seeing an Error Code 13 within User Statistics | |
| NotifyLink Enterprise Server:An Error Code of 13 within User Statistics means that there is a Gleaner Time out for this user. This means that this user may be taking too long to process for mail. Items to look into include: |
|
|
| Sending Attachments through AppleMail | |
| NotifyLink Enterprise Server:Problem:When a user sends an email with an attachment through Apple Mail it is not available to download on the device.Solution:This is an issue with IMAP formatting |
|
|
| Sent Items and Trash folders are automatically created if they do not exist for a user's account | |
| If names other than the default names are entered for the trash or sent items folder when setting up the Mail Server via the NotifyLink Administrative Web console (Server Administration > Mail Servers > Edit Mail Server), the folder(s) will be cr |
|
|
| SMTP Telnet Test | |
| NotifyLink Enterprise Server:If you are seeing an error stating "Relaying denied" in the ResponseHandler.log, the first thing to do is test the connectivity between the NotifyLink Server and your SMTP Server. To do thi |
|
|
| SQL Server connection test | |
| NotifyLink Enterprise Server:If you are having trouble connecting to the SQL server from the other NotifyLink server/servers try testing the ODBC (SQL) Connection between servers:1. Start -> Settings -> Control |
|
|
| Supported SSL Certificates | |
| NotifyLink Enterprise Server:Device to server SSL is has been fully tested and verified for the following certificates on the NotifyLink Enterprise Server:VeriSign/RSA Secure Server - More Information on acquiring a |
|
|
| Telnet Fetch command | |
| NotifyLink Enterprise Server:Question: How do I fetch the Header and Body of an email through a telnet session?Answer: The following needs to be done from the NotifyLink server. NOTE: |
|
|
| Telnet test is too large to view in the command prompt | |
|
NotifyLink Enterprise Server:Problem:Occasionally there are times when a telnet test is trying to be done and the results will exceed the size allowed by the buffer. When the buffer is not large enough to hold all of th |
|
|
| Time Zone Changes while traveling | |
| NotifyLink Enterprise Server:When you have a user |
|
|
| Using NLES on Windows Server 2003 R2 x64 | |
|
Follow these guidelines to setup and run the NotifyLink Enterprise Server on Windows Server 2003 R2 x64. Isapi FiltersNotifyLink version 4.5.x: PHP - php5isapi.dllNotifyLink version |
|
|
| Using NLES on Windows Server 2008 x64 | |
| Follow these guidelines to setup and run the NotifyLink Enterprise Server on Windows Server 2008 x64.ASP.NET 2.0, 32-bit versionFor NotifyLink to funtion correctly in a Windows 2008 x64 environment, IIS mus |
|
|
| Windows Server 2000 machines accessing SQL Server 2008 require SQL Tools for installing the NotifyLink SQL Database component | |
| Installation of the NotifyLink SQL Database component (version 4.6.0) fails when the machine you are running the installer on is Windows Server 2000 and accessing SQL Server 2008. The machine fails to connect to the Microsoft SQL Server.S |
|
|
| Windows Server 2008 Issues and Workarounds | |
| NotifyLink Enterprise Server:The following issues have been identified when installing or operating NotifyLink Enterprise Server v4.6.0 on a Windows Server 2008 machi |
|
|
| WinHTTP Trace Instructions | |
| 1. Locate the WinHTTP Trace file in the Downloads section of this site. 2. The winhttptracecfqui.exe is zipped. Extract this file to the root of C:\3. Open cmd line and go to root of C:\ by typing "cd c:\" (without the q |
|
|
| Wireless Device O/S Versions supported by NotifyLink and NotifySync | |
| Document last updated: August 17, 2010NotifySync Device Client:These are the wireless device O/S versions currently supported by the latest production releases of the No |
|
|
|
|
|
|
|
|
|
|
|
