RE: A get change first operation on table 'GL_Accounts_MSTR' failed to accessing SQL data
More times than not, when we see that type of message, there is a discrepancy between what the procedures for that table are expecting from the table structure, and what it actually is showing as.
The GL00100 table is one of the tables that gets setup with a specific amount of columns depending on the account framework maximums specified when Dynamics GP was first implemented.
For example, if we had a framework maximum setup of 10 segments each with a length of 5, the GL00100 table would have 10 columns, ACTNUMBR_1 through ACTNUMBR_10 for these 10 segments, and each column with a length of 5.
You can confirm your account framework maximums per the SY003001 and SY00302 system tables.
If the table is incorrect or the procedures are expecting a different structure, you will get an error message like this.
One thing you can try, in your GP instance, go into the Dex.ini and change the SYNCHRONIZE= line from FALSE to TRUE, save changes and close this file.
Launch GP Utilities and it shouldn't detect anything needs to be upgraded, if your database version and GP client versions match, but should synchronize the dictionary file. Once it does that, close Dynamics GP and open the Dex.ini again to verify it now shows FALSE for the SYNCHRONIZE= line.
If it still shows TRUE, the Dynamics.dic may be damaged and need replacing.
If it now shows FALSE, login to GP again and see if you still get this error message.
Thanks
