Hi,
We recently noticed a large number of .NET errors in our server’s Event Viewer, and they appear to be coming from multiple BO GetByID calls. For example, some are originating from various UD tables, while others are coming from Epicor BO calls.
In this older post, @hkeric.wci Haso mentioned that this is an Epicor-related issue caused by their migration to .NET Core and that the errors are harmless.
Does anyone know if Epicor has come up with a solution for this yet? If not, is there a recommended workaround? Would it make sense to wrap the GetByID calls in a try/catch block?
Below are some of the errors we’ve been seeing:
You should just ignore it.
A RecordNotFoundException is the 404 of GetByID. How would I know https://google.com/switchtobing doesn’t exist unless it tells my browser? Catching the exception in a BPM (even if possible) would be Google not sending back a 404 page, leaving my browser to spin around waiting.
It might be annoying they’re verbose about logging it, but it’s hard for them to determine who wants what exception logged under what circumstances. I’m fine with that, rather than it being ignored like I do in my code… sometimes. 
I also see that the record they are looking for is in Ice.Common, which is where standard reports and other shared resources are stored. Search for Ice.Common here and you may find some potential solutions.
Thanks, Genoah.
We’ve recently had users report some performance issues within Epicor, and we thought these Event Viewer errors might be related.
If these RecordNotFoundException messages are expected behavior and not something we need to worry about, have you found any way to reduce or filter them from the Event Viewer? It just seems like they’re being generated quite frequently, and the volume makes it harder to spot logs that may indicate actual problems.
I will do some more digging, thank you Mark!
