Paperless Office Email Error - Upgrade From v4.40 to 2015

SOLVED

We recently upgraded from MAS 90 version 4.40 to Sage 100 Standard 2015 on Friday and we're now discovering that the emails being sent from the Paperless Office system are not working anymore (specifically these are direct deposit stubs coming from the Payroll and Accounts Payable modules).  All of the settings migrated to the new server successfully so nothing has changed, and we haven't changed anything on our Exchange email server, however we're now receiving the following error message (abbreviated to just include what I think is the pertinent part):

Using Microsoft SSPI NTLM.

response: 535 5.7.3 Authentication unsuccessful

Logon denied.  Check username, password, and domain

NTLM authentication failed

Failed to login using NTLM method

--SMTP_Connect

Failed to connect to SMTP server.

Would anyone happen to know what might cause this behavior, seeing as how all the settings appear the same as they did on the old installation?

  • 0
    This from the World Famous Knowledge Base:

    Error: "Authentication Unsuccessful" sending Test E-mail from Company Maintenance in Sage 100 ERP

    Note: Relevant ChilkatLog error information below, particularly in bold:

    Unable to login to SMTP connection.
    AUTH LOGIN
    500 5.5.2 unrecognized command

    Failed to login using LOGIN method
    --SMTP_Connect
    Failed to connect to SMTP server.
    Failed.
    --VerifySmtpLogin
    --ChilkatLog

    OR

    With Exchange server
    Using Microsoft SSPI NTLM.
    response: 535 5.7.3 Authentication unsuccessful
    Logon denied. Check username, password, and domain
    NTLM authentication failed
    Failed to login using NTLM method
    --SMTP_Connect
    Failed to connect to SMTP server.
    Failed.
    --VerifySmtpLogin
    --ChilkatLog



    Disclaimer

    Operating System Warning
    This solution requires advanced knowledge of your computer's operating system. Contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Always create a backup of your data before proceeding with advanced solutions.
    Resolution


    On the Exchange Server enable Basic authentication.

    In Exchange Server:
    1. Locate SMTP Receive Connector
    2. Right-Click and select Properties
    3. Select Authentication tab
    4. Check the Basic Authentication Checkbox
    Note: This allows LOGIN method to be used by Chilkat
    5. For Sage 100 ERP version 2013+, if email test still gets error then un-check "Offer Basic_authentication only after starting TLS" checkbox.

    Note:

    Version 2013 of Sage 100 ERP uses a different version of Chilkat client from older versions.
  • 0 in reply to BigLouie
    Unfortunately I already tried that and had no success (the resulting error message is a lot like the one I posted except with "Failed to login using LOGIN method" instead of "Failed to login using NTLM method"). Thank you for the reply though.
  • 0 in reply to dkantola
    Have you tried re-entering the user name and password yet?
  • 0 in reply to TomTarget
    verified answer

    Yes sir, among many other things.

    The "solution" I came up with was to create a new Exchange Receive Connector scoped to just the IP addresses of those computers we use to send direct deposit stubs using the Authentication method of Externally Secured and the Permission Group of Exchange Servers. What this does is turn the Exchange server into an open relay but just for those IP addresses. Then I just blanked out the user name and password specified in the Company Maintenance E-mail tab, bypassing authentication completely. This might end up being a pain in the future though because now if we ever need to send direct deposit stubs from a different computer I either have to add that computer's IP address to the Receive Connector or change the computer's IP address to one of the IP addresses that already exists on the Receive Connector.

    Basically I used this solution: sagecity.na.sage.com/.../73992 except I added my own custom Receive Connector instead of using the existing one (his solution as posted wouldn't allow you to send direct deposit stubs to email addresses outside of the organization due to the permissions on the default Exchange Receive Connector for port 25).

    None of this explains why the problem came up in the first place, we're just bypassing authentication altogether now. Wish I knew why this happened, I'd rather it work the way it did originally so I didn't have to worry about managing a scoped Receive Connector.