I wonder if that’s what the issue is. It can’t load that icon (throttling maybe?) Or something like that, and it just hangs. That would be stupid… but???
This is me totally guessing here, hopefully someone who knows more than me can chime in.
2 Likes
That can’t possibly be it, can it?? That would be insane.
2 Likes
What does console tab show?
anything else in red?
No the rest of the screen is blank
What’s interesting is when I first launch it all the tabs are blank for quite awhile. I have to let it sit before anything shows up.
So for this user, after the update, the client worked fine. Then yesterday, spinning wheel of death, cleared the cache and it worked fine all day. Then today, spinning wheel of death again.
If you go to the headers tab of that last call, copy the value, then paste it into a browser, do you get something?
I do notice that it notes that it’s coming from the browser cache. Not sure if it’s relevant or not. But I had the white screen problem for a while after we upgraded, but it’s since gone away. I haven’t done anything different, but we don’t get upgraded every five minutes being on prem and all.
1 Like
Well now the screen is just blank.
For us it’s anytime the user closes Epicor and tries to relaunch. Doesn’t have to be the next day.
Sure, just keep rubbing it in @Banderson 
3 Likes
You can disable cache on the Network tab, then it will reload all from server. The thing is that after the files download the code is not showing to make any server calls on others screenshots.
Testify. All these trouble reports are scaring me away from a cloud setup. 
3 Likes
Epicor sent these instructions to me to try. The article is 4 months old though so I am hesitant to think this will fix the issue. Has anyone seen this suggestion before?
Epicor just sent this to me to try
There is a setting named AlternateCacheFolder in the client\config*.sysconfig files that can be changed.
- Navigate to your local Kinetic/ERP client\config folder.
- Create a backup of each .sysconfig file you plan on changing.
- Open the first .sysconfig file in a text editor.
- Edit and search for the term AlternateCacheFolder
- Between the double-quotes, you can enter a physical folder location such as
<AlternateCacheFolder value="c:\epicor\clientcache" />
In addition, some global variables can be used in concert with a physical path or instead of depending on the variable used. Examples:
-
- %username% - The Windows ID of the user.
<AlternateCacheFolder value="c:\epicor\clientcache\%username%" /> - %temp% - The temporary folder for the logged in Windows user
<AlternateCacheFolder value="%temp%" />
- %username% - The Windows ID of the user.
- Save your changes and repeat the process for each database (.sysconfig file) that you plan on using.
- For on-premise customers, if you wish to have these settings be used for all new client installs
-
- Navigate to \\ERP1x.x.x00Deployment\Client\Config
- Repeat steps 2 through 6 above.
Where would the “normal default” cache be stored? We were assuming it was in the program data folder and thought we were clearing it.
1 Like
We got the same KB but it didn’t work for us. Just throws the cache files into a different folder.
1 Like
Yup, it would still require the user to manually clear the cache from a folder they may not have rights to access (AppData). Not a long-term, sustainable solution.
These steps from Epicor Support worked for a few of our users this morning.
On the affected workstations, please perform the steps below to delete the Epicor client cache.
- Close the client
- From Windows, Open File Explorer
- Navigate to C:\ProgramData\Epicor
Note: ProgramData is a hidden folder and you’ll need to click on the View option to check the hidden items. - Here you will find a folder named after your server, with a port number appended to it, (e.g. servername.domain-808)
- Delete this folder, sub-folders and files
NOTE: these folders will get recreated again when the user logs into the client - Log into the client and follow up with the results.
1 Like
Yes clearing the cache works. The alternate cache location thing is a workaround for users who don’t have permissions to c:\programdata. We don’t have that issue so the solution is NA.
The problem is that we cleared the cache yesterday, and today they are back to spinning wheel of death. This should not be a daily activity to keep the client running, something is wrong.
1 Like
Good to know. Sounds like more fun to look forward to for me as an admin tomorrow until Epicor addresses the underlying issue. Thanks
Thank you this is what I needed