No it doesn’t consume all my system memory I think its hitting a 32 bit addressable space limit, so while I do have more memory available the Epicor .NET Process is hitting against the 2/3GB limit for the 32 bit Epicor.exe process.
I suspect if I have my users run Epicor64.exe we’d get past this, but… that causes other issues.
I will share the complete exception when I get it again, but its the same as above.
I agree, it was completely purported and makes no logical sense… but as a complete stab in the dark… 20 reporting daily occurrences and 20 NIC changes later… no other action taken and we’ve had no incident reports for at least 2/3 weeks now.
Try enabling tracing for the EO Browser, maybe that will give something useful.
There is also a server side flag, “trace://ice/fw/kinetic”, but I have no idea what it is supposed to log.
In my case not really and the error seems to be fleeting in these cases. Like when it legitimately happens Epicor just totally crashes in many of these instances you close the error and it’s biz as usual not always but 80/20
In this case it’s a slow death as errors creep. Epicor exe is only at 635 MB nominal
I haven’t used this type of client logging, but you can modify Epicor.exe.config and add below trace flag under system.diagnostics/switches
<add name="AssemblyReflector" value="4" />
This should provide more info as to what is being loaded when it fails, hopefully that gives more information.
Trace flag didn’t come through @Jonathan can you try again?
