Can anyone point me in the next direction?
We have been testing a move from 2024.1 to 2025.1. The only thing broken is the Mexico CSF process. When we post an invoice, our entry gets pushed to the review journal. Here is a small part of message [Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..] Full message below. The live environment is in its busy season with no problems.
We have been going in circles with Epicor support, but they only focus on the CSF setup as if we are installing it for the first time. We have engaged consultants in Mexico to look this over. They spent a lot of time yesterday looking at everything they could think of. Still no resolution. (Epicor setups, EAC setups, log files, event viewer, certificates – server, SAT, and Interfactura.)
We are testing on a new environment. New SQL and APP servers. Windows Server 2025 with SQL Server 2022. We had our Azure consultants create the machines. We had Coda Bears help us move over a 2024.1 copy and run the upgrade to 2025.1. We are using the same Mex. Gov’t certs in Production and TEST (as we have always done). There are minor differences between the Epicor setups, but I am going to fall back and match everything from the 2024.1 to the 2025.1 today.
Full Error Message
One or more errors occurred. (The SSL connection could not be established, see inner exception.)
The SSL connection could not be established, see inner exception.
The SSL connection could not be established, see inner exception.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
The following exception was found when creating the digital receipt: System.NullReferenceException: Object reference not set to an instance of an object.
at Erp.Internal.Lib.DigitalReceiptsDataSet.AddErrorMessage(String invoiceNum, String errorMessage, String stackTrace) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\Lib\MXDigitalReceiptsLib\DigitalReceiptsDataSet.cs:line 39
at Erp.Internal.Lib.DigitalReceiptsDataSet.AddErrorMessage(String invoiceNum, Exception ex) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\Lib\MXDigitalReceiptsLib\DigitalReceiptsDataSet.cs:line 45
at Erp.Internal.Lib.DigitalReceiptsDataSet.AddErrorMessage(String invoiceNum, Exception ex) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\Lib\MXDigitalReceiptsLib\DigitalReceiptsDataSet.cs:line 48
at Erp.Internal.Lib.DigitalReceiptsDataSet.AddErrorMessage(String invoiceNum, Exception ex) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\Lib\MXDigitalReceiptsLib\DigitalReceiptsDataSet.cs:line 48
at Erp.Internal.Lib.DigitalReceiptsDataSet.AddErrorMessage(String invoiceNum, Exception ex) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\Lib\MXDigitalReceiptsLib\DigitalReceiptsDataSet.cs:line 48
at Erp.Internal.Lib.DigitalReceiptsDataSet.AddErrorMessage(String invoiceNum, Exception ex) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\Lib\MXDigitalReceiptsLib\DigitalReceiptsDataSet.cs:line 48
at Erp.Internal.Lib.DigitalReceiptWriter.DumpComprobanteToXML(ComprobanteBase comprobante, String documentNum, Boolean regenSeal, XmlDocument& xmlDocRequest, XmlDocument& xmlDocResponse, Boolean mxDebugMode) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\Lib\MXDigitalReceiptsLib\DigitalReceiptWriter.cs:line 226
at Erp.Internal.Lib.DigitalReceiptWriter.DumpComprobanteToXML(ComprobanteBase comprobante, String documentNum, Boolean regenSeal, Boolean mxDebugMode) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\Lib\MXDigitalReceiptsLib\DigitalReceiptWriter.cs:line 138
at Erp.Internal.Lib.MXGenDigitalReceipt.GenerateDigitalReceipt(Int32 invcNum) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\Lib\MXGenDigitalReceipt\MXGenDigitalReceipt.cs:line 268
There are a couple other posts from the last week about CSF issues. But I think those were all cloud customers.
Its seems like Interfactura is blocking connections from your new environment IP Address (An existing connection was forcibly closed by the remote host..).
Are you already generated a ticket supoort with Interfactura?
Thanks Victor. We will get our TJ office go down that path.
Scott
I replied at the same time as @scott included the full error.
It does seem like a access issue or something with certs given the full error.
Hi Scott, which PAC are you using to stamp your invoices?
If you and other guys looks already at the Epicor Setup (PAC) to me sounds like a network issue, I saw it before in one of my new server migrations, the new server require some Network configuration (swithing level) to allow the correct PAC connection. When I discard everything at that time I ask the Network admin to see if any port fowarding, open ports, etc. was setup in our previous server and he found some rules that after applied to the new server the invoice post works like a charm.
Problem solved. It is all over my head, but here is the shorthand notes I took.
New Server OS 2025 had reduced the amount of default encryption cyphers that it used. My guy activated all of these cyphers, and the problem was solved. After the holiday he will work on identifying the old cypher that Interfactura is using and turn off all of the other old stuff.
Scott
Nice to ear its working now, you can now enjoy the holidays