Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Blogs / Dynamics GP Support and Services Blog / Known Upgrade Issues When U...

Known Upgrade Issues When Upgrading To Microsoft Dynamics GP 2015 R2

Sarah Purdy Profile Picture Sarah Purdy

ISSUES RESOLVED

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.

Purchasing-Pane.jpg

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.sql
Missing Vendor Nav List Fix - 2013.sql
Missing Vendor Nav List Fix - 2015.sql

If 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 = 0
AND ASI_Favorite_Type = 5
AND ASI_Favorite_Save_Level = 0
AND 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.sql
Missing Vendor Nav List Fix - 2013.sql
Missing Vendor Nav List Fix - 2015.sql

If 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.

Thanks!
Sarah

Comments

*This post is locked for comments

  • John Olley Profile Picture John Olley 365
    Posted at
    Thank you Sarah! I ran into the same problem just like Serigo did. This helped a TON so thank you for posting. I had the same scenario. GP 2013 R2 (1745) to GP 2015 R2 (1159) to GP 2018 (0672). I got the error when going from GP 2015 R2 (1159) to GP 2018 R2 (0672). I restored the Dynamics Database each time to restart the upgrade. (Don't forget to delete the dexsql.log each time so you can find the next error easily. Then I'd just added another "delete" set of lines for my next error. I only ended up with 4 instances of the error so not too bad! The upgrade continued to the GP company databases after that with no problem! Mine ended up looking like this: DELETE DYNAMICS..ASIEXP86 WHERE ASI_Favorite_Dict_ID = 0 AND ASI_Favorite_Type = 2 AND ASI_Favorite_Save_Level = 1 AND CMPANYID = 0 DELETE DYNAMICS..ASIEXP86 WHERE ASI_Favorite_Dict_ID = 0 AND ASI_Favorite_Type = 7 AND ASI_Favorite_Save_Level = 1 AND CMPANYID = 0 DELETE DYNAMICS..ASIEXP86 WHERE ASI_Favorite_Dict_ID = 0 AND ASI_Favorite_Type = 9 AND ASI_Favorite_Save_Level = 1 AND CMPANYID = 0 DELETE DYNAMICS..ASIEXP86 WHERE ASI_Favorite_Dict_ID = 0 AND ASI_Favorite_Type = 12 AND ASI_Favorite_Save_Level = 1 AND CMPANYID = 0
  • Sergio Ferreira Profile Picture Sergio Ferreira 30
    Posted at

    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.

  • kdraper Profile Picture kdraper
    Posted at

    Hi again Beat,

    Thought I should mention I have already logged it with GP support today

  • kdraper Profile Picture kdraper
    Posted at

    Hi Beat

    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 .

  • Beat Bucher GP Geek GPUG All Star Profile Picture Beat Bucher GP Gee... 28,054 Super User 2024 Season 1
    Posted at

    So... we're talking about GP 2018R2 (!!) and this bug is still around.. I'm bumping into this exact same problem today while trying to apply R2 & GP Utilities stops with the infamous message "The SP SynchronizeTableData() of form duSQLAccountSync: .... " and so on.. The issue seems again related to duplicate indexes in ASIEXP86, which strangely had absolutely no issues to upgrade from 2013 & 2015..  Note that this system wasn't even used much by then customer since the 2018 upgrade, as they were still in testing mode and hadn't added any new SmartList favorites AFAIK..

    /*  Date: 10/04/2018  Time: 23:09:48

    stmt(52932536):*/

    exec duAN_SynchronizeTable 'ASIEXP86','ASIEXP86_T','D'

    /*

    /*  Date: 10/04/2018  Time: 23:09:48

    SQLSTATE:(23000) Native Err:(2601) stmt(52932536):*/

    [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, 1, 0, 0,                ,                ,  

    I ended up applying Rob's trick by disabling the 'unique' key feature in the indexes for the table and re-ran the GP Utilities (without restoring the DYNAMICS DB) and it just went on to complete the system DB update..

    Microsoft really needs to do a better QA job on this.. Customer uses eOne's Extender & Builder series, like many other GP customers.. nothing fancy here.

  • Joni Hankin Profile Picture Joni Hankin 20
    Posted at

    Thank you ROB KLAPROTH for solving this issue.... as it has NOT been corrected in the latest GP2016 16.00.0675 build. I am upgrading from 12.00.2230 GP 2013 using SQL Server 2014 and your fix corrected my issue allowing the upgrade to be successful.  I used this script:  UPDATE ASIEXP86 SET ASI_Column_Display_Name = ASI_FIELD_NUMBER WHERE ASI_Column_Display_Name LIKE '%Debit%' OR ASI_Column_Display_Name LIKE '%Credit%'  Note the table names changed from GP2015R2

  • Community Member Profile Picture Community Member Microsoft Employee
    Posted at

    I am in the process of upgrading a client from GP2013R2 to GP2016R2 and received the Error 245 on the DYNAMICS  database. The error appears when the User Smartlist Master table is updated.

    I used the script below from Rob (Thank You Rob) and was able to get pass that error message:

    UPDATE ASIEXP86 SET ASI_COLUMN_NAME = ASI_FIELD_NUMBER WHERE ASI_COLUMN_NAME LIKE '%Debit%' OR ASI_COLUMN_NAME LIKE '%Credit%'

  • Kristie McNulty Profile Picture Kristie McNulty 977
    Posted at

    If data is returned when running the ASIEXP86 script prior to starting the R2 update, what are next steps please?  I only see next steps provided if you've started the update and have run in to the issue, but I'd like to fix the issue prior to starting the update, if that is possible.

  • Community Member Profile Picture Community Member Microsoft Employee
    Posted at

    I have to concur, this is rather frustrating.  I have spent almost 9 hours now tracking this one issue down to run scripts before the upgrade which did not resolve the problem to a hot fix to now having to determine what data in a numeric column is not numeric.  I don't see how that's even possible unless the data was in a non numeric column and was to be split during the upgrade into two columns but someone did not write the code correctly to do that.  The upgrade we are running will involve over 59 company databases and we cannot afford to be tracking something like this down on every upgrade.  Someone needs to take notice of this and resolve this immediately.  When you say something is resolved, we are relying on that information, if it was fixed in the July hotfix it is broken again in the October one.

    Please get this right and soon!!

  • Rob Klaproth Profile Picture Rob Klaproth 1,730
    Posted at

    This is getting pretty old.   The latest 3080334 hotfix STILL has the wfDeployClrAssmemblies issue.  And interestingly enough, I didn't have this issue on the previous hotfix with this client.  It's a BRAND NEW SQL server with all the windows updates and .net loaded.  When I loaded the previous hotfix and GP on their server, it worked, and they have been testing the 2015R2 upgrade for several months.  Now today we are going live, and I grab the newest hotfix and get this error?  WOW.  This is insane.