10.2.600 sysconfig Inconsistencies

Epicor ERP 10
, ,
1

Before I submit a ticket to Epicor wanted to see if anyone else is seeing this. Or has seen this in the past. New deployment of ERP 10.2.600 on new app servers. The .sysconfig file version value differs between environments. Which prevents users from having both PROD and Test/Dev open at the same time. And causes the AutoUpdate to run when they switch between environments.

PROD

<ProductID value="Epicor" />
<Version value="10.2.600.0" />

TEST

<ProductID value="Epicor" />
<Version value="3.2.600.1" />
2

That rings a bell.

I can’t find anything other than the “10.x.yyy.zz” format in any of my sysconfig files. But I’m pretty sure that’s been mentioned here before.

3

I searched around here too as I thought it had been talked about. But wasn’t finding anything. It’s a simple fix but seems like a bug. On new deployments I would think it would get set to the same value. Doesn’t make sense why it wouldn’t.

4

Well, I did find one sysconfig file that doesn’t specify the proper version …

image
image766Ă—309 7.4 KB

We’ve NEVER had version 9. Went straight from 8.03 to 10.1.400. and that was on a different server. The App server that this sysconfig file points to has only ever had 10.2.300. As shown by a later part of the sysconfig file:

image
image704Ă—179 4.33 KB

5

Hmmm… similar. It’s weird that on brand new deployments it’s inconsistent. I could see through an upgrade or if the deployment server was different. But new servers and same deployment URL. You’d think they’d be the same. Wonder if there is something else I’m missing here :thinking:

6

Have you redeployed the Test app after running whatever updates / builds might have been done?

What shows as the version for Test in EAC?

7

That 3.2.600.1 looks like an ICE version number. I remember in the earlier releases of 10, there were some naming issues with the directory where the Epicor client was installed – it would name the directory ICE3.x.yyy instead of ERP10.x.yyy – but these were resolved in 10.2 I believe.

Can’t say I have any other ideas for why the same deployment would have an ICE version in one environment, but maybe that points you in the right direction.

8

I remember that too and ran into that myself. It does seem that’s what happened here. For one of the deployments anyway.

9

I have not. All four environments where installed as base 600 then updated to .16. The database of all of them were copies of our 10.2.400 and upgraded to 600 via EAC.

PROD
image

TEST
image

10

Do you have the Client versions in two completely separate folders under c:\Epicor?

IIRC, when the client starts, it looks into the .sysconfig in the deployment folder and compares the version in the < customizations > area and if different then does an update.

  <customizations>
    <customization name="ERP10.2.500.22" directoryName="Update" version="10.2.500.22" deploymentType="Zip" />
  </customizations>
11

Ah ha! I think that’s the problem! It looks like the .16 update wasn’t added to our custom in test. Whoops :grimacing:

PROD

      <customizations>
    <customization name="MetalcraftSerials" directoryName="MC" version="10.2.600.16" deploymentType="ZIP" />
    <customization name="ERP10.2.600.16" directoryName="Update" version="10.2.600.16" deploymentType="ZIP" />
  </customizations>

TEST

      <customizations>
        <customization name="MetalcraftSerials" directoryName="MC" version="10.2.600.10" deploymentType="ZIP" />
        <customization name="ERP10.2.600.16" directoryName="Update" version="10.2.600.16" deploymentType="ZIP" />
      </customizations>
12

As @Mark_Wonsil asks, I would suggest having the client installed in separate directories within C:\Epicor. That way, you can be testing a different version than your live system without constantly having to auto update to a newer/older version.

13

We do… C:\Epicor<version><enviroment>

That also allows me to deploy new versions of different environments.

14

I remember @Rich mentioning something about it just being the GA Version.

1 Like