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.
Upgraded my local install from 2015 to 2015 R2 yesterday. Now receive the following error every time I log in: "An unexpected error was encountered trying toregister the trigger: AFTER - Credit_Check of form SOP_Entry. Error 2. This trigger will be disabled." I was not able to find the trigger.
@L. Steve Nevelle - We have seen this error coming from a third party project that is not ready for GP2015. GP 2015 R2 did make a change on the trigger "Credit_Check". They added another parameter. It is in the SDK for GP 2015 R2.
Another bug. If you have a dimension name of ACCOUNT and the dimension description is "Account" then your upgrade will crash with Analytical Accounting installed. The solution, is to change the description of the dimension to "Accounts" or something other than Account.
I'm not sure what's going on at Microsoft, but you guys need to do a better job quality checking these releases. This same type of issue happened with 2013R2 was released with the ADH tables for SmartList designer and we had to hack around it to get the upgrade to work, now here we are again - with tables related to SmartLists having more issues.
Rather then sit and delete rows and have to keep re-running the upgrade 500 times, I went ahead and restored the DYNAMICS database, and turned off the unique constraint on the index on the ASIEXP86 table. This worked beautifully. NOTE: THIS ONLY WORKS IF YOU CANCEL your upgrade and RESTORE DYNAMICS and turn the constraint off and then run GP utilities and do the upgrade.
We also had an issue with the other table, SY07240 going from 2013R2 to 2015R2 - the script provided here had an error "number of result columns doesn't match table definition", so I had to add another column to the insert statement on one of the tables, and it worked, and we were able to proceed with the upgrade.