Sage 100 Unable to Log into SMTP Connection

Sage 100 Error Unable to Log into SMTP Connection

This is a typical problem that is highlighted by the warning, that Sage 100 unable to log into SMTP connection or failed to get a response to log in password while attempting to send a test e-mail from company maintenance.

Now most often you will witness information on the screen, particularly on screen, despite its many valuable features, Sage occasionally stops responding or shuts off.

Causes Sage 100 Unable to log into SMTP Connection Error

The above error unable to log into an SMTP connection may occur due to the following possible reasons, to know more about them stick thoroughly.

  • The user ID entered on the Company Maintenance E-mail tab had already been validated, which can be one of the most prominent reasons for this error message.
  • Another reason can be the current exchange server also supports SMTP.

Tips to Resolve the Sage 100 Unable to log into SMTP Connection Error

A variety of server applications and vendors offer SMTP e-mail server services. Not all e-mail services/programs/providers have been tested in conjunction with Sage 100. We are not responsible for establishing the specific program or provider, security or authorization settings, inbound or outbound rules, account logins, passwords, bandwidth limits, and so on that are required for proper e-mail transmission. Service, program, and provider information are subject to change.

If a problem is unable to log into the SMTP connection, be careful to troubleshoot Sage 100 unable to log into SMTP connection. You may need to experiment with other settings or a different service, application, or provider.

Step I- Verify Login and Password

  • For the first, verify as well as double-check your login information.
  • Even though the password field looks to accept more characters, Sage 100 editions before the 2016 edition only Consultant 14 characters.
  • Next, In Sage 100 versions before the 2016 release, if the password is longer than 14 characters, it may be cut off, resulting in password authentication failing.

Step II- Check the SMTP Server

  • You can attempt to shorten the e-mail password in Sage 100’s Library Master, and Company Maintenance’s E-mail page by utilizing the SMTP provider’s e-mail settings.
  • Now, proceed further to Enable and examine the SMTP server log (you may need to contact the SMTP provider for this information) to observe how the handshake attempt looks if the username and password are right.
  • Thereafter, Based on the log data, troubleshoot.
  • Check to see if the SMTP server’s inbound rules are appropriately configured to allow for repeated login/connection attempts.
  • Some SMTP servers limit the number of connections that can be made in a given period.

Step III- 2 Factor Authentication

  • Sign into your Gmail or Google Apps account, then go to and enable Access for less secure apps.
  • If 2-step Verification is enabled for the Gmail account, the App Password can be used.
  • Related Resources contains instructions on how to configure Gmail with Paperless Office.

If you get the error 535 5.7.8 “Username and Password not recognized,” yet your username and password work when you log in to email through the web (with 2-factor authentication), you might need to activate “Access for less secure applications” (allow exceptions to 2-factor authentication) in your email settings.

Two-factor authentication cannot be configured for Paperless Office Electronic Delivery.

The following is a portion of a Chilkatlog error report, with important information underlined in bold text:

  • The SMTP connection is inaccessible.
  • ChilkatLog:\sVerifySmtpLogin:\sDll
  • On the 19th of January, 2012 Make SBestSoftMAILQ available as a prefix.
  • Little Endian; 32-bit architecture; user name
  • ActiveX is a kind of programming.
  • The login method is LOGIN 535. Incorrect authentication data.
  • LOGIN 535 5.7.3 LOGIN 535: Failed to get a response to login password OR login method: The authentication process failed.
  • There was no answer to the login password.


535 is a limited user (no detailed error message except 535, this can be due to a wrong email account password on Company Maintenance Email information). There was no answer to the login password.


535-5.7.8 SmtpCmdResp Both the username and password are incorrect. More details are available at SmtpCmdResp: 535 5.7.8


SMTP Authentication Error 535-5.7.8 “Username and Password not accepted” (535 5.7.8).

The above-presented information has effectively guided you through the entire concept of the Sage 100 error unable to log in to an SMTP connection. The reason why this error takes place as well as the causes are all listed in the above article in a detailed deeply involved information outlook.

All required actions are supplied, as well as the whole step-by-step approach guide. If you are still facing any issues or have any doubts concerning the above-listed information you can connect with the Sage chat customer helpdesk.

Frequently Asked Questions

Should I use an easy password to avoid this issue in the future?

While you can use an easier password to avoid this issue it is not recommended to do so. An easy password is well, easy to guess. So, any skilled hacker can guess your password, log in to your system, and steal all of your information. So, always use a complicated password and use a password tracker to ensure that you don’t forget it.

Is it possible to damage my system through the registry editor?

Yes, utilizing the registry editor can destroy your computer. It is software that should only be used by those who have substantial computer knowledge. If you make a single error, it might have a significant impact on how your device operates. Use the registry editor only if you are confident in your computer knowledge.

Failed to acquire a response to login password, “Is this a message which comes to your class?

Yes, such messages to hunt for such errors “Failed to acquire a response to login password,” “Unable to log in to SMTP connection,” and “Failed to obtain a response to login password.”