Skip to main content

Notifications

Announcements

Check out the New Agent Creator Community
Announcing new navigation menus and the Engage with the Community forum!
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Can't open SmartLi...
Microsoft Dynamics GP (Archived)

Can't open SmartList in GP 2013R2 - getting unhandled script exception

(0) ShareShare
ReportReport
Posted on by Rob Klaproth 1,730

When opening SmartList, we get Unhandled Script Exception:

Index 0 of local array is out of range in script

'ASI_Initialize_Explorer_Tree'. Script terminated.

If I click OK, i get into SmartList, but it won't load any of the SmartLists, not even the default ones.

We have SmartList Builder, both the microsoft one, and the eOne installed.

When I run a DEXSQL trace, I don't see much related to that, but I am seeing a:

Cannot find stored procedure 'DYNAMICS.dbo.zDP_SY30000F_1'

It looks like SY30000 is a new table in 2013R2, so I'm guessing this must be R2 related.

*This post is locked for comments

  • Suggested answer
    L Vail Profile Picture
    L Vail 65,271 on at
    RE: Can't open SmartList in GP 2013R2 - getting unhandled script exception

    Hi Rob,

    I just had this error and here's what I did to solve it. My problem was a difference between the ASIEXP81 and the ADH00100. It came about because of the new SmartList Designer feature. I added the missing records to the ADH00100 table and the problem was solved. Here's how it looked:

    SELECT DISTINCT asiexp81.asi_favorite_dict_id

                   , asiexp81.asi_favorite_type

    FROM   asiexp81

    WHERE  asi_favorite_type BETWEEN 498 AND 22000

          AND NOT EXISTS (SELECT asi_favorite_dict_id

                                 , asi_favorite_type

                          FROM   adh00100

                          WHERE  asi_favorite_dict_id = A.asi_favorite_dict_id

                                 AND asi_favorite_type = A.asi_favorite_type)  

    The results of the query above told me I was missing the two items below. I ran the Insert statement to populate the ADH00100 table. For me, it fixed it.

    begin transaction

    insert into DYNAMICS..ADH00100 values ('0',  '498','3',  'Requisition Line Items','sa','-1')

    insert into DYNAMICS..ADH00100 values ('0',  '499','3',  'Purchase Requisitions','sa','-1')

    --commit transaction

    Kind regards,

    Leslie

  • Pam Robertson Profile Picture
    Pam Robertson 4 on at
    RE: Can't open SmartList in GP 2013R2 - getting unhandled script exception

    Rob, did you ever figure this out?  We have a customer who is getting  a short dexsql.log generated regularly since installing an update to Smartlist Builder with basically just the same message: Cannot find stored procedure 'DYNAMICS.dbo.zDP_SY30000F_1'.  Everything seems to be running properly related to GP and Smartlist. 

  • Tom Mathew Profile Picture
    Tom Mathew 1,750 on at
    RE: Can't open SmartList in GP 2013R2 - getting unhandled script exception

    Try running the SQL maintenance for the smart list on with only the stored procedures option checked along with the recompile option.

    Please keep a backup of the databases before doing this process

  • Mahmoud Saadi Profile Picture
    Mahmoud Saadi 32,738 on at
    RE: Can't open SmartList in GP 2013R2 - getting unhandled script exception

    Would be highly appreciated if you keep us updated

    Your feedback is highly appreciated,

  • Rob Klaproth Profile Picture
    Rob Klaproth 1,730 on at
    RE: Can't open SmartList in GP 2013R2 - getting unhandled script exception

    Hi Mahmoud, the dex traces didn't turn up much, none of the Sprocs referenced in the dex trace are missing, I ran the entire trade in SSMS and it runs without any errors.  

    I've logged a case with Microsoft.  

  • Mahmoud Saadi Profile Picture
    Mahmoud Saadi 32,738 on at
    RE: Can't open SmartList in GP 2013R2 - getting unhandled script exception

    I believe this needs further more debugging, this is just to include that the SY30000 is a new table in GP 2013 R2, You may start from here.

    I recommend troubleshooting this on the SQL Profiler level, as I suspect that some stored procedures might be missing. Running the GP utilities may get things on track again.

    One more advice, back up is always a must.

    Your feedback is highly appreciated,

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Check out the New Agent Creator Community
Announcing new navigation menus and the Engage with the Community forum!

Quick Links

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Almas Mahfooz Profile Picture

Almas Mahfooz 3 User Group Leader

Last month Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans