After my client’s GP version 2018 year-end 2020 update was applied, they were no longer able to email EFT remittances from within GP. This was working fine prior to the year-end update. Now when they try to open Email Settings or process an email EFT remittance, when you type in the correct Exchange/AD credentials, it says “Login Failed: check your login information and try again.”
Nothing else we know of has changed outside of the GP year-end update. Both Windows 7 with Outlook 2010 and the Windows 10 with Outlook 2013 computers have the same behavior. The Outlook bit level is 32-bit, and we’ve tried both Exchange (what it was set to) and MAPI, with no success. We’ve validated that the Exchange EWS URL is correct and responding, and that AutoDiscover is working properly. We’ve tried the Login ID with the UserID only, the Domain\UserID format and UPN format (userID@domain.tld) as well.
One item of note is that they have an older Exchange environment – Exchange 2010 running on Windows Server 2008 R2. Since this version is out of support and doesn’t have TLS 1.2 turned on by default (and they have not turned it on), could this be the issue? Does this latest year-end update force all GP communications to use TLS 1.2, or at least the email portion? Also, if yes, is there a way to temporarily allow GP to use an older TLS version?
