Brand new 10.2.500 app server installs the ICE 3.2 Client?

Epicor ERP 10
1

So after getting a shiny new 10.2.500 app server up and running for testing we noticed that running the E10Client.exe from the \\servername\ERP10.2.500.0Deployment\ClientInstaller folder installs the Epicor ICE 3.2 Client. Not the ERP 10.2 client we where expecting.

epicorice

Very confusing, it appears to work the same but is it? I see there are a couple of other posts about this but no real answers. and i have yet to hear back from Epicor about it on my support ticket.

Can anyone shed any light on whats going on here or am i doing something wrong? or have i missed some news about this somewhere

Thanks

1 Like
2

I noticed this going from 10.2.400.15 to 10.2.400.18 and had some issues, so I rolled back to 15. Would love to hear what you find out.

3

When I did a clean install of 10.2.400.2 (The initial public release I think) this did a similar thing; The client was ICE3.0Client. Patching to .8 and the client install became ERP10.2Client.

4

Epicor got back to me and this is their response .

Eric Tay 2020-01-24 19:57
Kieran, Ice 3.2 is the Framework, and 10.2 is the product. Hence it is alright if you are installing Ice 3.2.

Thank You
Regards,

Eric

Which obviously we all know. But this was marked as the solution on the ticket by Eric, so i guess we carry on…

5

They got back to me again over night and have told me they are looking into it again and will get back to me, so maybe there is more to this, will let you know what i hear back

6

They now acknowledge this is actually an issue and have created a problem ticket with the developer team

The plot thickens

7

We noticed the same thing after installing and deploying patch 10.2.400.19.

Before, when we were on 10.2.400.11, running the Client Installer E10Client.exe would say, “This executable will install Epicor 10.2 Client on your computer”. Now, it says “This executable will install Epicor ICE 3.2 Client on your computer.”

After the first screen, the rest of the installation process is identical as before. After install, a user clicks the Epicor shortcut and the same client files are downloaded from the server (as before).

As far as I understand, these two installers are exactly the same thing… perhaps updated verbiage would help: “This executable will install the Epicor ERP 10.2 Client (Epicor ICE 3.2) on your computer.”

The product running on the server is Epicor 10.2. The framework that runs on my desktop to interact with the product on the server is ICE 3.2 (as before).

8

Yes that’s what i think too, its just a naming thing, the actual software is the same and all i’m after from them is some confirmation on this.

But that seems to be asking a lot… :sweat_smile:

9

The same thing happened to us with 10.2.500.7. I called support and they confirmed by installing the client themselves and sent a screen shot with the ICE 3.2 Client verbiage.

10

Still happening on 10.2.500.11 between this and the Zeus verbiage for environment’s it certainly caused some confusion.

11

It’s supposed to. They even moved to the ICE 3.2 client in one of the recent 10.2.400 patches. We installed the .19 patch and I noticed the client had been updated to the ICE 3.2. We are running both right now. Any existing installs have the old client and new machine setups have the ICE 3.2. Has not caused any issues.

1 Like
12

I can’t the original post, but I believe either @Rich or @Bart_Elia confirmed that it was just a mistake in the build - should say Erp 10.2 rather than Ice 3.2. Nothing said above is incorrect, the Ice framework is 3.2.

I’m sure they will correct the confusing version numbers in the next update.

13

I missed that post. I could see why they called in ICE 3.2 client. ICE tools are there shared tools. They could be reusing the launcher between ERP and some other app.