You’re offline. This is a read only version of the page.
Announcements
I'm trying to assist a customer with the error "Get/change next operation on GL_account_mstr is for an invalid key" when selecting the 2nd entry for 'by Account" in the Account Inquiry and Account Maintenance windows (see screen shot). The error does not occur for any other entries in the drop down list. The error occurred after installing SP3 for GP2010. They also have installed BSSI MEM product. The error is happening in both the live and test company; for all users (including sa) and on the TS and SQL boxes.
I've tried:
changed dynamics.set from reports.dic to reports41.dic and b39rpts.dic to b39rpts41.dic
deleted gl00105
created a new gl00100 after running all options in SQL Maintenance
confirmed DYNSA is db_owner
ran grant.sql
Any other suggestions on how to resolve this error?
Thanks! Beth
*This post is locked for comments
Also,
All of my client's GP users use one GP workstation - a terminal server. The only other GP workstation is on the SQL server - this workstation does not get the error when scrolling through accounts. I tried Richard's above recommendation (re-syncing with GP utilities) on the terminal server, but still had the problem.
I tried Jeff's suggestion - rebuilt GL00105 and restarted the SQL Server. Still have the problem :(
Hi Beth,
Everytime I have seen this error is was due to a corrupt GL00100 table. I see you have already deleted these tables but I will usually use PSTL to rebuild the GL00105 since this has given me better results.
I have also found that restarting the SQL server after running PSTL has helped.
I have a client having the same issue :(
The only additional info I can provide is that the problem is happening only when browsing/looking up accounts using segments that were RECENTLY RENAMED.
Not sure how this would have an effect, but any assistance that may be provided with the above info in mide would be greatly appreciated.
At this point I would turn on SQL Profiler and then try this again to get this error to occur and then look in the Profiler results to see what it actually tries to do. Please attach the trace file and I will take a look.
You could also try this.
1) Exit GP
2) Go into DEX.INI and change the line SYNCHRONIZE=FALSE to SYNCHRONIZE=TRUE
3) Relaunch GP and Utilities and make sure you see the box about Synchronizing.
4) Try to lookup again.
It is possible that somehow your GL Account Settings for this installation are out of sync with the GP code that has been installed.
Meant to say after deleting GL00105
Yes, I ran Checklinks on the Account Master Logical Files after deleting the GL00100. I could not find any invalid entries in the GL00100 or GL00105 table. It is happening for all companies/databases.
I've also removed User Access to the company and reset - same error.
Here's link to the site with the steps to recreate the table. www.database-answers.com/.../a-get-change-first-operation-on-table-glaccountmstr.aspx
THanks,
Beth
Did you run check links after DELETE GL00105? How did you populate the GL00100 after you created it again? If you view the GL00100 and GL00105 tables in SSMS look at the values in that column. Do you see any invalid values?
Beth,
Can you reassign-grant user access to company? Goto Tools-->Setup-->System-->User Access and take away access from company for specific user, save and then come back again and grant back access again.
It may resolve your issue.
Let me know how it goes.
Thanks
Sandip
#1
André Arnaud de Cal...
293,435
Super User 2025 Season 1
#2
Martin Dráb
232,567
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (