We upgraded from 10.2.500 on prem to 10.2.700 to our own Azure Cloud. We are using Azure Load Balancer, and the Epicor Client is ran through Citrix. We have three App servers, a Database Server, and Reporting Server… Users are having Epicor Go Offline…Any Ideas?
Are you using Net.tcp or https? If you go over a WAN, https is MUCH, much nicer. In Kinetic, Net.tcp is being phased out.
1 Like
We are using Net.Tcp… I kept getting a certificate error when i tried setting it up with https
I would second https. We had an issue with net.tcp and moving to https solved it. I am totally onprem, so I made my cert with windows CA and as long as the friendly name matched Epicor was happy. But I know nothing about cloud hosting, so it could be way harder.
Also, just curious if this was a recent upgrade why only to 700 and not to 11.2 and stay classic?
We have a heavily modified system and we started this upgrade 11/2021 hoping to go live 3/2022, but the issues we had with servers in azure it extended… These were our first server builds in azure.
Ouch. It sounds like you need a cloud networking consultant to get https solved unless you have already gone there and not had luck.
1 Like
First of all, you should check server log for errors, not just client message.
Second, with load balancing you for sure will need this line uncomented in web.config
<!-- Uncomment this element when AddressFilter mismatch at the EndpointDispatcher happens
<AddressFilterModeAny/>-->
third, you have to figure out certificate subject name, and whether you use SSL offload on your LB.
If yes, your cert should be issued for your LB and placed there and server should use offload binding.
3 Likes