Epicor Clients wont Update

Hi,

Anyone else having issues where their user’s epicor clients wont update? Ive tried resrting the PC’s and reinstalling but wont update to latest version, keep getting version mismatch error.

For prod or pilot?

Prod

Here’s a KB Article that might help.

Client Server mismatch with Kinetic Public Cloud client

Pasted text below:

The Cloud environments are updated regularly and this error means that the appserver process on our servers is at a different version than the client. Go through the processes one at a time, and only proceed to the next process if the previous didn’t resolve the issue. After each process, try to log into the client to determine if the issue is resolved.

PROCESS 1:

  1. Right-click on your Epicor Shortcut and select Properties.
  2. Click on the Shortcut tab.
  3. Go to the end of the target line, press the SPACEBAR, and add /update to the end. For example, if your target line looked like:
    F:\epicor\ERP10.1MT\client\Epicor.exe /config=SaaS201.sysconfig

You would change it to:
F:\epicor\ERP10.1MT\client\Epicor.exe /config=SaaS201.sysconfig /update

  1. Click Ok.
  2. Try to launch the client again and an autoupdate should trigger.
  3. After the client update completes, enter your ERP credentials and try to log in.
    NOTE: remember to remove /update from step 3 as soon as the autoupdate starts running.

PROCESS 2:

  1. Right-click on your Epicor Shortcut and select Open File Location.
  2. Open the Config folder.
  3. Right-click the SaaSxxxx.sysconfig file and select Open With… > Notepad.
  4. Click on the Edit Menu, then select Find.
  5. Search for (without quotes) “customization name”.
  6. Remove all lines that begin with <customization name. For example, if your customizations block looks like one of the below labeled --BEFORE (example 1) and --BEFORE (example 2):

–BEFORE (example 1)

<customizations> <customization name="Update11240011" directoryName="Update" version="11.2.400.11" deploymentType="Zip" /> <customization name="MexicoCSF" directoryName="Update" version="11.2.400.11" deploymentType="Zip" /> </customizations>

–BEFORE (example 2)

<customizations> <customization name="Update11240011" directoryName="Update" version="11.2.400.11" deploymentType="Zip" /> </customizations>

You would change it to:

<customizations> </customizations>

  1. Save your changes.
  2. Try to launch the client again and an autoupdate should trigger.

PROCESS 3:
If the previous processes do not resolve the issue, please download the Cloud Client installer, reinstall the client for your system number, and try to log in afterward.

To manually install the appropriate Kinetic Cloud system/shortcuts for your environment:

  1. Launch an Internet browser and open https://download.epicorsaas.com.
  2. Enter your SiteID (account number) and press TAB.
    NOTE: the Kinetic homepage URLs are displayed and can be copied/used to log into your Kinetic Cloud environment with an Internet browser without the need to reinstall the legacy Kinetic client.
  3. When the appropriate Client Installer options are specified, click GET CLIENT INSTALLER and run that downloaded .exe on the workstation in question to reinstall the legacy Kinetic client.

PROCESS 4:
If the issue persists after completing the previous two processes, please update the EpicCare case letting the Support analyst know so they can assist with appropriate next steps.

2 Likes

When this happens to me, it usually means Epicor hasn’t finished doing the update properly on the sever and no matter what I do I still get the error. Usually fixed after a couple of hours. I see you are third party hosted, if forcing the client to update doesn’t fix the issue I think you should contact your host/provider, not Epicor.

2 Likes