Error upgrading from GP2016 to GP18.2 - Product does not support upgrading on all products..

(0) Share

Report

Posted on by abutler1986

677

Hi All,

I have just upgraded to GP2016 and transferred the databases over to the destination server, changed the DB owner of them all and compatibility level and ran grant against them all. Gone into Utilities in GP18.2 but getting the below.. it seems to be thinking that all the products are on version 12 when I look at the DB_UPGRADE db though under Dynamics there is versions 16?

Tried re-installing GP18.2 but still getting the below, any ideas?

Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 0 does not support upgrading from version 12.0.2230.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 309 does not support upgrading from version 12.0.2187.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 949 does not support upgrading from version 12.0.1679.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 1042 does not support upgrading from version 12.0.1603.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 1058 does not support upgrading from version 12.0.1717.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 1493 does not support upgrading from version 12.0.1722.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 1632 does not support upgrading from version 12.0.1592.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 1878 does not support upgrading from version 12.0.1600.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 2277 does not support upgrading from version 12.0.1604.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 2416 does not support upgrading from version 12.0.1593.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 2547 does not support upgrading from version 12.0.1596.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 2992 does not support upgrading from version 12.0.1748.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 3096 does not support upgrading from version 12.0.1717.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 3104 does not support upgrading from version 12.0.1591.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 3278 does not support upgrading from version 12.0.1605.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 5597 does not support upgrading from version 12.0.1597.
Failure encountered ON 12/04/2020 at 10:03:20 . Error: Product 8811 does not support upgrading from version 12.0.1717.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (6)

Answers (1)

Richard Wheeler 75,848 Moderator on at

Like (1)

Report

You need to on at least

16.00.0716 or later

Mid-Year

KB4099098

to upgrade to GP 18.2. You will need to rollback your data and apply the GP 2016 service pack first to get to 16.00.0716. If you look in [DYNAMICS].[dbo].[DU000020] you will see where you were.

Was this reply helpful? Yes No
Suggested answer

Justin Sutton on at

Like (1)

Report

Richard is spot on, you will want to make sure you are on a supported path to 18.2.

These can all be found here: https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGPUpgrade

You will also want to make sure that you are able to Run the GP 2016 Utilities without issues before you move on to GP 2018. This should point you to where the issue is occurring as sometimes issues crop up in the first jump.

If you are on a supported path, make sure to grab the following data:

Select * from Dynamics..DB_Upgrade

Select * from Dynamics..DU000020 order by companyID

These are going to help you figure out what version everything is.

Let us know if you have any questions or concerns.

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report

This looks really weird..

You say you just upgraded to GP 2016, but the error messages are about a GP 2013R2 product list.. kind of the feeling it's trying to upgrade a company that might not exist anymore.

You may want to run the 'clearcompany' SQL script against your GP instance to get rid of all ghost entries left over by old GP companies (which might have been TEST companies).

Was this reply helpful? Yes No
Verified answer

abutler1986 677 on at

Like (1)

Report

Thanks for the advice all. It turns out one of the 51 companies I was upgrading had some issues in the DB_UPGRADE table where it still referenced major version 12 instead of 16 like the other 50 companies. I took a gamble and modified the versions manually to match the same versions as the other ones, after I did this it then worked and everything updated to GP18.2 successfully. Very bazaar!

Regards,

Was this reply helpful? Yes No
Justin Sutton on at

Like (1)

Report

Great to hear you were able to make progress!

We normally wouldn't recommend making version changes manually, but normal testing will usually bring up any errors that this would cause. For example, you would get Table or Column Not Found errors throughout GP when using any functionality that was changed between the versions.

If you really want to make sure its working, go through the article below and just test using the new functionality. If you don't get any errors you are probably fine, what an odd one!

docs.microsoft.com/.../version-october-2019

Just as a note, make note of the company that had this problem, and keep it somewhere for the new few upgrades. This way you know that this company needs reviewed special if its upgrade fails.

Have a happy, and healthy, day!

Edit: I marked your post as the answer, since you figured it all out

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report

great to hear!

make sure you have that many companies in your system.. sometimes customers get the Fabrikam installed by the partner during initial setup, later then delete it, but some traces remain in some system tables that could lead to the issue you ran into.

Did you make a note about the company DBName that was referenced the DB_Upgrade table ? have you checked which company it was in the SY01500 table ? IF you can't find a match, you should still run the "ClearCompany" script to remove any references to that ghost company.

You could use this script :

SELECT DB_Upgrade.db_name, SY01500.CMPANYID, SY01500.CMPNYNAM
FROM DB_Upgrade LEFT OUTER JOIN
SY01500 ON DB_Upgrade.db_name = SY01500.INTERID
GROUP BY DB_Upgrade.db_name, SY01500.CMPANYID, SY01500.CMPNYNAM
HAVING (SY01500.CMPANYID IS NULL)

Leave out the last line if you want all lines returned. The above query should return at least 1 row: your DYNAMICS system DB, but this is normal as it's not part of the company table. Anything else would be suspicious.

Was this reply helpful? Yes No