Good Morning,
We are receiving this error message in GP when trying to use the Smartlist function, any ideas?
Thanks
Rob
Good Morning,
We are receiving this error message in GP when trying to use the Smartlist function, any ideas?
Thanks
Rob
Update on this......
Via a support case with the same exact error, we found working with eOne (at least in that case) that the issue was that a user had taken one of the default SmartLists and clicked 'Modify' and it somehow put it in the 99 series, which is for SmartLists, under the 'Additional SmartList' folder.
Changing the series number back to 1, the SmartLists were then able to be opened.
When SmartList Builder was removed/uninstalled, the error didn't show, so working with eOne, the customer resolved by finding the above.
Thanks
I've seen a '"Index 0 of local array" error launching Smartlist due to mismatches between the ASIEXP81, ADH00100 and ADH00101 but not so much Index 99.
The first question I'd have is whether you have SmartList Builder from eOne installed and if so, whether you are on Dynamics GP 2018 as this forum indicates?
If you are, on one of the machines where Dynamics GP is installed and showing this error, have all users log out of Dynamics GP, then rename the GP directory from something like C:\Program Files (x86)\Microsoft Dynamics\GP\ to C:\Program Files (x86)\Microsoft Dynamics\GP_OLD\.
2. From there, in Control Panel > Programs and Features, right-click on Dynamics GP, choose 'Change' and then select the 'Repair' option when prompted with the options window. Verify the Repair process runs successfully. Its run successfully
Repair will re-create the entire GP directory under the original name, minus modified forms/reports dictionary files, third party products, customizations, etc.
3. Login to this 'new' Dynamics GP directory as 'sa' and see if you now recreate this 'Index 99 of local array' error message or not.
--if not, then we'd want to add back third party products and customizations, if any, one by one, testing after each one till the error returns. I'd start with SmartList Builder, if applicable.
--if not, generate a dexsql.log from this 'new' GP directory and re-create the SmartList error message. At that point, we'd probably want a support case opened to troubleshoot further.
Thanks
Here's some steps we tried:
It almost seems like there is a duplicate favorite since I can see that the entries in the dexsql.log that are erroring are in the SQL table but what is trying to get input has a higher field sequence number. Example this entry errored
BEGIN DECLARE @num int EXEC DYNAMICS.dbo.zDP_ASIEXP86SI 0, 6, 0, 0, '', '', '', 11, 1, 1, 5147, 22001, 'Company', 0, @num OUT SELECT @num END
The number 11 is the ASI_Field_Sequence. But there is the same exact entry is already in the table but with a field sequence number of 10.
This is just one type of error. There are other tables that give a different error
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,235 Most Valuable Professional
nmaenpaa 101,156