web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

GP 2018 R2 upgrade failing with usual message about wrong version but that is not true

(0) ShareShare
ReportReport
Posted on by 75,852 Moderator

Well, here is something new. I am upgrading from GP 2013 to GP 2018 R2. I have finished the upgrade from GP 2013 to GP 2015 (14.00.0898). When I try to go to GP 2018 (18.00.0672) I get these messages. I have checked the DB_UPGRADE AND DU00020 tables and no records indicate version 12. Where is GP Utilities going to get these values and how do I correct this?

Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 0 does not support upgrading from version 12.0.2038.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 258 does not support upgrading from version 12.0.2014.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 949 does not support upgrading from version 12.0.1679.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 1042 does not support upgrading from version 12.0.1603.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 1235 does not support upgrading from version 12.0.1607.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 1493 does not support upgrading from version 12.0.1722.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 1632 does not support upgrading from version 12.0.1592.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 1878 does not support upgrading from version 12.0.1600.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 2277 does not support upgrading from version 12.0.1604.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 2416 does not support upgrading from version 12.0.1593.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 2547 does not support upgrading from version 12.0.1596.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 2992 does not support upgrading from version 12.0.1748.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 3104 does not support upgrading from version 12.0.1591.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 3278 does not support upgrading from version 12.0.1605.
Failure encountered ON 8/27/2019 at 12:16:47 AM.  Error:  Product 5597 does not support upgrading from version 12.0.1597.

*This post is locked for comments

I have the same question (0)
  • RJarrell Profile Picture
    321 on at

    Have you tried this? www.ktlsolutions.com/.../

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    Yes, this is the opposite of the issue I have. The companies with the wrong version do not even exist. After reviewing their SY01500 table I noticed that two companies had been removed via SSMS and not through GP. I ran the clear company script and the upgrade is proceeding normally. I just cannot explain how the upgrade was getting these version numbers since none of the existing nor missing companies had version 12 any more.

  • Derek Albaugh Profile Picture
    Microsoft Employee on at

    Hello Richard,

    Looking at the error > Product 0 does not support upgrading from version 12.0.2038, and the fact you mentioned you've just finished the upgrade from GP 2013 to GP 2015, it would appear that you have a database(s) that are still at the GP 2013 version, whether a database(s) that failed to upgrade or was decided wasn't needed to upgrade, but most likely at least one database is still showing as 12.0.2038.

    Because there isn't a direct upgrade path from GP 2013 to GP 2018, this is why you're getting this version error when launching GP 2018 Utilities.

    You can use a script like this, run against your DYNAMICS/system database, to find the database(s) causing the issue:

        Select * from DB_Upgrade where PRODID = 0

    Let us know if this doesn't resolve the issue.

    Thank you,

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    Derek, this is the really odd issue here. All records in the DB_Upgrade and DU00020 indicated that the upgrade to GP 2015 was complete. DB_Upgrade.db_verMajor were all 14 as well as DU000020.versionMajor.

    I did notice that in SY01500 there were two companies that no longer had a corresponding database. I ran the ClearCompany script and the upgrade completed with no issues. There must have been something in another table from where utilities pulled the version 12 numbers.

  • Derek Albaugh Profile Picture
    Microsoft Employee on at

    That is interesting. Usually, when there are database records in the SY01500 that Utilities can't find in the DB_Upgrade/DU000020 and/or the database doesn't exist physically, Utilities will just hang, as it can't find the information.

    I don't know that I've ever seen it say a 12.0 version, when it didn't actually show it in one of the two system tables mentioned.

    Good job figuring out that one.

    Have a great day.

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    Derek, this was an oldie but goodie.  Born in GPA for DOS and migrated to GP 7.5 Btrieve and then to MSSQL. So who knows what was in there.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Dan Liebl Profile Picture

Dan Liebl 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans