We have been using an Office 365 account to send out our emails from Epicor for years and in the past 2 weeks we have been receiving this message “Authentication failed because the remote party has closed the transport stream.” . Has anyone else run into this recently and have you found out the cause/solution?
I don’t have a solution for you but I can tell you that we have been having the same issue recently so you are not alone.
2 Likes
Not sure if related…
Basic Authentication and Exchange Online – September 2021 Update - Microsoft Tech Community
1 Like
We’re in the same boat right now, trying to use Epicor Service Connect to read/send emails from an O365 exchange account. Getting that same error. It seems the issue is related to Service Connect making the connection with TLS1.1 instead of TLS 1.2. We’ve tried multiple things to update to TLS1.2 and even tried to use a legacy endpoint setup by microsoft without success. Service connect will log into the email, read 2 or 3 emails and then generate the error you mentioned. Here’s a link to Legacy endpoint if you want to give that a try: Exchange Online to Introduce Legacy SMTP Endpoint in 2022 - Office 365 for IT Pros
1 Like
In E10, TLS1.2 can be used in .NET Framewok 4.6.1+ AFAIR.
What is .Net version is used in your system? If greater than 4,6,1 then TLS 1.2 can be allowed with the following change:
<system.web>
…
<httpRuntime … targetFramework=“4.6.1 or later” />
</system.web>
2 Likes
Thanks for the reply. Ours is 4.7. Where do I make this change?
In web.config on server. Better try on non-production installation first
2 Likes
any luck with modifying the web.config? in particular which service connect web.config file did you modify?
1 Like
I did not have to modify our Service Connect web.config as we don’t use it for any emailing purposes but I did notice that at C:\Program Files\Epicor Service Connect\WebApps\IntegrationWcfServices there is a web.config file that has the targeted runtime of 4.5.
1 Like
Edit: Oh, sorry, you said you are not using SC for mail. Please ignore.
Hi Jason,
What is the version of Service Connect that you are using?
I see that you list Epicor 10.2.100.7 as your Epicor version – is Service Connect 10.2.100 or newer?
Question to people experiencing mail errors when retrieving/sending mails using Service Connect using Office 365:
Are you on Service Connect 10.2.100 or newer?
(or maybe we should have a dedicated thread for this)
Our standard BAQ emails are failing with the same error message. Based on our web.config, we are running 4.0. How do we fix this?
1 Like
What version is your server actually running? Find that out and if it’s above the 4.6.1 add the runtime target line in your config.
what is the location of this web.config file?
We’re an on premise 10.2 setup but for us it at \Epicor\Websites"Epicor Instance". I will say that while this has fixed the email issue it has caused another issue with Job Receipt to Inventory throwing an error: “BPM runtime caught an unexpected exception of ‘IOException’ type. The specified path is invalid.”
We are having the same issue (your original one that is). I have already found where the web.config file is but when putting in as @Olga stated, I get an error. It’s all kind of new for me so trying to be careful where I make changes and/or not to make too many at once.
Our test environment didn’t even have the <system.web> bit at all so I added:
<system.web>
</system.web>
just before the final .
The whole thing froze so I recycled the app pool and it started working fine (other than the error I mentioned above).
Thanks. I had done that as well. In fact, when adding just like you have there, it’s fine. When I add the “httpruntime” portion of his text it crashes.
I added/edited that text in the “supportedRuntime” portion at the beginning of the config file and it takes it okay. It may have fixed the issue but hard to tell yet. 
You also fix this issue by adding this to the registry on the sql server
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001