Hopefully, at this point, you’ve looked at our prior Dynamics GP 2013 R2 Upgrade blogs that have been released beginning April 29th, 2014:

--Lifecycle blog

--Upgrade Planning

--Known Upgrade issues

--Version Checks and Upgrades

If you haven’t already looked through these prior blogs, I would highly recommend it.

I would also recommend looking at the 'System Requirements for Microsoft Dynamics GP 2013' page and the ‘Upgrading to Microsoft Dynamics GP 2013’ hot topic as well, on both PartnerSource and CustomerSource, if you haven’t already done so, as these will be updated with the Dynamics GP 2013 R2 information.


Microsoft Dynamics GP 2013 Product Download Page / new Dynamics GP 2013 R2 DVD:




Microsoft Dynamics GP 2013 Service Pack Page








Database Upgrade - The Basics!

The upgrade to Microsoft Dynamics GP 2013 R2 is the same upgrade process that we’ve had in prior versions, in that the database upgrade does take place in Microsoft Dynamics GP Utilities.  The Upgrade Manual outlines the step-by-step process for the upgrade.  Here are the basics...

  1. Setup your test environment to test out the upgrade first.

       2. Review the Upgrade Manual and Upgrade Hot Topic for the latest Known Issues and Pre-Upgrade Scripts.

       3. Backup your existing DYNAMICS/system database and all company databases.

       4. Verify you are on the correct version/build of your current Microsoft Dynamics GP environment in order to upgrade to Microsoft Dynamics GP 2013 R2. 

           **Note: The minimum versions for Microsoft Dynamics GP 10.0, GP 2010 and GP 2013 aren’t released at this time. This blog will be updated with this information as soon as it is released.

       5. Obtain all the code and installs for your integrating products.

       6. Download the latest DVD for Microsoft Dynamics GP 2013 R2.

       7. Install Microsoft Dynamics GP 2013 R2 from the DVD to include all modules that you currently have installed on your current version of Dynamics GP 2010 or GP 10.0.


           If you’re currently already on Dynamics GP 2013 at a pre-R2 version/build, you’ll need to install the Dynamics GP 2013 R2 patch to update your current Dynamics GP 2013 system.  Refer to the Service Pack/Hotfix Download Page for Microsoft Dynamics GP 2013 for the R2 patch. 

      8. Launch Microsoft Dynamics GP 2013 R2 Utilities and after the version check, it’ll detect that you have databases that need to be upgraded. Click Next through the wizard to first upgrade your DYNAMICS/system database and then select to upgrade all company databases, as needed.

     9. When the Additional Tasks Window appears, the database upgrade is complete and successful.  If the Upgrade Company Window returns your company with a Red X, troubleshooting must take place.  Stay Tuned for the ‘Modified Dictionary Upgrade’ being released on May 15th, 2014 for information on upgrading your modified forms and modified reports.


Database Upgrade Tables

1. DU000010

The DU000010 table in the DYNAMICS database is the ‘Utilities Update Files’ table. This table contains a list of all tables that must be upgraded. Microsoft Dynamics GP Utilities uses these records and the versions on each record to know what tables get upgraded when you’re going from one version or build of Microsoft Dynamics GP to another.

2. DB_Upgrade

The DB_Upgrade table is also held in the DYNAMICS database and is the first table looked at when you launch Microsoft Dynamics GP Utilities. This is the main version table reviewed during the version check process discussed in the previous blog.  Once the upgrade begins, Utilities will change the db_verMajor, db_verMinor and db_verBuild to the new version that you’re upgrading to. Not all products have the same version/build number. The db_status column in the DB_Upgrade table will also change as the upgrade of the database processes. It begins at zero and increases along with each database upgrade step. A db_status of 23 is at the table conversion process for that database.  When Utilities has finished the database upgrade process and the entire process is successful, the db_status is set back to zero.  The db_verOldMajor, db_verOldMinor and db_verOldBuild values are also set to match those of the db_verMajor, db_verMinor and db_verBuild for each product when the database upgrade process is complete and successful. 

3. DU000020

The DU000020 table is another table that holds the versions of each feature/product installed for each database.  The versions in the DU000020 will remain at the previous release until all tables in the database are upgraded successfully.  When a user launching into Microsoft Dynamics GP following the upgrade, the version in the DU000020 is checked similar to how Microsoft Dynamics GP 2010 Utilities checks the version in the DB_Upgrade table.

4. duLCK

The duLCK table is used by Utilities to put a lock on a database while it is being upgraded. This prevents users from logging into the company database during the upgrade process. Once Utilities has finished the upgrade of the database, it will remove the record thus releasing the lock on the database. If Utilities is shut down or closed improperly, for example if the machine reboots or through Task Manager, this record may still remain in the duLCK table and when you re-launch Utilities, there will be a lock icon next to the database, so you won’t be able to select it in order to upgrade until you close Utilities and delete the record(s) in the duLCK table.

5. DU000030

Lastly, is the DU000030 table or ‘Utilities Fail List’ table. When Utilities starts upgrading the tables within the database, it looks at the DU000010 table, as mentioned previously, to see what tables get upgraded.  For every table upgraded, a record is inserted into the DU000030 table with a Status for the upgrade.  The ‘Status’ column shows which tables failed the upgrade and which tables were successful.  Some common statuses that are seen in this table are:

0 - The conversion ran to completion without error
2 - The table being converted or deleted was not found
15 - The table was already converted since the table’s structure matches the destination table definition.
25 - The path to the table could not be determined
70 - Script Error. An error occurred while running a script
135 - An error occurred and the table was renamed back to its original name and it contains the original data

**Note: The 'Microsoft Dynamics GP 2013 R2 - Upgrade Troubleshooting’ blog released on May 20th, 2014, discusses more on what to do when tables fail!


Server VS. Client - Where Should you Upgrade? 

You can launch Microsoft Dynamics GP 2013 R2 Utilities for the upgrade from the server or any workstation.  You are not required to install Microsoft Dynamics GP 2013 R2 at the SQL Server.  The upgrade can be launched from a client if you choose to keep the SQL Server clean of all application installs.  The only difference may be just a slight slowdown as we talk back and forth between the SQL Server and the workstation.  This does not add much overhead however. 

Upgrading all companies at once or one at a time?

Upgrading all companies at the same time or one at a time doesn’t make much of a difference as far as Utilities is concerned, it will upgrade the databases in the same manner regardless.  If you choose to upgrade all company databases at the same time, which is the default setting in the ‘Update these companies?’ window, Utilities will run through all company database’s upgrade process, one after the other, and won’t stop until either all company databases are upgraded successfully or an error occurs on one of the company databases.

If you choose to upgrade one company database at a time, Utilities will upgrade that company database and then once it completes successfully, it will go back to the ‘Additional Tasks’ window in Microsoft Dynamics GP Utilities and you would need to close Utilities and re-launch it in order to upgrade the remaining company databases. If the company database has an upgrade error that will show just like if you selected all companies to upgrade at the same time. Usually, only upgrading one company database at a time is used more during troubleshooting of a specific upgrade error in the company database, but again, there isn’t any repercussions of doing the upgrade in this manner, other than you must close and re-launch Utilities for each company database upgrade if choosing one company at a time.


VIDEO!!  VIDEO!!! Check out the walk through demo video of the Microsoft Dynamics GP 2013 upgrade!!

Continue to check back with our Microsoft Dynamics GP 2013 R2 Upgrade Blog Series Schedule to learn more about the Microsoft Dynamics GP 2013 R2 Upgrade!

Happy Upgrading!!!