User has windows 7 Pro, when opening the Epicor program windows asks for Admin credentials on a User Access Control windows ( UAC ). ( If I turn UAC off, then the user gets an error where the program cant read any config files.
If the user types in credentials for an ADMIN user, Epicor opens but doesn’t have the correct printers.
Nothing has changed, except the server went down a few months ago ( before I worked here )
I’m very new to Epicor, I’m an IT professional, just hired.
Any help would be helpful. Thanks.
I find this occurs when the user does not have the correct permissions to the local Epicor install folder (or perhaps files).
Does the user need full control of the following files? If not, which rights should a user have?
server location is…
\server\ERP10.2.400.0Deployment\Client\config…
files are…
epicorlive.sysconfig
default.sysconfig
It’s been so long since I had to solve this issue…
Have you tried Read/Write on that folder?
The Epicor Client reads the Server files to see if it needs to update itself and the Windows user only needs Read access to the Server files. The Windows user should have Full Access to the local Epicor Client folder and sub-folders.
1 Like
User has full rights to local Epicor folder, and Read/Write to server files.
However when user opens the app, windows still asks for UAC credentials.
I could try turning UAC off, that requires a restart and I’ll have to wait for the user to take a break.
…That didn’t work.
Make sure the user is logged into the domain and not the local machine. Hardly anyone really looks at the domain field when logging in to their laptop/workstation.
This was installed on his machine before I was here. I’m thinking about making him a local Admin, and reinstalling Epicor. I don’t want him to lose his favorites inside Epicor, is this a local file that I can be sure not to remove? Does Epicor like it better if UAC is off ?
Pretty sure every personalization (favorites, form layouts, etc…) are stored in the Epicor DB, and not on the users machine. If you’re really concerned, just install the client to a different folder. I make a different folder for each App environment
c:\Epicor\ERP10.2Client_PRD\Client\ for our Production environment
c:\Epicor\ERP10.2Client_UAT\Client\ for our UAT (User Acceptance Testing)
I don’t ever recall any users ever reporting a UAC request.
Also, when the Client Install is run on a workstation, the settings selected during the install are used to create the batch file silent.bat. This is supposed to be so that you can then repeat the install on other workstations with the same exact settings. I’ve found the BAT file created doesn’t really work.
The Epicor Client does almost nothing that would interact with or trigger UAC. That said, the Client may run afoul of UAC based on installation location or running on a shared environment.
Windows has several folders that are “Windows managed” and activities that alter those folders can trigger UAC. The “Program Files” and “ProgramData” folders are the ones that commonly interact with the Epicor Client. Program Files as that is where many Windows Administrators will install software and ProgramData as that is the default location for the Epicor Client cache.
As the Epicor Client is self updating and language satellite assemblies are generated and written out as needed, the Program Files location for non-Admin users can be problematic and you might want to use a folder structure like @ckrusen references.
A shared system - where you have different Windows users using the same environment - can also cause UAC or permission issues, especially if the Windows Users have different access rights (Admin User and a non-Admin user). That usually manifests itself via ProgramData and the shared Epicor Client cache but can also occur due to permission conflicts with the generated language assemblies. Problems with Shared cache can be resolved using the Windows User environment variable in the AlternateCacheFolder path (Sysconfig setting).
@rfarrar74 - add " /Skip" to the end of the Epicor Client Shortcut the user is executing. That will prevent the Client from trying to auto-update and if that gets them to a logon prompt, the UAC problem will be related to wanting to update the Client. If you still get the UAC challenge, it might be time to do a fresh Client install to a non-Windows managed Folder and setup the AlternateCacheFolder with the User Environmental.
@Rich I tried the /skip and the UAC still appeared…
I think the “no longer working here” IT guy, installed the software as himself, and not as the user.
so a simple uninstall and reinstall should fix that. Are there any user files that are kept locally that I need to know about before I remove the software? Thanks.
Generally not but best to Zip up the directory before deleting just in case there are any custom components installed individually.