Unable to install Epicor Client 10.2.400.6 on local computers

I did an upgrade this past weekend to 10.2.400.6 and everything went great, EXCEPT now when I try to roll out the Clients they do not install. It seems to create the local client folder but never downloads all the Client files, just some basic ones shown in the screenshot. If I run the “AutoUpdater.exe”, it launches temporarily and show a progress bar for about 1 second then disappears. There is no error log that is generated. I have tried this on various computers.

I am going to call Epicor Support about this, but just curious if others have experienced something similar.

1 Like

What version are you coming from? When you did the Epicor client install it should have already downloaded everything you needed no update necessary. Did you uninstall the old client then install the new client if you went from a 200 -> 400 or 300 -> 400 or try to install over the old folder?

You can’t just run AutoUpdate.exe manually that won’t do much at least not without some parameters. What happens when you run the proper Epicor shortcut with the sysconfig and such?

Random question: do your usernames have spaces in it?

AutoUpdate will only update minor versions, it won’t work with major versions - you will have to reinstall Major Version – or bundle a .msi. I am with Josh.

This isn’t accurate, it will update major versions too if setup correctly.

I mean out of the box it’s accurate, you sort of have to jury rig it to work across dot hundred releases, but thanks for voluntolding what needs to be done to get the new stuff to pull from the new deployment folder lol

Well, I did a 1 hour + WebEx Support call with Epicor and we could not get it to work. Tried everything.

The AutoUpdater.exe does not work (and it is for major releases too). No log is created and nothing goes to the Event Viewer either.

As a workaround, I was able to bring down the entire Local Client (1.2GB) off the Application Server and it worked that way.

The call has been transferred to the MN office. At least I have a workaround, but a pain to download this off the Sever for each client.

I will report back to the root cause.

1 Like

Agree with Jose here. Our Pilot upgraded this weekend and the auto update brought it from .300 to .400 with no problems. We only had to do a new install when we went from 10.0.700 to 10.2.100 because they actually changed the installer.

On Prem usually it uses a version based deployment path:

So perhaps SaaS Customers have a more generic path like \SaaS##### and it picks it up? Even when I used to change this manually in my config, it starts AutoUpdate.exe but blows up with half files missing. Maybe they fixed it in 10.2?

This is what 10.2.400 looks like:

It’s https based and not a file share.

I finally got it working. I had to let ClientInstaller build the basic Client folder (which contains about a dozen or so files). Then, I had to manually create the shortcut and use these properties:

I had explicitly use the switch “/update” at the end of the target path.

ShortCut Properties:

Target: C:\Epicor\ERP10.2.400Client\Client\Epicor.exe “/Config=E102400LIVE.sysconfig” /update
Start In: C:\Epicor\ERP10.2.400Client\Client

I launch the shortcut and got this:

Then eventually it launch the AutoUpdater:

02AutoUpdate

Then it started transferring the files

03TranferringFiles