When I try to print a Packing Slip, Epicor is thinking and after a few seconds shutting itself down without a error message. When I check the system monitor, the following message is showing:
“ERROR: Run in preview mode from System Monitor for details. Arithmetic operation resulted in an over”.
It stops after “over”, and there or no more details to check in History Tasks.
I have to start Epicor again, and then I can print the same Packing Slip with no issues. Is this a connection issue with our printer maybe?
It is not always an issue, it’s very random.
It sounds more like a formula issue. Are you using the base packing slip, or have you modified it to show any custom calculated fields? Look out for any divisions, as divide by zero can show up when you least suspect it, and often throws an untraceable error.
With Epicor shutting down like that, it is hard to say. We had an issue where every once in a while while printing checks, Epicor would just crap out and close with an error. Support tried to give me ideas for a couple of months to fix it. They had me change some timeout settings in Windows registry. I haven’t had the issue again, but it happens so randomly that I don’t know if it is really fixed or not.
I would start with trying to run the base pack slip. and see if you ever get the error to happen there. If you do, then you have grounds to head to support. If you don’t see the issue in your base report, then you have a customization issue. Something in the customized report is tossing that error and it is likely a calculated field somewhere.
Good luck!
1 Like
Hi Nate,
I have tried printing several packing slips with the standard Epicor Report Style.
The same issue occurs when I try the base packing slip. So it does not matter which Report Style I use. So this is no custumisation issue. But thanks for the reply anyway.
If you can rule out custom report styles, and calculated field issues, then you should push this up through support. They will run you around in circles trying to get all kinds of traces, and logs. Just play along and eventually they will probably figure it out. Good luck!