Please consider voting for the following enhancement request on the Sage 100 Ideas web site:

• https://www5.v1ideas.com/TheSageGroupplc/Sage100ERP/Idea/Detail/27341

Failures during Electronic Delivery may result in an error log. However, such Chilkatlog error logs are long. They may overflow the error window, which itself covers more than the entire display screen, leaving only a middle portion of the log available for viewing - it cannot be copied and pasted for research. And usually, crucial error information that would indicate what the problem may be, is unavailable and hidden (disappears off screen).

Or, users are not aware that the error log is far longer than what is displayed. They need to copy the entire log, as oftentimes the actual issue will be revealed near the end of the log, not at the beginning.

Sage Engineering is reviewing this issue.

Possible Workaround:

1. If the text of the error log can be scrolled down to reveal more, then copy the entire error log (via click+drag, and continue dragging until it is all highlighted, then use the keyboard keys Ctrl+C to copy the text) so it can be pasted into NotePad or Microsoft Word or an e-mail for review.
2. If the text of the error log cannot be scrolled down to reveal more, then try sending a Test E-mail from Library Master, Main menu, Company Maintenance, on the E-mail tab. If an error is generated there, the text of the error can be scrolled and even copied as above.
   • Note: This possible workaround is not viable for some Electronic Delivery errors, as they tend to only occur during actual Electronic Delivery - not during tests conducted through the Test function in Library Master, Company Maintenance, E-mail tab. This makes troubleshooting the actual problem difficult.
3. Also, if an error is generated, search the Sage Knowledgebase for the key details of the error, such as "Error 550 5.7.1 Unable to relay", etc.

Note: There are numerous different server programs and providers that provide the services of an SMTP e-mail server. Sage does not test Sage 100 with all e-mail services/programs/providers. Sage 100 Customer Support is not responsible for knowing the exact combination of program or provider, security or permission settings, inbound or outbound rules, account logins, passwords, bandwidth restrictions, etc. to enable successful e-mail delivery. The specifics of services, programs, and providers are subject to change. If an error is encountered, troubleshoot based on the Chilkat error log information. You may need to try various settings, or test an alternate service, program, or provider.

Note: The vast majority of SMTP errors customers have reported to Sage 100 Customer Support are not caused by Sage 100.