Have you tried setting the update option to not clear out the client folder during the upgrade?
Weâve tried that option as well, but that gives us the error âThe file âC:\Epicor Software\E10Client\Epicor.ServiceModel.dllâ is currently locked. Hitting Cancel will cause AutoUpdate to exitâ. If we clear the client folder, AutoUpdate.exe hard-crashes when we run it individually.
@MarkBetts Itâs no use, Iâve looked at the the code they run the update as admin no matter what.
Itâs not working for me either, we have to wait for 10.1.600 indeed.
We wrote a .bat script that copies the epicor localclients zip folder from the app server and unzips to the client pc. I also implemented a .bat âlauncherâ that the e10 shortcut points to. When launched, This checks to see if the version file in the client directory matches the version number on the server. If it does not, it wipes the epicor client directory and re-downloads the client, if it does it goes ahead and launches epicor.exe with any specified switches you want. The auto-update with UAC has been a problem for years now and this was the only solution that i found that works and would not require us to run around putting passwords in for users after an update was performed.
Interesting⌠are you able and willing to share the script? Something Iâve been waiting for Epicor to fix as I also donât like having to visit many many workstations each time and upgrade is applied!
I figured out how to get his to work. I used Process Monitor to see what the command line arguments for AutoUpdate.exe are when the Epicor.exe program runs it. AutoUpdate.exe gets copied to a temp directory and run from there.
So I modified my batch file to run the copy on the server and give it arguments for the local client copy, like so:
pushd â\\servername\ERP10.1.600.0Deployment\Clientâ
AutoUpdate.exe âEpicorERP10.1.sysconfigâ âInstallPath=C:\Epicor\ERP10.1Client\Clientâ
popd
Now when I push out the batch program and run it on client machines, it will download all the client files, and any updates that I included in the serverâs copy of the .sysconfig file, right away instead of users having to wait for all that to download when they first run it from the shortcut.
@JasonBennett Did you ever resolve this issue? We have one user that occasionally experiences the locked dll when AutoUpdate runs which usually requires a full reinstall of the client. This just happened again today with the latest update 10.2.300.1. We are Dedicated Tenant.
Hi Tom,
Iâve only seen this with a bad shut-down of Epicor. Restarting the workstation seemed to fix the issue without a complete re-install. We, too, are Public Cloud - Dedicated Tenant.
Mark W.
Like @Mark_Wonsil said, I havenât seen this issue since we moved to 10.2.200 unless the PC was still holding onto the file for some reason, but we locally host our own environment so that could affect things. Iâd try restarting the PC first as well, but aside from that Iâm not sure how much help I can be.
Does anyone here use âSCCMâ ? We use that to Deploy to 1000+ PCs. https://www.microsoft.com/en-us/cloud-platform/system-center-configuration-manager-features