Open Forum

Expand all | Collapse all

Upgrade from GP 2015 R2 to GP 2018 R2

  • 1.  Upgrade from GP 2015 R2 to GP 2018 R2

    Posted Nov 16, 2018 09:54 AM
    Hi everyone-

    Am testing the upgrade to GP 2018 R2. When I get to the portion of the company database upgrade, it is stopping on "Updating table Posting Definitions Master" every time. At first I thought it was just how GP Utilities stops responding sometimes when it is working away, but this has been sitting here for two days now.

    I have a dexsql.log running but I am not sure what is relevant to it just stopping.

    Is something going on with my upgrade or testing system? Am not sure where to begin to figure out why it is just hanging at this point.

    Thank you.

    Joseph Markovich
    IT Manager
    Okaya Electric America
    Valparaiso IN

  • 2.  RE: Upgrade from GP 2015 R2 to GP 2018 R2

    Posted Nov 16, 2018 01:35 PM
    Edited by Ven Sharma Nov 16, 2018 01:43 PM
      |   view attached

    Hello Joseph:

    MS upgrade guide included the below attachment-

    running the script on the dynamics database (or the named instance) would list out the exact table names that failed to convert.

    You may then look for those tables names in the dexsql.log file.
    It can even be a simple error such as transaction log file is full etc.

    Also, were you able to convert any other company successfully?

    I tried a test upgrade from GP 2010 SP1 to gp 2018r2 and most of the heavy lifting I did was to land the companies in GP 2015R2. There was a account framework validation script I had to run etc.

    I also remember running a bunch of other scripts that came with the upgrade guide.

    1. Check_workflow_status
    2. eConnect_out_Setup
    3. invalid_records_POTables
    4. Payroll work tables

    Good luck

    Ven Sharma
    Sr ERP Technical Analyst
    Long and Foster Companies
    Chantilly VA
    Dynamics Credentialed Professional


    Failed_Tables_List.txt   393B 1 version

  • 3.  RE: Upgrade from GP 2015 R2 to GP 2018 R2

    Posted Nov 19, 2018 09:12 AM
    The 'Posting Definitions Master' is the SY00500 table which receives a new 'CARDNAME' column in it and that has been what we've seen issues with when we see this table fail an upgrade, though it's not something we frequently see fail.

    What I would do is the following:

    A. Run the following script:
    Delete DYNAMICS..DU000030 where Status <> 0 and Status <> 15

    B. Start a dexsql.log and delete any prior dexsql.log files that may already exist:
    C. Launch Dynamics GP Utilities and continue the upgrade of this company database.

    When the upgrade fails again on this or any other errors, run the following script and look at any tables showing as having failed the upgrade and the error description:

    SELECT b.fileOSName, a.fileNumber, a.PRODID, a.Status, a.errornum, a.errordes, c.CMPANYID, c.INTERID
       FROM DYNAMICS.dbo.DU000030 a
       DYNAMICS.dbo.DU000010 b
       ON a.fileNumber = b.fileNumber
       AND a.PRODID = b.PRODID
       DYNAMICS.dbo.SY01500 c
       ON a.companyID = c.CMPANYID
       WHERE (a.Status <> 0 or a.errornum <> 0) and a.Status <>15

    Then, you can search the dexsql.log for SY00500 table and/or any other tables that are failing the upgrade for any errors related to the error description in the above 'failed tables' script.

    In the log file, you should see the SY00500 and its primary key get renamed, then a new, updated SY00500 table and primary key will be created, along with any indexes, triggers, dex procedures. Once the table updates successfully, you'll see a series of 'default bound to column' messages for each column in the table, then at that point it will attempt to take any data from the original table and put it into the newly updated table.

    If the structure of the SY00500 table is not correct going into the upgrade, you may not see a specific error in the log file, just that it hits something and rolls back the upgrade, however, the 'failed tables' script will usually state something like the table did not have proper structure prior to the conversion (upgrade) taking place.

    If you haven't already done so, a support case is easier to troubleshoot this type of issue when we can get into your environment with you and look at the table.


    Derek Albaugh
    Sr. Support Engineer
    Moorhead MN

  • 4.  RE: Upgrade from GP 2015 R2 to GP 2018 R2

    Posted Feb 11, 2019 12:33 AM
    I'm also in the process of upgrading from GP 2015 R2 to GP 2018 R2. I first saw that it hung on the "Updating table Posting Definitions Master" and found that it is important that all batches are posted in SY00500 (mkdtopst=0, and bchsttus=0). It still takes a great deal of time getting past the "Updating table Posting Definitions Master" section but eventually completes the upgrade.  Mine took about 6 hours.

    Jeff Roe
    Kele Inc
    Bartlett TN

  • 5.  RE: Upgrade from GP 2015 R2 to GP 2018 R2

    Posted Feb 12, 2019 11:26 AM
    I completely forgot about posting this discussion on here.

    The problem of the upgrade hanging wasn't anything to do with the Posting Definitions Master table (or GP at all) -- it was the next step: upgrading SOP30200. We have a SmartConnect trigger on that table since we sync all posted invoices/returns with D365. It was making our test SQL Server and test SmartConnect go BONKERS because of the changes to the records from the upgrade.

    Once the trigger was disabled, the upgrade proceeded normally. I have since added this step to my upgrade checklist.

    Sometimes it is the silliest things...


    Joseph C. Markovich
    IT Manager
    Okaya Electric America
    Valparaiso IN

  • 6.  RE: Upgrade from GP 2015 R2 to GP 2018 R2

    Posted Feb 21, 2019 12:22 PM
    I was finally successful with the GP2015 R2 upgrade to GP2018 R2.

    What I ended up finding is when the upgrade was at the point of doing an update on the SP30200 table is was creating a SQL block against itself. At times that would prevent that step from completing and the step would terminate. What I ended up doing is stopping and restarting the database server, which in turn cleans up the the tempdb database.

    At that point i then restarted the company upgrade and although I still some blocking with the update on the SOP30200 table it would eventually complete.

    With all that being said when the Posting master is showing, it will do so until the step that updates the SOP30200 table completes which in my case took around 4 hours.

    Jeff Roe
    Kele Inc
    Bartlett TN

If you've found this thread useful, dive deeper into User Group community content by role