Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / 'Error registering tab...
Microsoft Dynamics GP (Archived)

'Error registering table GL_Account_MSTR' when printing modified reports.

(0) ShareShare
ReportReport
Posted on by Alvin Liu 110

I'm running into this error when trying to run a report after upgrading to GP2013.

So far I've tried syncronize forms and reports in GP Utilities and set Synchronize=TRUE in dex.ini but neither have yielded any results.

I tried to recreate the reports.dic by exporting and then importing the modified reports, however when exporting I'm getting this error for 6 of my reports: 'Key: Unable to set property Table to GL_Account_MSTR.' I'm not sure if this means if the reports were exported or not.

*This post is locked for comments

  • Prasan.naik Profile Picture
    Prasan.naik on at
    RE: 'Error registering table GL_Account_MSTR' when printing modified reports.

    Hey Alvin,

    Any luck with your issue here ?

    I am having difficulty here with another set of tables related to the GL_Account_Master

    I came across an issue where we are unable to create new accounts or modify existing accounts using the Account Maintenance Window. This led me to create the auto procedures to try and fix the problem. (SQL Maintenance under the the MS GP menu). However this gives me an error "Unable to register GL_Account_MSTR_Filter1".


    Hence I came across your post here. I'm going to be attempting the same thing and trying to recreate the tables.

  • Alvin Liu Profile Picture
    Alvin Liu 110 on at
    Re: 'Error registering table GL_Account_MSTR' when printing modified reports.

    I succesfully rebuild GL00105 last night but it didn't seem to fix the situation. I tried exporting the reports again, but it's still giving me the same error. ('Key: Unable to set property Table to GL_Account_MSTR')

    I'm going to try to get the reports rebuilt in report writer, will post update here.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: 'Error registering table GL_Account_MSTR' when printing modified reports.

    Hi Alvin,

    Thanks for the advice. Typically if there is a problem with the GL00105 you'll run into problems creating new accounts or modifying existing ones. Another indicator of a problem with this table is if each time you choose one account another account is used. This can mean the account index between the GL00100 and GL00105 is out and recreating the GL00105 will usually fix this.

    Regards

    Rob

  • Alvin Liu Profile Picture
    Alvin Liu 110 on at
    Re: 'Error registering table GL_Account_MSTR' when printing modified reports.

    Hi Rob,

    Thanks for your quick response. I will recreate GL00105 tonight after the client's working hours and then post an update. Just out of curiousity, what are some other possible symptoms of corrupted GL00105?

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: 'Error registering table GL_Account_MSTR' when printing modified reports.

    Hi Alvin,

    Thanks for raising this with us. Typically this error occurs when the Reports.dic is damaged or the GL Account Index Master is corrupt. I suggest that we recreate the GL00105 first, then recreate the reports dictionary again, and see if this corrects the problem for you.

    Please follow the steps in this KB to recreate the GL00105:

    mbs2.microsoft.com/.../KBDisplay.aspx

    After this lets recreate the reports dictionary then see if the modified reports can now be printed. If the problem continues after this the error may be occurring due to a damaged layout. If we recreate the problem report and update the table links this may correct the error.

    I suggest that we do the following to see if we can correct the error for one of the reports

    1. Export the report that is creating the error from Customization Maintenance

    2. Delete the report from modified reports in Report Writer

    3. Add it back over from the left side pane in Reports window

    4. Recreate the modifications on the report

    5. Verify security is still granted to the report in Alternate/Modified Forms and Reports

    After this try printing the report to see if the error occurs. If the error does not occur lets repeat these steps for the other modified reports that have this error. Please let me know if you would like any additional information on this issue

    Regards

    Rob

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

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,468 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,287 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans