Error Registering Table GL_Account_MSTR

Microsoft Dynamics GPWhile ding an upgrade of a client to Microsoft Dynamics GP I suddenly started getting an error when navigating the system; for example, when opening the General Journal Entry window:

Microsoft Dynamics GP: Error Registering Table GL_Account_MSTR

Microsoft Dynamics GP

Error Registering Table GL_Account_MSTR

After clicking OK on the first error message a second one was displayed:

Microsoft Dynamics GP: Unhandled script exception

Microsoft Dynamics GP

Unhandled script exception

Clicking OK again dismissed the error, but I could not do anything involving accounts.

I’m not sure what caused the error to appear as I had used the client earlier in the day and not had the same problem.

The resolution was actually fairly simple, but it took me a few minutes to work it out. Open the Dex.ini file located in, by default, C:\Program Files (x86)\Microsoft Dynamics\GP2015\Data and change Synchronize=FALSE to Synchronize=TRUE.

Once you have made this change, save and close the file and log back in Microsoft Dynamics GP and everything should again be working as this switch causes the client to synchronise with the database.

Looking for support or consultancy with Microsoft Dynamics GP?

I no longer work with Microsoft Dynamics GP, but the last company I worked for was ISC Software in the UK; if you’re looking for support or consultancy services with Microsoft Dynamics GP you can contact them here.

What should we write about next?

Your Name

Your Email

Suggested Topic

Suggestion Details

4 thoughts on “Error Registering Table GL_Account_MSTR

  1. Pingback: Comment
  2. Pingback: Comment
  3. Pingback: Comment
  4. Comment says:

    Thank you! I was helping a client run payroll on a remote desktop session on their SQL server due to a workstation problem. I had just imported the workstation’s reports package because this user was the payroll admin and had some reports that were not already on the server. I received an error on the GL Account Master for one of the reports during import, which I ignored, figuring it was a report that wouldn’t be used during the payroll run. But as soon as she started the payroll Build, she received this exact error and we had to End Task to get her out. Finding this write-up gave me a quick way to fix what would have otherwise taken me much longer to diagnose. Much appreciated!

Leave a Reply

Your email address will not be published. Required fields are marked *