Notifylink Error Code 1
Web Server (19)NotifyLink Database Component (1)NotifyLink Multi-Tenant Edition (5)NotifyLink On Demand (4)Sales (2)NotifyLink Patch Installer (48)NotifyMDM Server (108)NotifyMDM Device SEARCH Knowledgebase: NotifyLink Enterprise Server Error Code 1 Posted by on 25 January 2013 02:27 PM The Error Code 1 is an IMAP No Examine error. When the NotifyLink Enterprise Server attempts to access the folders on the email server over IMAP - the examine command fails. An Error Code 1 can be produced if... The user is set to synchronize a folder, selected in the user's policy (Edit User Policy > Folders), that was renamed, moved or deleted on the email server. Resolve thisby navigating to the Folder Selection (Edit User Policy > Folders) and de-selecting that particular folder. The Check Mail Server for Folder Updates option can be used to update Folder Selection list on the next successfully completed Mailbox check, which will remove the folders that were moved or deleted on the email server. TheInbox (listed as Mailbox within the GroupWise Client) folder has been moved from the root of the mail client's folder structure (ex. nested below another mail folder). Resolve thisby moving the Inbox (or Mailbox within the GroupWise Client) folder back into the root of the mail client's folder structure. You may need to contact your Email administrator or IT department for further assitance. The mail folders selected to synchronize are exceeding IMAP limitations imposed by the mail server and/or the folders contain a large amount of emails. Resolve thisby either moving emails into a different folder or deleting emails to reduce the number contained in the folder. Please consult your Email administrator or IT department to make sure that mail folder(s) are not exceeding any IMAP limitations imposed by the mail server. Please refer to the GleanerController log for exact details of which mail folder(s) is inaccessible. The user's ClientDeviceSAKey will be needed to identify the user within the log. If the issue persits, please contact technical support for further assistance and troubleshooting. Help Desk Software by Kayako
and whether GO!NotifyLink is finding new email. To do this, open the GO!NotifyLink admin web console and browse to User Statistics for the user in question. The Result will display whether or not GO!NotifyLink was successful in accessing the mailbox. The value that should be displayed is "Mailbox checked successfully". If the statistics page is empty and there is not yet a value for the Result, then most likely the user has just been added to the http://support.notifycorp.com/support/index.php?/Knowledgebase/Article/View/1360/1/error-code-1 server. Wait a couple minutes and refresh the statistics, as GO!NotifyLink has probably not gotten around to checking this user yet. If the mailbox statistics are still not updated, see the above section entitled Ensuring mailboxes are being accessed. Additionally, you can check the GleanerController.log file. Once you have determined the user's ClientDeviceSAKey, search for the most http://help.notify.net/TechDocs/enterprise/Troubleshooting/NetHelp/WordDocuments/deviceisnotreceivingnotifications.htm recent log entry for this user. It should look something like the following: [Thu Sep 30 09:19:43 2014] Retrieving devices at 09:19:43 UTC[Thu Sep 30 09:19:43 2014] Gleaning 7 devices ClientDeviceSAKey 60064 ClientDeviceSAKey 60952 ClientDeviceSAKey 61020 ClientDeviceSAKey 61108 ClientDeviceSAKey 62754 ClientDeviceSAKey 62764 ClientDeviceSAKey 62856[Thu Sep 30 09:19:44 2014] Confirm that the user is in the list of user's being checked for mail and that the logs are up to date. Most other error codes in the Result value of the User Statistics should point to an error with user configuration or an error with the mail server. For example, "User authorization error" generally means that a user's username or password is incorrect. "Cannot connect to server" means that the mail server could not be contacted. Check that the user is set up on the correct mail server and check that the mail server is functioning correctly and has support for IMAP. For a list of all error codes see the end of this document. Assuming that GO!Notif
AuthFail User authorization failure 5 MaxGleanTime Gleaner Timeout http://help.notify.net/TechDocs/enterprise/Troubleshooting/NetHelp/WordDocuments/servererrormessagecodes.htm 13 IMAP_ERROR_361 IMAP SELECT NO 361 PIMAuthFail PIM Authorization Failure 551 MAILPP_ERROR_10021 Internal Error (10000) 10021 MAILPP_ERROR_10022 System Error (10000) 10022 MAILPP_ERROR_10023 Usage Error http://sonykado.projects-library.com/notifylink-error-code-1-360.php (10000) 10023 MAILPP_ERROR_10024 Canceled (10000) 10024 MAILPP_ERROR_10025 Host unreachable (10000) 10025 MAILPP_ERROR_10026 Connection refused (10000) 10026 MAILPP_ERROR_10027 Timed out (10000) 10027 MAILPP_ERROR_10028 Connection notifylink error dropped (10000) 10028 MAILPP_ERROR_10029 Protocol error (10000) 10029 MAILPP_ERROR_10030 TLS handshake error (10000) 10030 MAILPP_ERROR_10031 TLS data error (10000) 10031 MAILPP_ERROR_10032 Invalid certificate (10000) 10032 MAILPP_ERROR_10033 Bad certificate name (10000) 10033 MAILPP_ERROR_10071 Internal Error (10050) 10071 MAILPP_ERROR_10072 System Error (10050) 10072 MAILPP_ERROR_10073 Usage Error (10050) 10073 MAILPP_ERROR_10074 Canceled notifylink error code (10050) 10074 MAILPP_ERROR_10075 Host unreachable (10050) 10075 MAILPP_ERROR_10076 Connection refused (10050) 10076 MAILPP_ERROR_10077 Timed out (10050) 10077 MAILPP_ERROR_10078 Connection dropped (10050) 10078 MAILPP_ERROR_10079 Protocol error (10050) 10079 MAILPP_ERROR_10080 TLS handshake error (10050) 10080 MAILPP_ERROR_10081 TLS data error (10050) 10081 MAILPP_ERROR_10082 Invalid certificate (10050) 10082 MAILPP_ERROR_10083 Bad certificate name (10050) 10083 MAILPP_ERROR_10121 Internal Error (10100) 10121 MAILPP_ERROR_10122 System Error (10100) 10122 MAILPP_ERROR_10123 Usage Error (10100) 10123 MAILPP_ERROR_10124 Canceled (10100) 10124 MAILPP_ERROR_10125 Host unreachable (10100) 10125 MAILPP_ERROR_10126 Connection refused (10100) 10126 MAILPP_ERROR_10127 Timed out (10100) 10127 MAILPP_ERROR_10128 Connection dropped (10100) 10128 MAILPP_ERROR_10129 Protocol error (10100) 10129 MAILPP_ERROR_10130 TLS handshake error (10100) 10130 MAILPP_ERROR_10131 TLS data error (10100) 10131 MAILPP_ERROR_10132 Invalid certificate (10100) 10132 MAILPP_ERROR_10133 Bad certificate name (10100) 10133 MAILPP_ERROR_10171 Internal Error (10150) 10171 MAILPP_ERROR_10172 System Error (10150) 10172 MAILPP_ERROR_10173 Usage Error (10150) 10173 MAILPP_ERROR_10174 Canceled (10150) 10174 MAILPP_ERROR_10175 Host unreachable (10150) 10175 M