It never loads.
What values do you have in your sysconfigs for MaxBOMRU and MacClssAttrMRU? If they aren’t 0, have you tried setting them to zero - does it work ok then?
1 Like
Yes but that has to be done one computer at a time. Its not practical.
The client *.sysconfig are being fixed as we speak, and you will only need to restart the client to get the fixes.
If you need a workaround, set the two *.sysconfig file values back to “0”. This will get you running, but might take a long time on your first log in. When you close the app, it will update the two files I’m going to mention next.
If you want to clear the files yourself, open File Explorer to “%PROGRAMDATA%\Epicor”. Find the directory that is the host part of the URL of your application server. Next find the directory which is your version number. Next find the directory of your company. For example, mine (for next release) is C:\ProgramData\Epicor\localhost-5001\5.0.100.0\EPIC03. Under that are two directories “BOSecMRUList” and “ClsAttrMRUList”. Delete the files in those directories. This should get the client running quickly again.
4 Likes
When can we expect the fix for this to be pushed out? Is this included in the maintenance for this weekend? Or will an update be provided sooner?
I’m glad to hear this but . . . what happened? Why was this fixed, then broken again? And how do we know its not going to continue to break every time we get an udpate?
I just experience my client updating when exiting and starting Epicor.
They must be working on this again.
1 Like
Installed 2024.2.9 > and issue doesn’t seemed to be resolved for me…
case created although very limited response