I’m interested in what this alternatecachefolder holds.
Typically the alternate cache folder key has no value and by default “Cache folder” gets automatically created in the c:\ProgramData\Epcior\ServerName:port folder.
You would only set this value if you were going to be running the smart client on an RDS server and you want segregate users caches or if for some reason your client PC is so locked down that the user can’t write into the ProgramData folder, or you would rather not have it buried in ProgramData to more easily delete it with extreme prejudice when the time arises (I know I used to do this in E9), particularly when the clear client cache just did not seem enough.
When the Epicor client starts up if the folder does not exist then it gets created with a whole directory structure for each company
Information such as
- customisations
- MRU
- dashboard assemblies
- themes
- spell checker dictionaries
- browser cache (I’m assuming for essential objects browser that gets spun up when you use the active home page with the smart client
- plus a lot more such as the pesky export directory that you see as default when exporting dashboards
For the most part the files stored there are meant aid in improving performance, that’s my understanding
I hope answers the question. @utaylor, or were you asking what was in the folder from @askulte post specifically?
I must admit I have always been interested in some of these keys in the sysconfig that don’t get a heap of explanation, like splashscreen logo etc.
Using StartSystemMonitor = False didn’t work for use either. @askulte Do you get the cache files being created in the client directory when you use that configuration with the AlternativeCacheFolder?
Matthew,
I’m not sure. What do the cache files look like?
Here’s my client folder:
The Epicor folder seems to have cache files in it:
Yes, that folder would be it. I ask because I’m not sure I understand why moving the cache folder there would make any difference, assuming that the default cache directory and client directory are stored in the same general location and was curious if moving it to the client directory show how changed the behavior.
The cache folder gets created/updated by the client in the context of the logged in users security, so If the permissions on the folder were wrong then you might get an issue. But it would be more like an access denied error dialog which would happen just before the icons start appearing on the active home page (don’t ask how I know).
I agree with @regency-mho I don’t think moving it to the client folder would make much difference either.
In my experience the spinning wheel/blank screen is either a lack of resources on the app server or the client and the loading of the kinetic home page times out. Perhaps it’s an EOBrowser timeout setting.
The LaunchType option is where you can force the client to use whatever menu UI.
One other consideration is if you have your AV exclusions configured. If not this might be impacting things by it examining the files as they are being created/updated and slowing things down to generate a timeout.
@Olga would you be able find out what was changed.
No, i am not in cloud team
I have a ticket with support. I’m now able to replicate this issue with the same user IDs but on different machines while simultaneously showing that other users never have a problem logging in at the same time. Support did already provide me an alternative client config in which the cache loading behavior is supposed to be modified (how I don’t know), but that hasn’t worked so it’s back to them to investigate further. I’ll provide an update once/if this is resolved.
We too are having this issue with delayed login times, sometimes upto 5 minutes before the login is completed, and then opening an app can take anywhere from 30 seconds to 5 minutes also.
our case has been with the cloud team now for 2 weeks with no resolutions suggested.
i have tried clearing the user cache etc as well as the BAT file provided above with no improvements.
This topic is already closed. You should consider raising a new one.
Quick query though - do you use Sophos Antivirus? I’ve had a customer site where that was killing the Epicor smart client, it’s a known Sophos issue with a documented fix.
yes we use sophos, at the time when this was happening, Epicor did a small update and there was no documented fix, it is now resolved though!
Hello everyone,
I have explored and attempted all the suggested solutions, but unfortunately, none were successful in my case.
However, what ultimately resolved the issue for me was resetting the user password. Upon resetting the password, the system prompted the user to create a new one during the next login. Once the new password was set, the issue was resolved, and the user was able to proceed without further problems.
While I am unsure of the exact reasoning behind this, it effectively addressed the issue.
Thank you.
1 Like
Some of our users were experiencing this and the issue was that user accounts created a long time ago had the password expiry set to more than 120 days, which now isn’t allowed in the Cloud. Changing the expiry time to less than 120 days and resetting their password fixed the issue.
2 Likes