Notifylink Error Codes
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 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 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!NotifyLink connected to the mailbox successfully, the next thing to be checked is whether new email is found. The User Statistics will show this under Number of Emails Found. To test this, send the account a test email and do not read the email (leave the email marked as unread). Allow GO!NotifyLink to process the mailbox again and then check the statistics for Number of Emails Found. This value should show a 1 or higher, depending on how many emails were new. Also confirm that Number of Emails Sent also matches the n
Locating and reading log files Section 2 Determining a user's ClientDeviceSAKey Section 3 Ensuring that all services are running Section 4 Ensuring that mailboxes are being accessed Section 5 Confirm that SQL cleanup jobs are running Section 6 Tearweb error when using a proxy server Part 2 Server Configuration Section 1 Port configurations Section 2 Server configuration diagram Part 3 Troubleshooting the server Section 1 Messages to the Device 1. Device is not receiving registration messages 2. Device is not receiving http://help.notify.net/TechDocs/enterprise/Troubleshooting/NetHelp/WordDocuments/deviceisnotreceivingnotifications.htm notifications 3. Leasing may be failing or we can't hit the leasing page 4. Device to Server authentication Section 2 Messages from the Device 1. Commands or replies from the device are not being processed Section 3 PIM Service 1. NLPim.log not being updated or user's address book list is empty in the web UI Section 4 http://help.notify.net/userguide/enterprise/esimap/ESCGPTrouble.asp Telnet Commands 1. SMTP commands to send mail. 2. IMAP commands to test DELETE of message 3. Other IMAP commands Part 4 Troubleshooting the eFile server Section 1 General Setup 1. Dynoplex Administration button is missing 2. Can’t get to NotifyLink Enterprise Server web admin (http://
to Settings and click notifylink error iv. Scroll to Network and click v. Select the correct service provider and click to OK the selection. b. Check the eFile notifylink error codes Server Registration Code i. If the registration code is wrong, there will be an error in the eFileMDS log ii. Log in to http://