Property Mismatch in Live after dot release update on Test

Epicor ERP 10
1

We have a single VM server with Live, Pilot, and Test. Live is running 10.2.400.11. Last week I updated Test to 10.2.400.15.

After the upgrade, anyone who opens Test (and thus runs the .15 auto update), then goes back to Live (and thus runs the .11 auto update), gets a “property mismatch” error when trying to open a purchase order.

The only fix that I can find is to complete remove Epicor from the client (clear program data didn’t fix), then just run the installer again and only open Live. This makes the property mismatch error go away (unless they open Test).

I was under the impression that I could install dot releases on our Test environment without any cause for concern in our Live environment.

Thoughts / Advice?

Capture

2

To get around this, you could install the Client to another location on the workstation, and only create the links to the Test App.

I have client installs at:
c:\epicor\ERP10.2Client_PRD
c:\epicor\ERP10.2Client_TST
c:\epicor\ERP10.2Client_UAT

For example, the shortcut for the Production App has

  • Target: C:\Epicor\ERP10.2Client_PRD\Client\Epicor.exe /config=PRD_102300.sysconfig
  • StartIn: c:\Epicor\ERP10.2Client_PRD\Client\

While, the shortcut for the UAT App has

  • Target: C:\Epicor\ERP10.2Client_UAT\Client\Epicor.exe /config=UAT_102300.sysconfig
  • StartIn: c:\Epicor\ERP10.2Client_UAT\Client\
3

This is where I was planning on going… the nice thing about the separation is that both versions can be open side by side without conflict.

Any downsides to this strategy though?

4

Besides the extra steps for managing the client installs, not really.

Now If Epicor would just make alternate Icons, so the shortcuts would stand apart.

One last thing. Make sure you tweak the theme in the Test environment, so that folks dont wast time doing real work in it.

1 Like