Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Upgrade to 2015 fails ...
Microsoft Dynamics GP (Archived)

Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Hello,

I have a client who is on GP2013 SP1.  They are heavy FRx users and dissatisfied with Management Reporter for their version.  They wish to go to GP2015 and I am attempting to set up a test environment to ensure a smooth transaction.

I have created a new SQL instance, created the company and restored the backup.  However, I did the same on a non production server.  On that server I created the company and restored the same backup from this past Friday night.  I then installed GP2013R2 and upgraded the company to that version.  Next I installed GP2015 and proceeded to perform the upgrade.

The upgrade failed indicating problems with 3 tables,

Company has errors from a previous update.

The tables are

Account Current Summary Master       The table doesn't match definition, error 25

Account Summary History                    Same error

Payroll Year End Wage                          I resolved this by deleting table at database level

When I ran update again, it gave an explanation mark and said it was only a problem if table still exists.

I thought I could attach a Word Doc but apparently not.  Well that the gist of the issue.  Any thoughts ideas greatly appreciated.

thanks,

 

Phil Gilbert

*This post is locked for comments

  • Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

    That's fine if the tables are empty and they were re-created to get past an upgrade issue and yes, the lengths on the GL table columns will cause them to fail if not setup as per the account framework.

    At this point, is the upgrade completed, or what exactly are you seeing at this point?

    Thank you.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

    Richard,

    When I check HotFixes for GP 2015 R2, all I see is one date 09/21/15.  Is that okay, retroactive.

    thanks,

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

    Hey Derek,

    Thanks for the reply.  Deleting the Payroll Table was the recommended action suggested by the Upgrade procedure.  They had never had the Payroll installed.  The other 2 tables Account Summary Master and History... one of the staff accidentally changed an account segment from 2 in length to 4 the max  a few months back.  Other than screwing up FRx reporting nothing else seemed broke.  I wonder if that's the issue.  BTW, I'm via the Upgrade Path guideline.

    Thanks,

  • Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

    You must be on a minimum of 12.00.1482 for Dynamics GP 2013, to be able to upgrade to Dynamics GP 2015:

    mbs.microsoft.com/.../HOT_TOPIC_MDGP2015Upgrade

  • Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

    Hello Phil,

    The GL10110 and GL10111 which are the Acct Current Summary Master and Account Summary History tables, both get setup with a specific number of columns to correspond with the account framework, as you probably know.

    Because of this, these two tables may be failing the upgrade because the dictionary files haven't been synchronized with the account framework. For Dynamics GP 2015, in the Dex.ini file, try setting the SYNCHRONIZE=FALSE line to TRUE, then save changes and, after removing the failed records from the DU000030 table, launch GP 2015 Utilities again to see if these two tables still fail.

    Also, normally we don't want to delete a table to get past an upgrade error, especially if the table has data in it, obviously.

    The other thing I would say is, before starting the upgrade, did you verify the DU000030 table was completely empty? What can happen is that if there are records in this table from a prior upgrade, it can cause tables to get skipped during the upgrade process, so I recommend making sure the DU000030 table is empty before beginning any type of database upgrade.

    Thanks,

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

    Hey Richard.  I looked at the upgrade path which indicated that I could upgrade from GP2013 as long as I applied SP2.  I went back to GP2013, applied SP2 and now received this when attempting to upgrade to GP2015;  BTW, I am looking for hotfix... Thanks for reply.  

    Failure encountered ON 11/18/2015 at 7:51:28 AM.  Error:  Product 0 does not support upgrading from version 12.0.1412.

    Failure encountered ON 11/18/2015 at 7:51:28 AM.  Error:  Product 949 does not support upgrading from version 12.0.1376.

    Failure encountered ON 11/18/2015 at 7:51:28 AM.  Error:  Product 1493 does not support upgrading from version 12.0.1384.

    Failure encountered ON 11/18/2015 at 7:51:28 AM.  Error:  Product 2277 does not support upgrading from version 12.0.1385.

    Failure encountered ON 11/18/2015 at 7:51:28 AM.  Error:  Product 2992 does not support upgrading from version 12.0.1372.

    Failure encountered ON 11/18/2015 at 7:51:28 AM.  Error:  Product 0 does not support upgrading from version 12.0.1920.

    Failure encountered ON 11/18/2015 at 7:51:28 AM.  Error:  Product 0 does not support upgrading from version 12.0.1920.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

    Bill, from what I understand FRx is out of the question for GP2015.   The client is not satisfied with Managment Reporter 2012.  The Report Viewer created issues with Headers/titles not aligning and using a browser to print/view was not viable.  IE had issues printing a 2 page report that Chrome solved somewhat, however we still could not control output to a printer satisfactorily when using output to the browser, ie page breaks, repeating titles etc.

  • Bill Campbell Profile Picture
    Bill Campbell 22,647 on at
    RE: Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

    Phil is the purpose of the update to GP2015 to get to a newer version of Management Reporter?  or for some other purpose.  From the lead line to the case I almost believed you were dissatisfied with MR and wanted to move to get to a better FRx.

    That aside, I have seen a number of these types of errors and have lived with the blasted 'Yellow !' for a number of years.

    You are correct, seeing the does not mean the system will not work, it does imply that at some point you have a bad or missing table.  I have found in past that it is easy enough 'during the update' to remove the offending table from SQL and watch what the system does at that point.

    Of course all of this is being done on a TEST system and you are able to restore and dump the trashed system as needed.  Use the TEST system to learn how to solve the problem before you go live with the conversion.  You will still likely encounter error in LIVE, but at least now you will know what to do.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Upgrade to 2015 fails - Company has errors from previous update 2 tables do not match definition Error Code 25

    Have you tried going to GP 2015 R2 and use the July 2015 hot fix?

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans