You’re offline. This is a read only version of the page.
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?
Hello Brian,
You would need to swap GP to use MAPI in System Preferences and it might work (with the normal MAPI caveats).
TLS doesn't really matter here, its a question of code, with Exchange 2010 using different code then Exchange 2013 (Which is the code we are calling).
If they can't get MAPI to work, then they really only have the option of upgrading Exchange (Which they need to do regardless).
Thanks!
Trying to update this customer's exchange server and outlook clients (Outlook 2010) will be a massive effort. The planning and rollout will take more than weeks to complete.
As a stop gap measure could they enable TLS 1.2 on their current Exchange Server 2010 and continue to use Outlook 2010 32 bit MAPI Client?
I am guessing from reading your posts and replies the only option is to upgrade Exchange Server.
Brian
Hello BPhill,
The issue here is with Exchange 2010 and the new endpoint GP uses to attempt to work with MFA and TLS 1.2.
This is all laid out in my article here:
community.dynamics.com/.../an-unknown-error-occurred-while-emailing-from-gp-18-3-using-exchange
To put it as quickly as I can, the general change is that the new DLL we uses defaults to Exchange 2013 style code, which does not work with Exchange 2010.
The only real solution is to upgrade Exchange.
As a note, Windows 7, Outlook 2010, Server 2008, along with Exchange 2010 are all out of support. Generally speaking GP doesn't care, but
in this case GP does.
Let me know if you have any questions or concerns.
Thanks!
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
290,524
Super User 2024 Season 2
#2
Martin Dráb
228,469
Most Valuable Professional
#3
nmaenpaa
101,148
Share
Report
All responses (
Answers (