We’ve been having random issues with some Kinetic screens not loading (getting errors).
It initially happened about a week ago where Part Entry wouldn’t load. I thought perhaps it was a customization issue… so I turned off a customization layer, saved… and the form then loaded. I turned the customization layer back on… and it worked as usual. It’s like it needed refreshed or something.
It happened again with Order Entry… I did the same “fix”… and it started working.
This morning it happened with PO Entry (and PO Tracker). But we don’t have any customization layers on these screens… so there’s nothing I can find to do to “refresh” these menus.
We just get the below error:
This is company wide… not just me. Classic PO Entry will load… but Kinetic will not. Error occurs in both Desktop Client and Web Browsers.
Not sure how to correct this issue… but this is the 3rd form to randomly have this issue over the past week or so.
Had this happen yesterday on the PO Print dialog, specifically for one user who was using the desktop client. I forced the dialog to open in Classic mode via Menu Maintenance, just to get around it. Not sure what the root cause was/is.
I have seen this when the browsers are waiting for an update, and there was patching done yesterday. I had one person with a 401 this morning and a reboot after applying patches seemed to fix it.
Yes this has been happening to us too. I finally received instructions on my most recent case on copying and then clearing the cache on the server to try to get to the root of it (the next time it happens).
We’ve been getting these errors for over a year & support has never been able to track down a cause. Order Entry, Job Entry, PO Entry…incredibly frustrating.
These are the instructions I got from support (our issue is with order entry specifically):
The path to the cache file will be on the deployment server and look something like this: deployment/server/apps/metaui/Erp.UI.JobEntry/cache (note: this is the Job Entry path, you’ll want the Order Entry path). There is no harm in deleting the cache as it will auto regen if it’s not there or if the existing has expired.
So the Action Items that would be helpful are as follows if we have another event:
Create a ZIP back up of metaui/…/cache folder (include metaui on down to cache, name it “bad”)
Delete the cache file
Open Order Entry
IF the form loads with all of the content correctly, THEN
Create a ZIP back up of the metaui/…/cache (include metaui on down to cache, name it “good”)
We have been experiencing the same issue with our Order Entry and Tracker on the web app since Wednesday. Desktop client works fine. Support hasn’t been able to give any suggestions that work.
They told us to delete personalizations on the specific app screens, so I went to client version and reset to default in personalization but it still won’t load on the web.
Republish your custom layers, that is what has fixed it for us several times. If you see my post above yours, support seems to suspect it has to do with the caching of the layers on the server itself. Perhaps republishing them recreates that cache.
This hasn’t happened in a while… but reared its ugly head again.
As I stated in my first post, and @aosemwengie1 confirmed in hers, if you have customized layers on the problematic screens, you can toggle them off (SAVE) and back on (SAVE) in Menu Maintenance. this should refresh things and they start working again.
If the problematic screens do NOT have customized layers, or the above doesn’t work… I was instructed to run 191 MetaUIMigration in Conversion Workbench. This worked in the past and just worked again.
Description: Migrates MetaUIs from disk to DB.
I came back here to find the process I needed to run and realized I never posted the solution I received from EpiCare. Hope this is helpful to others.
We just started seeing this issue on the Kinetic AP Void Payment Entry and we have no custom layers or personalizations. Epicor Support had me run the 191 MetaUIMigration in Conversion Workbench which didn’t resolve it. They also had me check for kinetic personalizations using a data fix. Correction: This just started is happening in 2023.1.10 and with the 2023.2.9 upgrade. Epicor Support seems stumped. Does anyone have a suggestion?
We’ve been fighting this a long time - with your Epicor window in focus, press CTRL+ALT+i. That’s supposed to clear the cache file on the server and works…sometimes.
Depending on this flag that @vingeance told me about you’ll either need to run that conversion OR you need to go to your event viewer and find an error about a file lock error in a directory on your app server.
