We have a few Windows 10 clients that when you try to launch the application the first time, it never launches. You click on the client and the windows wait cursor spins for just a sec and then disappears. The AutoUpdate never launches and neither does the sign on screen. I have an open support ticket with Epicor but I wanted to post here just in case someone else has experienced this issue.
Come to think of it, I think I’ve run into that. Delete the client cache.
There’s also an issue going back to at least 10.1.x where you open a form like Order Entry and the entire application just quits with no error. If it starts happening a lot on a particular machine, deleting the cache seems to help with that, too.
If all else fails, check the Windows Event Viewer under Applications and Services Logs | Epicor Software Corporation Client Log. Make sure you’re showing information messages, not just warnings and errors. It logs a ton of errors as information.
Hi @MattPrice81 ,
I agree with @KevinK .
Could be totally because of the version. Any reason you have stuck with 10.1 ?
Some of the bugs in the application impacts the stored data (for instance a bug i calculation of labour cost) and later you would find it far down the road, causing a lot of headache of course.
I would suggest upgrading to a newer version. If you read the documentation and release notes, you will see what issues have been fixed so far.
I wasn’t suggesting it was because of the version. I had the same issue in 10.2.x and I have no reason to believe it was ever fixed. In fact, I reported it and was told that support wouldn’t even pass it along to the developers because there were no clear steps to reproduce, and because the workaround of deleting the cache exists. The problem with the client sometimes randomly exiting without error persists to the present day in Kinetic cloud.
There are other serious bugs related to the cache or worked around by deleting it. For example, if you customize a UI form, weeks or months later, a few users will randomly start seeing the old version of the form. Deleting their cache fixes it for a while, then the old version mysteriously reappears again.
Hi @KevinK ,
Windows deprecates some libraries and methods from time to time and since Epicor is a Winbdows application wrapping a webapp on some level, it is expected to encounter issues. That I why I suggest upgrading to a newer version for Epicor.
However kindly proceed with caution and install the new version on TEST environment and then run it on the impacted systems to see if any improvement can be seen.
Regarding the weird bugs and errors, I still think could be mainly version related BUT I have seen them for one of our users specifically and what happens to him is that he has two separate systems, one Desktop, and one laptop. What happens is that he saves some settings and personalizations on his Desktop and that gets cached on his Desktop, then later when he uses the laptop, that cache is not on the laptop and that causes error, then this causes the Desktop also hit an error two. In a weird way it seems Epicor tracks what each user is doing for persoalization and if that does not match the cached info on the system, causes issue.
We saw these errors in a corporate environment where all the hardware and software was theoretically identical. But clients silently not starting and old versions of forms reappearing both seemed to happen more in the engineering department, as if something somewhere in Engineering Workbench or the other related parts of Epicor is what triggers the cache corruption. We never pinned it down and just kept deleting the cache.
Just to confirm, have you purged the personalizations?
I had something like this recently with my PC with all of my Epicor shortcuts. In task manager the program was running, but it never came out of background tasks. I set compatibility and it went back to normal.