Weird client issues

Unsure how to explain this but I’m seeing some weird issues with the Epicor client.

Both in production and pilot. I do run it on a VM on my machine but I’ve never had issues before. I uninstalled and reinstalled and still have the same issues.

Basically, if I open any window, like Order Entry, then I try to search for an order, it will pull up the orders but then I can’t select one. And then if I try to close the search window, it won’t close. I can move the window but nothing else. I end up having to force quit Epicor.

Weird thing is, I tried this on another VM (Azure - not local) and I have the same issue.

I’m guessing it’s time for a ticket?

Are you running the classic still? Is it possible that your AV, Malware, Ransomware software, etc is thinking the search popup is nefarious?

It’s Kinect but the local client, not the browser version.

I doubt it’s the machines/AV software. The local VM is a fairly new install and the Azure VM is like a few days old with only local network access. Everything works on both machines. It’s just Epicor that is the issue. The Azure VM doesn’t have an AV/Malware software other than the Windows one.

Are you sure you have not enabled tracing and have the Enable EO Browser Trace logging enabled. (might be a long shot)

As @gpayne mentioned might be AV, so check your exclusions.

No go. I’m going to make a ticket. Unsure what the deal is.

Has the search been customised, if so try the basic version…

Nope. Tried a few other things. Same issue.

Also this only applies to pilot. Not Production.

Created a ticket for this.

1 Like

Just to update, now my production environment, for only my account seems to be a problem.

Opened order entry, entered an order, it slowly comes up. Then I try to reopen the order and it hangs.

Have you tried personalization purge and/or deleting the cache directory? I’ve seen weird issues for our users when they have two personalizations on the same form as well as some occasions when their C:\ProgramData\Epicor\ folder contains corrupted files

Shouldn’t matter for the Kinetic Web screens, even in the client.

Sorry didn’t catch that it was the web client. :grimacing: