2015 R2 upgrade path discoveries

(1) Share

Report

Posted on by Tom Cruse

1,477

Has anyone been able to upgrade to 2015 R2 from 2013 SP2?

We currently have our PROD environment on 2013 SP2 and a DEV environment on 2013 R2 for test purposes. We wanted to jump up to 2015 R2 and skip 2013 R2 and 2015 all together for our PROD environment. Here's what we did:

1. Create a new company in the DEV environment (2013 R2) as a shell and then restored a backup of PROD over this company, yes this would basically step the company down from 2013 R2 to 2013 SP2.

2. Install 2015 R2 and upgrade all companies in the db.

This is where I ran into a lot of problems with the newly created company because it was still on 2013 SP2. Numerous workflow tables were not found, all WF....... tables, StoredProcs could not be created due to missing columns that pertained to Workflow Status and a few new tables in the POP module for requisitions like the POP10200, POP10210, POP30200, and the POP30210. Again basically all of these were newly added in 2013 R2 because of the added functionality that GP brought inside the application with Workflows.

From what I can tell, to get to 2015 R2 will require a 2-step upgrade, first to 2013 R2 and then to 2015 R2.

In case you were wondering, the company that was already on 2013 R2 upgraded without a problem to 2015 R2. All the literature I find states that you only need 2013 SP2 to upgrade directly to 2015 but nothing is mentioned about 2015 R2.

*This post is locked for comments

All responses (5)

Answers (0)

Suggested answer

Ian Grieve 22,784 on at

Like (0)

Report

RE: 2015 R2 upgrade path discoveries

I have just done a test upgrade for a client moving directly from 2013 SP2 to 2015 R2 + hotfix; apart from an issue with the HR tables (this client does not have HR installed), the upgrade went through without a problem.
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

RE: 2015 R2 upgrade path discoveries

Just for the record I upgraded GP 2013 SP2 to GP 2015 R2 Year-End by going from 12.00.1482 to 12.00.1745 and then directly to 14.00.0898. So that was GP 2013 SP2 to GP 2013 R2 and then directly to GP 2015 R2 Year-End.
Tom Cruse 1,477 on at

Like (0)

Report

RE: 2015 R2 upgrade path discoveries

Beat thanks for the info, I was able to get the upgrade to work properly from 2013 R2 to 2015 R2 without a problem.

I did use the full DVD setup, it's possible I made a mistake upgrading the 2013 SP2 directly to 2015 R2, I made so many first attempts I forgot what I did :)

My main problem were the discrepancies between my PROD Environment being 2013 SP2 and my DEV Environment being 2013 R2, I wanted to take DEV straight to 2015 R2 but the data in DEV was really old so I needed something meaningful so here's what I did, plus I wanted a new test company too in DEV, long story but we have a prod and test company in PROD with some custom triggers and stor procs and I wanted DEV to properly mirror this setup ,that way my restore wasn't writing over a company in DEV that I had already established.

Get ready, this one is kind of a tongue twister :)

1. Create new company in DEV to match the setup in PROD

2. restore PROD company (2013 SP2) to DEV new company (2013 R2)

3. This over-wrote the version so I changed the DBUpgrade table versions for that company back to match the PROD servers company version.

4. Run GP Utilities to properly upgrade my newly restored company up to 2013 R2

5. Install GP 2015 R2

6. Upgrade all companies

7. Boom! DEV matches PROD but has been upgraded to 2015 R2.
Suggested answer

coquisalsa 2,725 on at

Like (1)

Report

RE: 2015 R2 upgrade path discoveries

You should be able to upgrade directly from GP2013 SP2 or GP 2013 R2 to GP 2015 R2, though there are known issues with the GP 2015 R2 installer.

Try this:

1) Install GP 2015 R2 (14.00.0725)

2) Install KB3066933 (14.00.0778)

3) Upgrade the databases. Only Upgrade the DBs after you complete the previous 2 steps
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (1)

Report

RE: 2015 R2 upgrade path discoveries

Hi Tom,

I did the upgrade from 2010R2 directly to 2013R2 and then upgraded to 2015 RTM. I'm in the process of applying the R2 July release..

The only issues I had in my first upgrade step was with the SLB and Extender tools, from which I had to get some scripts from eOne to fix issues about missing tables and other SQL objects.

I guess that MS did not include some of the WF objects in full with the R2 upgrade (BTW, did you use the full DVD setup of R2 or only the July SP?).