With the new release of Microsoft Dynamics GP 2015 R2, we do want to make sure we are sharing any known issues that we run into with the upgrade of the new release so that you can be the most prepared for your upgrade.
We do have great documentation on the known upgrade issues list in the Microsoft Dynamics GP 2015 Upgrade Manual. Please review our Upgrade Manual and Upgrade Hot Topic to prepare and make yourself aware of all known issues that may arise during your upgrade. We do continually update this information! Again, it is very important to review the known issues prior to upgrades as we have several pre-upgrade scripts for you to run. Along with reviewing the known issues prior to upgrade, it is always recommended to perform a test upgrade to insure that you will have minimal downtime when it comes time for your production upgrade.
We currently have the following known upgrade issues for Microsoft Dynamics GP 2015 R2 as of May, 2015:
1. Account Framework Table Conversion: We convert several tables that have account framework information in them. If the account framework tables in the company database, do not match the SY003001 and SY00302 tables in the DYNAMICS database, the upgrade will fail. Please run the Account_Framework_Validation.txt script from the Upgrade Guide to validate your tables prior to the upgrade. If results are returned, please work with your Partner or contact Technical Support to talk about the options for those tables. We do have other account framework tables that can be changed but these are a few of the main tables we look at when it comes to account framework. Here are the tables we convert:
GL10110
GL10111
GL70500
GL70501
GL00100
GL00201
IV70500
2. Microsoft Dynamics GP OLE Object Migration Utility: Currently is unavailable for GP 2015 but may be coming soon with the GP 2015 R2 release.
**This tool is provided for your convenience to assist in transferring OLE Notes over to Document Attach. Circumstances may be encountered in which this tool may not be able to convert all of your OLE Notes. In these scenarios, the notes that do not convert, will need to be manually attached in Document Attach.
3. Budget date records in Analytical Accounting: The AA Budget Tree Balance (AAG00904) table contains the records for each budget in Analytical Accounting. If there are budget date records in the AAG00904 table that do not exist in the aaDateSetup (AAG00500) table, the upgrade will fail and the following error occurs.
AAG00904 135 [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot insert the value NULL into column'YEAR1', table 'XXXX.dbo.AAG00904'; column does not allow nulls.UPDATE fails.
4. Database Compatibility: If you are moving to a new SQL Server in addition to the upgrade to Microsoft Dynamics GP 2015, you can restore your databases to the new SQL Server and start your upgrade. Please refer to KnowledgeBase Article 878449 for the steps to move to a new SQL Server. Once the databases are restored to the new SQL Server, you must change the database compatibility.
a. In the SQL Server Management Studio. right-click your database and click Properties.
b. Under Select a Page on the left, click Options.
c. Change the Compatibility Level to match the version of SQL Server you are running SQL 2012 = 110, SQL 2014 = 120.
5. Purchase Order Tables: If there are detail records in the POP10110 and the POP30110 that do not have a matching header record in the POP10100 and the POP30100, the upgrade may fail on those tables. Run the Invalid_Records_POTables.txt script from the Upgrade Guide to validate all detail records have a header record. If results are returned, you can either remove the detail records or run checklinks in the current version you are running.
6. Server Drop Down List Blank: When launching Microsoft Dynamics GP 2015, the Server drop down list may be blank. The Server drop down is the OBDC DSN that Microsoft Dynamics GP needs to connect to your SQL Server databases. If the ODBC DSN is an older version or an x64 DSN, it will not show up in the list. Please make sure you have a 32-bit ODBC DSN created using either the Native Client 10.0 or Native Client 11.0 driver. Click HERE for the steps to setup an ODBC DSN.
7.The U.S. Payroll Automatic Tax Engine: The U.S. Payroll Automatic Tax Engine does not work with Microsoft Dynamics GP 2015 RTM.
Click HERE to install a recent hotfix for a new tax engine.
8. Workflow Documents Must be Final Approved: If you use our Workflow for GL/PM/RM batches, Purchase Orders, Vendor Approvals, Credit Limit Overrides, Sales Quotes. Employee Onboarding, etc., all Workflow Documents must be final approved prior to the upgrade. No documents can be pending. The upgrade does check for this and will stop Utilities and provide a report showing what documents need to be approved.
9. Microsoft Dynamics Adapter Service: If you use the CRM Connector for Microsoft Dynamics GP and the Microsoft Dynamics Adapter Service is running on the server where you are performing the upgrade, please stop the service temporarily. Once the upgrade is complete, the Microsoft Dynamics Adapter Service can be restarted.
10. Professional Services Tools Library: If you receive an invalid version error on PSTL (Professional Service Tools Library) click HERE (Partner only) for an updated install. This is fixed in the January Hotfix, click HERE.
11. Microsoft Dynamics GP Utilities Stops Responding: When you launch Utilities for the upgrade, most of the processing is done on the SQL Server. If you happen to client away, Utilities may appear to stay white and show "not responding". Please do not close out of Utilities, the upgrade is still running. Please give the upgrade time to continue working. If you feel the upgrade is hanging or locked up, please start a SQL Server Profiler trace to review activity.
Please review the known issues above prior to your Microsoft Dynamics GP 2015 R2 upgrade! Going through the information will help alleviate any known issues that you may run into! Also, remember to always run a test upgrade first!
Continue to follow our Upgrade Blog Series! More blogs to come!
Thanks,
Lance