Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
This is fixed in the 2015 Canadian Payroll Mid Year Tax Update released June 25, 2015. We do however recommend that you use the July Hotfix Round 2 Update (KB 3080334) that just released on July 23, 2015 going forward so you will not run into the issues below. Click HERE for the download.
Hello -Their are currently a few known upgrade issues that you may encounter when upgrading to Microsoft Dynamics GP 2015 R2:
ISSUE #1:You may encounter an issue with the ASIEXP86 table (SmartList Favorites Columns Master) when upgrading to Microsoft Dynamics GP 2015 R2: "The stored procedure SynchronizeTableData() of form duSQLAccountSynch : 27Pass Through SQL returned the following results: DBMS: 2601, Microsoft Dynamics GP: 0."
BEFORE UPGRADING TO MICROSOFT DYNAMICS GP 2015 R2: To identify whether or not you will encounter this issue, before upgrading, to Microsoft Dynamics GP 2015 R2, please run the following script against your DYNAMICS database:SELECT * FROM DYNAMICS..ASIEXP86 WHERE ASI_Field_Number NOT IN (SELECT ASI_Field_Number FROM DYNAMICS..ASITAB20)
ISSUE #2:You may encounter an issue with the SY07240 table (List View Action Pane) when upgrading to Microsoft Dynamics GP 2015 R2: Cannot insert the value NULL into column 'CmdSequence', table 'DYNAMICS.dbo.SY07240'; column does not allow nulls. INSERT fails.*/
BEFORE UPGRADING TO MICROSOFT DYNAMICS GP 2015 R2: To identify whether or not you will encounter this issue, before upgrading, to Microsoft Dynamics GP 2015 R2, please log into your current Microsoft Dynamics GP installation and verify that you see the Vendors Not Submitted list and Vendors Pending Approval list underneath of Vendors on the Purchasing page.
If the Vendors Not Submitted and Vendors Pending Approval lists are missing, please run the appropriate script based on what version of Microsoft Dynamics GP you are coming from. After that, go ahead and launch Microsoft Dynamics GP Utilities to proceed with your upgrade.Missing Vendor Nav List Fix - 2010.sqlMissing Vendor Nav List Fix - 2013.sqlMissing Vendor Nav List Fix - 2015.sqlIf you continue to run into an issue on the SY07240 table, please open up a support incident for further steps to proceed. In addition, please let us know the version of Microsoft Dynamics GP that you are upgrading from.
If those lists do appear, you can go ahead and proceed with your upgrade to Microsoft Dynamics GP 2015 R2.NOTE: Issue #2 will be resolved in the Microsoft Dynamics GP 2015 Canadian Payroll Mid-year Tax Update which is tentatively slated to release the week of June 22nd.
IF THE UPGRADE IS ALREADY IN THE FAILED STATE ON THE ASIEXP86 TABLE: If you have already attempted to upgrade to Microsoft Dynamics GP 2015 R2 and have ran into an error on the ASIEXP86 table in the System Database, you can perform the following steps:
1. Start a Dexsql.log file for Dynamics GP 2015 R2 and delete any other logs that may previously exist:How to create a Dexsql.log file to troubleshoot error messages in Microsoft Dynamics GP https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;850996
2. Launch Microsoft Dynamics GP 2015 R2 Utilities and begin the upgrade of the DYNAMICS system database.3. You will again encounter the same error on the ASIEXP86 table.
At that time, look in the dexsql.log file for the duplicate key, which will look something like this:
exec duAN_SynchronizeTable 'ASIEXP86','ASIEXP86_T','D'
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert duplicate key row in object 'dbo.ASIEXP86' with unique index 'AK2ASIEXP86'. The duplicate key value is (0, 5, 0, 0, , , */
Make note of the results.
4. If you get a duplicate index record error as referenced in Step 3 we need to remove all the records that begin with, in this example, 0, 5, 0, 0, which we can do by using a script such as this:
DELETE DYNAMICS..ASIEXP86 WHERE ASI_Favorite_Dict_ID = 0AND ASI_Favorite_Type = 5AND ASI_Favorite_Save_Level = 0AND CMPANYID = 0
5. Do this for any further duplicate errors that you encounter on the ASIEXP86 until you get past the 'Load Required Data' which is where the ASIEXP86 fails.
IF THE UPGRADE IS ALREADY IN THE FAILED STATE ON THE SY07240 TABLE:
If you have already attempted to upgrade to Microsoft Dynamics GP 2015 R2 and have ran into an error on the SY07240 table in the System Database, please close out of Microsoft Dynamics GP Utilities and restore the DYNAMICS database from prior to the Upgrade attempt to Microsoft Dynamics GP 2015 R2.
Then in SQL Server Management Studio, please run the appropriate script below based on what version of Microsoft Dynamics GP you are coming from. After that, go ahead and launch Microsoft Dynamics GP Utilities to proceed with your upgrade to Microsoft Dynamics GP 2015 R2.Missing Vendor Nav List Fix - 2010.sqlMissing Vendor Nav List Fix - 2013.sqlMissing Vendor Nav List Fix - 2015.sqlIf you continue to run into an issue on the SY07240 table during the upgrade, please open up a support incident for further steps to proceed. In addition, please let us know the version of Microsoft Dynamics GP that you are upgrading from. If you are enrolled in a support plan directly with Microsoft, you can enter a new support request to Microsoft Dynamics® Technical Support from Customer Source or Partner Source under Support >> New Support Request.UPDATE:
These issues have been resolved in the 2015 Canadian Payroll Mid Year Tax Update which was released on June 25, 2015. The recommendation however is to go to the July Hotfix Round 2 Update (KB 3080334) that just released on July 23, 2015.
Ran into this today. In my case, I was upgrading a test environment I had previously upgraded from GP 2013 SP2 > GP 2015 > GP 18.00.0404 several months ago months ago and then to 18.00.0439 a few months later. After each test, the server was shut down and nothing was entered, so nothing was changed before bringing it up to R2.
Hi again Beat,
Thought I should mention I have already logged it with GP support today
I had the exact same problem from GP 2016 to GP 2018 R2. The only temporary work around that I have found to push past this in my test upgrade was to work through deleting the duplicate keys in the DYNAMICS..ASIEXP86 as described in this post .
Business Applications communities