I want to hear other opinion who using Kinetic 2022.1.3 Cloud. Has anyone faced any issues on release 11.2.100.0 after 2022-05-13 upgrade? We are facing issues with taskagent when it constantly random tasks especially ssrs reports gets stuck, queue increases and taskagent tottaly fails. Maybe someone faced something similar or any other issues. in our case in one area UOM class started to fail on one of part numbers when submitting labor, one day before upgrade the same job was working perfectly.
Would like to hear your discoveries after upgrade
I’ve got a client who I helped with the upgrade to Kinetic 2022.1.3 cloud. When I was testing reports Sunday night, I noted that reports seemed to be taking a long time to preview. Pack slips, for example, that normally pop up in a few seconds was taking about 3 minutes to preview. I wrote that off to Epicor’s servers likely still working overtime on the upgrade and figured I’d see if users complained as of Monday morning.
So far, no complaints from any users on upgrade issues.
About uomclass failing, got some hook from support, it seams they have changed the logic of salvage calculation or something like that. So we need to investigate how the logic works now.
Whats about preview time our consultant allso said that our report generates quite long, but previously some of them like packslip also was a bit slow but it becouse user want to see quite a lot different data in it.
We’re being hit with the very slow performance issue from 6 mins after the hour to 26 minutes past the hour, every hour. We have random error messages popping up and the user can’t do anything until they find the error pop up and dismiss it. DMT works in Pilot, but not in production. Had to use a new installation procedure to replace the production client.
Within the callFunction routine, the serializer was fixed, so our previous work around to get around a broken serializer didn’t work.
Then we had a firewall issue that prevented the auto update from working at a particular location. You can hang that one on us. We had the same issue with Pilot, just not a large enough base to figure out the pattern and find the root cause of the issue. (Turned out the firewall in one of our manufacturing facilities automatically quarantined zip files of a certain size). So the update would download, the firewall would quarantine the zip and there was nothing to install.
Other than that, just the occasional custom report that needed slight adjustments (end users didn’t test in Pilot - but I suspect that’s a forever state).
Have you figured out any solution on this? We are continuing to receive errors on Job Creation and Issuing materials about failed UOM Class. I have received a fix for blank UOM from Epicor, but that has not solved the issue.
I am receiving an issue when I try to salvage a part that does not share a UOM with the UOM class assigned to the parent part.
I had REST calls failing that didn’t use to fail
I had BPM’s made from only blocks that broke and had to be updated.
SSRS reports went down
Dashboards were broken and had to be redeployed
Field Security has changed somehow, we used to have certain fields read only so that people couldn’t change them (example, Entry Date on quotes so they couldn’t make it look like they quoted a customer faster than they did). Now this totally breaks the quote screen so we can’t do that anymore.
A couple random slow downs, but not as bad as a lot of people are reporting here.
In our case BOM was built this way:
Main part UOM pcs
Materials UOM pcs
salvage part UOM weight(Kg)
and the system has been trying to convert that salvage to pcs and was not able to do that. We did not dig a lot in Classes since we decided that BOM not correct we can remove salvage part, so problems gone. So seams salvage has to be in the same UOM or Classes has to contain correct conversions between UOM
As support told, they they have added some new logic into salvage core for calculation
Thanks for the reply. We had been playing with it this morning. We determined that we could add the conversion to the salvaged part’s UOM class and it really didn’t effect anything, but it made the error disappear. I still cannot understand why the change would have now required the salvaged part to have the same UOM available as the main level part, but oh well, I guess.
The only random error message we encountered was in regard to the users personalization could not load. Selecting TOOLS / SAVE LAYOUTS saved the personalization to the new version level and resolved the issue. We notified users before the migration of this popup and how to fix it.
One of the most pressing being an issue with none breaking characters in comments that were DMT’d into customer maintenance. preventing us from being able to take customers off credit hold. Epicor has not proposed a fix yet. The issue presented itself just before the upgrade so i t may be unrelated…
Some of our custom RDD’s needed to be tweaked, as Epicor added some new fields to the Process Payment form that our custom check form did not use
We occasionally cannot check parts back in on Engineering Workbench without getting an error about XFileAttach Table.
Epicor sent us a data fix for this as a temporary fix, and I have been running it when Engineering reports the problem has returned. They tell me the fix for the root cause of this issue is coming in the next update.
With xfileattach we had this last week, it apeared when user dublicated part and somehow system was pointing to non existing mtl seq(null) which has reference to the drawing. I know workarround how to fix this when it is pointing to seq with number but when expression null, then workarround does not help
@BrianP I have a bpm on checkin that removes the bad attachment records. @Justas it happens when the bom is resequenced, but the attachments are abandoned. I am on my way back from Insights but will upload it tomorrow.
If you know what the bad characters are you should be able to sql or baq them out of the comments using replace and then DMT them back in over the bad ones.
Started see errors in PILOT (MT) every morning after it was upgraded to 2022.1. Have to close and reopen. Never had to do that before. Now seeing the same problem in LIVE (MT) and Shop Floor computers are now having this issue.
Did anyone report something like this to Support?