I’m seeing a large number of Windows Event Viewer entries being generated by Epicor, and I’m wondering if this is expected behavior or if something is misconfigured.
Every time a user opens a menu, Epicor writes an Information event similar to:
Telemetry: Menu OMMT3001 was not loaded, perhaps company XXXX opted out. Tenant:
This happens for every menu that is opened, so the Application log fills up very quickly with these telemetry-related messages.
Is this normal?
Epicor Kinetic version 2025.2.18, and otherwise everything appears to be working correctly.
I’d be interested to know whether this is expected or if it’s something worth opening a support case for.
We see it too. We have forever. We just chalk it up to Epicors lack of logging hygiene. They constantly spit out useless logs, and leave out ones you need.
Did you also notice Ice.Diagnostics.Log.WriteEntry() now writes a Warning instead of Info to the Event Viewer? Perhaps it was always a Warning, and I just dont remember.
I didn’t do the leg work to double check where this one is coming from, but I think that’s how this message was created, and this is just and information message. Isn’t there a parameter to control the level in that call?
To clarify the response from support was it is fixed in 2026.100 (these events come from classic screens which are removed in 2026.100 so easiest fix ever).
If they are not fixing the issue in 2025.2 then that tells me 2025.2 is out of support?
That was always my issue with the idea of “sustaining support” vs active support. Epicor has been of the stance for the past 5+ years that only the most egregious issues get any kind of backwards updates. So I can never really tell what the difference was between those 2 levels actually are. You are 100% current, or you are not. Falling 2 years behind and moving to sustaining support changes what exactly? 1 year behind is functionally the same as 5 years behind as far as support is concerned. (from my limited perspective).
I think in past years (E9-ish era) they would issue hotfixes much more liberally and they also didn’t put out a new version every month so it came down to active getting new hotfixes and sustaining only getting those that existed. IIRC sustaining support also loses the ability to call support to create a case short of system down, they must use the web to initiate a case.
I agree though, in the ‘modern era’ there is not much of a distinction IMO.
