Stored Procedure missing "zDP_SLB10100F_1
Ralph Daigle asked 8 years ago
When I log into (sa) I get the “Smartlist needs update…”, I click OK and after a minute GP opens up no errors.
It is registered and SL opens.
I clicked the create views and refreshed queue but when we open SL it throws the following error.
[Microsoft][SQL Server Native Client 10.0][SQL Server]Could not find stored procedure ‘DYNAMICS.dbo.zDP_SLB10100F_1’.
[Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid column name ‘Extender_Type’.
Here is part of the SQL log
/* Date: 10/26/2015 Time: 13:57:42 SQLSTATE:(37000) Native Err:(102) stmt(11753232):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near ‘USE’.*/
/*
/* Date: 10/26/2015 Time: 13:57:42 SQLSTATE:(37000) Native Err:(102) stmt(11754040):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near ‘USE’.*/
/*
/* Date: 10/26/2015 Time: 13:57:42 SQLSTATE:(37000) Native Err:(102) stmt(11754040):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near ‘USE’.*/
/*
/* Date: 10/26/2015 Time: 13:57:42 SQLSTATE:(S0002) Native Err:(3701) stmt(11747464):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot drop the procedure ‘##zDP_0184257S_1’, because it does not exist or you do not have permission.*/
/*
Lorren Zemke answered 8 years ago
The error “Invalid column name ‘Extender_Type'” signifies that SmartList Builder was not updated correctly when you upgrade from GP 10 to GP 2010 so the upgrade to GP 2015 expects that column to already exist. The upgrade from SmartList Builder 10 to SmartList Builder 2010 would needed to be done as part of the Dynamics GP upgrade.
If there are SmartLists that you need you would have to restored back to GP 10 on another system and run the upgrade to 2010 and then to 2015 again so you can export those from SmartList Builder. Once you are on GP 2010, these steps can be followed. http://www.eonesolutions.com/Manuals/SmartList-Builder/SmartList%20Builder%202015/?page=upgrading_from_2010
Lorren
Ralph replied 8 years ago Thanks Lorren I found the solution the next morning through a different search. Instead of looking for the stored proc name error I searched for the missing fields for extender_type which lead me to the link below. We went directly to GP2013r2 which would have worked. what I discovered is there is a quirk in the updater that missed it’s chance to update smartlist but updated all the other products including check printing and collections. I built the test system first and had my golden PC ready for the go-live so that all I had to do was change DSN, make backups and run dynutils to upgrade. Everything else worked like a Swiss watch and the system was ready to go. What I walk away with on this is that for EOne products we need to remove and add the EOne products back in before dynutils. This introduces a small risk as we have to change installs on the running (Golden) PC to make the switch. In the end the link below was excellent in directing me to a fix. I’ll pass this info onto a sister division that is migrating from GP11 to GP12r2 s that we will all be on the same platform. As for GP13 (2015) that will go-down sometime in the future.
http://www.eonesolutions.com/help-article/kba-01238-w5g2y3/