Upgrade warning-10.2.600

[Townes69 (Anthony Townes)]

This was the most common error

[Aaron_Moreng]

That’s related to CRM configuration of the tasks, nothing to do with infrastructure

[Doug.C (Doug Crabtree)]

You guys are really making me think I’m going to wait until 10.2.700 to upgrade. Seems like there has been quite a few issues.

[Aaron_Moreng]

Haha don’t not upgrade on my account, I could just have performed the worlds worst upgrade from 10.2.200 to 10.2.600

[Arul (Arul Shankar)]

Please check the CRM Task setup. Most likely Epicor would have added a validation.

[knash (Ken Nash)]

External BAQs break in .8 and .9. You can only run the External BAQ if you are the owner or security manager.

Upgrade from 10.2.200 to 10.2.600 dashboards with external BAQ not working

Good Morning, We upgraded from 10.2.200 to 10.2.600. Everything is working except for one major thing. IT folks can run external baq dashboards and see results. Users cannot; they open the dashboard and the grid is blank. IT opens the dashboard, get the retrieving data, and data appears. We had User log in on ITs machine and get the same results. Must be a security issue. Is there a new user config setting to allow them to se external BAQs.

[Aaron_Moreng]

Getting this on a non-External BAQ as well. I changed the author from someone else to me to make an edit and cannot change it back with the same error. I am security manager level so if I can’t do it, I am sure no one else can

[jgiese.wci (Joshua Giese)]

@Doug.C

You guys are really making me think I’m going to wait until 10.2.700 to upgrade

Overall it’s not bad. I would let 700 bake a bit though before going to it. 600 has enough time under its belt that even a heavily customized place like ours it was very manageable.

[hkeric.wci (Haso Keric)]

Make sure you go to atleast .10 - had some other minor bugs that, make now sense (with MES).

[Bridget_Casey1 (Bridget Casey)]

@kfierce Were you able to resolve the 404 error when trying to print, We are currently in the middle of upgrading to 10.2.600.9 and are seeing the same behavior.

[kfierce (Kristine Fierce)]

@Bridget_Casey1 - happy we connected over the weekend. Good luck on your work week.

[Bridget_Casey1 (Bridget Casey)]

Hello all,

We went live on 10.2.600.9 over the weekend. We have ran into a couple of issues.

The biggest issue is when printing ANY SSRS report whether it was standard or custom it would intermittently fail with an error of RunTask:
System.Net.WebException: The request failed with HTTP status 404: Not Found.

In our test database we did not see this error and I think it is because we went from 10.2.300 to 10.2.600.5 and then put the .9 patch in last week and no issues. Over go live weekend we upgraded our database from 10.2.300 straight to 10.2.600.9.

@kfierce solved a similar issue with 10.2.600.9 by shutting off kinetic before ever seeing the HTTP status 404: Not Found error.

To resolved our issue we backed up the test database that no users were in yet and moved it to prod and immediately shut kinetic off before seeing the HTTP status 404: Not Found.

A couple of small things to also be aware of.

1. Our payment methods for AR were no longer connected to our bank accounts.
2. Attachments have been moved out of company maintenance and now have their own table. This change does not allow users to attach documents without having a document type selected unless you set up an attachment type maintenance like below.
   
   

Thank you @kfierce for your help this weekend!
Hope this helps!

[pwilliams (Paul Williams)]

The problem is that your .net framework did not update to 4.8. if you look at your web config file. search for supportedruntime, you will see the SKU will reference 4.0. This is not correct. it should be 4.8. This seems to be an issue with the upgrades. Epicor support couldn’t tell me how to prevent the issue. To resolve, you will have to remove the old Application Server and create a new one with the exact same name. I have down this a few times and it only takes 10-15 minutes for my application server (no Epicor extensions, just SSRS).

Backup and CSG files, custom reports, etc.

• Remove asp.net web pool
• Remove web directory
• Remove from Local Clients

[hkeric.wci (Haso Keric)]

@pwilliams

you will have to remove the old Application Server and create a new one with the exact same name

You should always do this for any non-patch level upgrades:

1. 10.2.300 to 10.2.400
2. 10.1.500 to 10.2.200

The only time I dont do it is for patch level 300.15 to 300.27.

10.2.400 New Install Gotcha's

Just Reminding Everyone when you upgrade from a older version to a major version it is best you not just upgrade your AppServer but DELETE it then Add a New AppServer with the same old settings. Its recommended in the Upgrade Guide but kind of not so clearly stated. Remove AppServer from Admin Console Via IIS Management, Remove the Application then the App Pool Delete your IIS Directory Example C:\inetpub\E10_Demo Delete the LocalClient from Example C:\Epicor\LocalClients\E10_Demo Then a new …

[ckrusen (Calvin Krusen)]

How does one install the new version for testing on the same server?

Say I currently have 2 Apps (both 10.2.300) on my production server\\App01. They are PRD_102300 and TST_102300. SQL is in a different server, \\SQL01. DB’s are also names PRD_102300 and TST_102300. And we’re upgrading to 10.2.600.

My plan would have been to:

• Install 10.2.600 on \\App01
• Duplicate DB PRD_102300 as TST_102600 (Notice the number change)
• Update DB TST_102600
• Create App PRD_102600 on \\App01, pointing to TST_102600

After testing was complete, the real upgrade would be to copy PRD_102300 to PRD_102600, and then redo the steps that I did to get PRD_102600 running with DB TST_102600.

But it sounds like 10.2.600 doesn’t want to run if and earlier version is installed. So how to test the version while keeping the current version running?

[hkeric.wci (Haso Keric)]

Just make a new instance

I have like 23 instances.

1. Copy PRD_102300 SQL Database to TST_102600 SQL
2. Register the Database TST_102600 in Admin Console (when you do this it should ask you which snap-in version you want)
3. Upgrade TST_102600 via Admin Console (Database Node still)
4. Add New AppServer TST_102600 and point it to DB TST_102600 (this will also ask you which snap-in version you want)
5. Login and it’ll ask you to run Conversion Workbench, do it
6. Setup Task Agent stuff… etc done.

[ckrusen (Calvin Krusen)]

So if you create a new App server for 10.2.600 (with a different App name), then previous posts about having to remove the prior version don’t apply?

It’s only when trying to upgrade an App that was originally created with a prior version?

[chaddb (Chadd Blanchard)]

I may have taken the wrong approach for our .600 upgrade but I spun up new servers (VMs) for it. Here’s how I got our .600 test/dev environments going. This worked fairly well. There were a few little bumps in the road but I figured those out. When it’s time to the PROD .400 to .600 I would do the same thing.

1. Installed .600 RL on new VMs
2. Copied our PROD .400 dB to a new .600 DEV dB
3. Added the new .600 DEV dB to the EAC
4. Ran the dB upgrade to get the dB up to .600
5. Add a new app server and deployed a .600 DEV app
6. Ran the conversion workbench to go from .600 to 600.10

[hmwillett (Hannah Willett 🏳️‍🌈⚧)]

@Aaron_Moreng

User Process Wrapper
I mistakenly ran the Conversion Workbench prior to installing UserProcessWrapper. I am not sure if the recompile step or the conversion workbench did, but what this did was it deleted any BPMs tied to that BO.
I had to restore a backup of the db from the night before into a new 10.2.200.3 (old version) environment to export those BPMs out and back into the upgraded environment.

Damn. Wish I saw this 28 days ago, lol.
Nuked ours too.

[Aaron_Moreng]

At least it’s not just me